Detailed list of what A1 Data Migrator handles automatically and what it surfaces for you to decide on.
0/1
false/true
pgcrypto
GETDATE()
SYSDATETIME()
now()
GETUTCDATE()
SYSUTCDATETIME()
(now() at time zone 'utc')
NEWID()
gen_random_uuid()
SUSER_SNAME()
current_user
DB_NAME()
HOST_NAME()
current_database()
inet_client_addr()::text
CONVERT([date], expr)
CAST(expr AS date)
'X'+expr
'X' || expr
DEFAULT 0
TIMESTAMP '1900-01-01 00:00:00'
When a btree index hits the 2,704-byte row limit, the runner reacts:
USING HASH
{db}_constraints_report.sql
NOT VALID
Triggers, stored procedures, views, scalar/table-valued functions are not auto-rewritten (T-SQL → PL/pgSQL is too lossy). Instead:
_migration_meta.objects
tsql_definition
{db}_unconverted_objects.sql
port_status
PENDING / IN_PROGRESS / DONE / IGNORED
_migration_meta.unported
a1mig inspect Read source schema and print a summary report. a1mig convert Generate the PostgreSQL DDL script (writes to file). a1mig schema Phase 1: drop+create target DB and apply tables (no idx/FK). a1mig data Phase 2: copy rows (binary COPY, deferred FKs). a1mig constraints Phase 3: indexes + FKs + check constraints (smart fallback). a1mig objects Phase 4: capture triggers/procs/views/functions into _migration_meta.objects + write porting workbook. a1mig full Run all phases in order, then verify. a1mig verify Compare row counts between source and target tables.
قائمة تفصيلية بكل ما يعالجه A1 Data Migrator تلقائياً وما يُظهره لك للقرار.
عندما يتجاوز btree index حدّ الـ 2704 بايت، يتصرّف الـ runner كالآتي:
We use cookies to improve your experience.