From: | Alban Hertroys <haramrae(at)gmail(dot)com> |
---|---|
To: | KK CHN <kkchn(dot)in(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: MS SQL to Postgres |
Date: | 2025-08-20 20:14:56 |
Message-ID: | 48AA15E9-1979-489D-B94E-5FE2972A6AD2@gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On 20 Aug 2025, at 19:25, KK CHN <kkchn(dot)in(at)gmail(dot)com> wrote:
(…)
> 4. Any hurdles or challenges or risks
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’ve 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Justin | 2025-08-20 21:31:16 | Re: MS SQL to Postgres |
Previous Message | Alban Hertroys | 2025-08-20 20:03:52 | Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug |