| From: | KK CHN <kkchn(dot)in(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | MS SQL to Postgres |
| Date: | 2025-08-20 17:25:56 |
| Message-ID: | CAKgGyB8ZZLzDVg3eCym=BMf7+8LOS-bfOE1EdXWA_X4qha_=Xw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
I am in search of the best practices to migrate from an MS SQL database
server to PostgreSQL 16
Existing DB server MSSQL with 6 Million records and 3.5 TB with 424 Tables
running from 2019 onwards.
Each table has 5 to 16 columns ( basically text, numbers, lat long
coordinates , time stamps, and images/voice file (stored in archive
folders)reference links, etc. ).
I am in need to port / migrate all this data from this MS SQL server to
Postgres16 .
1. What are the best methods and practices folks employ to do this kind of
data porting operations?
2. what are the tools and techniques to explored / employed for this
3. How much time is consumed by employing the right tools, the entire
porting of 6 million records of 3.5 TB size to Postgres 16 takes
4. Any hurdles or challenges or risks
Kindly enlighten me with the best practices and reference materials /
links or tutorials to perform these operations successfully.
Thank you,
Krishane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2025-08-20 17:30:00 | Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug |
| Previous Message | Rob Sargent | 2025-08-20 17:24:29 | Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug |