Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uomZg-00A5wO-S3 for pgsql-general@arkaria.postgresql.org; Wed, 20 Aug 2025 17:26:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uomZg-00ALBc-76 for pgsql-general@arkaria.postgresql.org; Wed, 20 Aug 2025 17:26:12 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uomZf-00ALBU-T2 for pgsql-general@lists.postgresql.org; Wed, 20 Aug 2025 17:26:12 +0000 Received: from mail-yb1-xb2f.google.com ([2607:f8b0:4864:20::b2f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uomZe-000wuH-0z for pgsql-general@lists.postgresql.org; Wed, 20 Aug 2025 17:26:12 +0000 Received: by mail-yb1-xb2f.google.com with SMTP id 3f1490d57ef6-e931cddb0e2so98423276.3 for ; Wed, 20 Aug 2025 10:26:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1755710768; x=1756315568; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=4S6aP7mJF6l8aZIpXzv3fdkl2b9Z2ocPGgPkRaG6gJ8=; b=PMASZ0CAKf0DE7NgbPE81ImFGJTxW+9fjHH0qKhIghx2JYNelfQAgS2x6r5bZZkWvQ UTWgG6xUQwl3HFBfMl6Zo6xCk63VLCUd59sb4xo5UYu4dV+vYNvKaZs4S7E4q+EuOqtE BaBryiCqbSuAjDtYTEIUloGNvxl9SmC2p6i7IgohVVyx50a2s/hp40cmalSe9towCKCf HD+iZmhRb6J0xYqsUx7PWf3sctUrMTEDwGsGdNHbEN2+TIg5paGA4dNT9jTagwuBxStp XI/NbfyDmL/ED+IpP4rfwYmLMdftKFruwjYIadFHF+nlb2z9d8XsZIW39eXJekbWNnbv Phig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755710768; x=1756315568; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=4S6aP7mJF6l8aZIpXzv3fdkl2b9Z2ocPGgPkRaG6gJ8=; b=dng21cMCyXQnoJbr3lgmp9qpBPX23KWCe3fOTmlvIDM7nDwG0D0Se98nMXtTyXXHYs p0UvG5Oxmzsp5jdhtUJt9aIMZhZEIrRkgaB4XWi4rZrxcRrN4H79NYtn5Lp4RYNS+HpR fC3Xhhw40/FoZcnx8OnLGHuDKgditlOjP0DC1FW5TvhsdSxo/R0aAdj4Xl/a14cDYfFT KOsy+YPp/QdN66TvuJI3fGkcusOUCl4aWUxupBvDXrl4gOGYO7FBI2QVMsyeB400nJgx 2grT7ZvtsfUXNJORIBkQd2Czd2g8AW4uL+ouhM0NjwSwKiAaiGc1M9YyHEHBUGQihEy4 1gaw== X-Gm-Message-State: AOJu0YzW5PgbzY6eatv5ZBbG7GnSqafjDEiP2gqsxlEgntN/giU5hLFk 2+eI86ECKCE1MAGv0OZkrMCxdmsDPDVWTgzR3RXzobZjt/8hG6SfaSyY/HXYdDa8QYDyHNOJU4C 3k00VQkSF/U7DpKb5NzRhB8jPWBIeqz6hgx7G X-Gm-Gg: ASbGncuXCFuC2QY5C7qNVMUuq+6KOiWL7qPWHSp714FFnOiDOp4LE8hyLoMxAVpSxOa n/Z5t+nvYMnBruh55pXgzMzRZbE35LPo2zmtbMmXqXJ5Tph8irgXWCVxmr1FiP7k06jbXO3W/NU 7wtgcROeGoar7Nqx7A4hTjSZKQyDbfxkfY/x4cnSY5zfxozbfFGq8kNGKoqH8IJAo3T/7oxyENL Aw9KHCVagi2RvIbg/Z6n75AlOqfWbe5VmFa3HhztA== X-Google-Smtp-Source: AGHT+IHNhmOQ+vtWlcBN0qKio0D0vsnuqQyorw1jrHUdem5WlGl2fM748lcuhRWIhx/0RAVO/clpFccRptINWhFoZxQ= X-Received: by 2002:a05:6902:2890:b0:e90:39b7:6085 with SMTP id 3f1490d57ef6-e94f661a4famr3393220276.17.1755710768529; Wed, 20 Aug 2025 10:26:08 -0700 (PDT) MIME-Version: 1.0 From: KK CHN Date: Wed, 20 Aug 2025 22:55:56 +0530 X-Gm-Features: Ac12FXyIFh64l0_492VPM2h8TBjeX1hM_KolWx2_CPMxODTK60XMzBBSYJaikJg Message-ID: Subject: MS SQL to Postgres To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000b014bd063ccf44fb" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b014bd063ccf44fb Content-Type: text/plain; charset="UTF-8" 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 --000000000000b014bd063ccf44fb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,=C2=A0

I am in search of the bes= t practices to migrate from an MS SQL database server to PostgreSQL 16

Existing=C2=A0DB server=C2=A0MSSQL with 6 Million reco= rds and 3.5 TB=C2=A0 with 424 Tables running from 2019 onwards.
<= br>
Each table has 5 to 16 columns ( basically text, numbers, lat= long coordinates , time stamps, and images/voice file (stored in archive f= olders)reference links, etc.=C2=A0 ).

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 emp= loy to do this kind of data porting operations?=C2=A0=C2=A0
2. wh= at are the tools and techniques to explored / employed for this
3= . How much time is consumed by employing the right tools, the entire portin= g of 6 million records of 3.5 TB size to Postgres 16 takes=C2=A0
= 4. Any hurdles or challenges or risks=C2=A0

Kindly= enlighten me with the best practices and=C2=A0 reference materials=C2=A0/ = links or tutorials to perform=C2=A0these operations successfully.=C2=A0=C2= =A0

Thank you,=C2=A0
Krishane=C2=A0

--000000000000b014bd063ccf44fb--