public inbox for [email protected]  

help / color / mirror / Atom feed

From: Adrian Klaver <[email protected]>
To: KK CHN <[email protected]>
To: [email protected]
Subject: Re: MS SQL to Postgres
Date: Wed, 20 Aug 2025 10:56:49 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKgGyB8ZZLzDVg3eCym=BMf7+8LOS-bfOE1EdXWA_X4qha_=Xw@mail.gmail.com>
References: <CAKgGyB8ZZLzDVg3eCym=BMf7+8LOS-bfOE1EdXWA_X4qha_=Xw@mail.gmail.com>

On 8/20/25 10:25, KK CHN wrote:
> 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 .
> 

Up front, I have not moved data from MSSQL to Postgres. What follows 
will be generic.

> 1. What are the best methods and practices folks employ to do this kind 
> of data porting operations?

Planning and patience.

It is a matter of drawing a map/diagram of where you are now(MSSQL) and 
where you want to end up(Postgres) with steps to get from A to B.

> 2. what are the tools and techniques to explored / employed for this

One that I know of:
	https://pgloader.io/

> 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

Unknowable at this point. I will say it depends on how many MSSQL 
specific features you use and whether there are Postgres direct 
equivalents or you whether you will need to do extensive modifications.

> 4. Any hurdles or challenges or risks

Changing database vendors.

> 
> Kindly enlighten me with the best practices and  reference materials / 
> links or tutorials to perform these operations successfully.
> 
> Thank you,
> Krishane
> 


-- 
Adrian Klaver
[email protected]

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: MS SQL to Postgres
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox