From: | Igal Sapir <igal(at)lucee(dot)org> |
---|---|
To: | Ravi Krishna <ravi_krishna(at)aol(dot)com> |
Cc: | "Psql_General (E-mail)" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres for SQL Server users |
Date: | 2019-05-06 19:47:32 |
Message-ID: | CA+zig09kP5GOkwJcZ8ntrEnLH_2hVgQBTk2U4J=6Nj5Nxa90jw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ravi,
On Mon, May 6, 2019 at 12:28 PM Ravi Krishna <ravi_krishna(at)aol(dot)com> wrote:
> > I was wondering if anyone has any tips that are specific for SQL Server
> users? Best features? Known issues? Common rebuttals?
>
> Are you talking about SS to PG migration.
>
> Generally SQLServer shops use SS specific functions and T-SQL heavily
> since they provide very good functionality.
> For example:
>
> 1, convert function is used heavily in SQL to format various datetime
> formats.
>
> 2. SS does case insensitive searches. Converting it to PG involves
> modifying the SQL. Not an easy job to do.
>
> 3. SS has 3 part structures. DB.SCHEMA.TABLE which can be used in SQL.
> PG can go only up to 2 part SCHEMA.TABLE.
> 3 part is possible, but using FDW or other cumbersome mechanism.
>
Thank you. I am referring more to features, functionality, scalability,
etc.
I want to get them interested in giving Postgres a try instead of SQL
Server. Surely the savings on licenses can be substantial (I have no idea
how much, TBH), but I want to instill confidence in them that anything they
do with SQL Server can be done with Postgres.
Igal
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2019-05-06 19:53:45 | Re: Postgres for SQL Server users |
Previous Message | Ravi Krishna | 2019-05-06 19:28:31 | Re: Postgres for SQL Server users |