Post reply

How to Choose the Right Tool for MS SQL to PostgreSQL Migration

  • June 20, 2025 at 12:00 am

    #4607296

    Comments posted to this topic are about the item How to Choose the Right Tool for MS SQL to PostgreSQL Migration

  • June 20, 2025 at 2:13 pm

    #4610613

    This is a pretty good article but I would not call it an in depth analysis.

    ewm2

  • June 20, 2025 at 2:56 pm

    #4610635

    Maybe call it a Framework?

    412-977-3526 call/text

  • June 21, 2025 at 12:10 am

    #4610847

    "Data Integrity:

    Is data transferred reliably?

    Are full and incremental loads supported?

    Finally, does the tool validate post-migration data for consistency?"

    1. This is a vague perspective as there is usually a all or nothing approach to moving your data. Any one issue should have error handling or if severe enough the ETL should abort and rollback any transaction. But issues here are very likely caused by a developer's oversight in design leading to a data type issue, null handling , etc..
    2. A migration tool should have batching hopefully & avoid any full logging and resource use on target system during an initial load.
    3. How do you validate for consistency ? Counts via logging? N rows selected & n rows copied in? Rather vague.

    ----------------------------------------------------

  • June 21, 2025 at 3:25 pm

    #4611129

    The article is really helpful thank for writing this; however, if it is focused on MS SQL to PostgreSQL conversion, then there is no SSMA equivalent available, unlike what exists for Oracle to SQL Server migrations. Please correct me if I am missing something

    Thanks,
    Abhinav

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply