On 8/20/25 15:52, Avinash Vallarapu wrote:
Hi Krishane,
* SQL Server often auto-generates constraint names, while PostgreSQL
typically requires explicit
names.
You will need to give more detail on above as:
create table constraint_test (id integer primary key, fld_1 varchar,
fld
Hi Krishane,
On Wed, Aug 20, 2025 at 1:26 PM 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.
>
This is definitely
On Wed, Aug 20, 2025 at 4:15 PM Alban Hertroys wrote:
>
> > On 20 Aug 2025, at 19:25, KK CHN 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 co
> On 20 Aug 2025, at 19:25, KK CHN 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 S
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, number
