Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Subject: Re: MS SQL to Postgres
From: Alban Hertroys <haramrae@gmail.com>
In-Reply-To: <CAKgGyB8ZZLzDVg3eCym=BMf7+8LOS-bfOE1EdXWA_X4qha_=Xw@mail.gmail.com>
Date: Wed, 20 Aug 2025 22:14:56 +0200
Cc: pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <48AA15E9-1979-489D-B94E-5FE2972A6AD2@gmail.com>
References: <CAKgGyB8ZZLzDVg3eCym=BMf7+8LOS-bfOE1EdXWA_X4qha_=Xw@mail.gmail.com>
To: KK CHN <kkchn.in@gmail.com>
Archived-At: <https://www.postgresql.org/message-id/48AA15E9-1979-489D-B94E-5FE2972A6AD2%40gmail.com>
Precedence: bulk


> On 20 Aug 2025, at 19:25, KK CHN <kkchn.in@gmail.com> wrote:

(=E2=80=A6)

> 4. Any hurdles or challenges or risks=20

MS SQL defaults to case insensitive string comparisons, trimming =
trailing white-space.

PostgreSQL defaults to case sensitive string comparisons, so incorrectly =
cased strings in queries that match in MS SQL will not match in =
PostgreSQL.

The trailing spaces bit is not going to matter while moving the data to =
Postgres, as you will not get any trailing spaces from MS SQL to be =
stored in PostgreSQL (they=E2=80=99ve been trimmed already, after all) - =
but it could trigger some application bugs where people have assumed =
that trailing spaces get trimmed.

Also, time zone names are wildly different between the two. MS SQL uses =
Microsoft Windows time zone names, Postgres (and most other RDBMSes) use =
IANA names.

Alban Hertroys
--
There is always an exception to always.