From: | Brent Wood <pcreso(at)yahoo(dot)com> |
---|---|
To: | "Psql_General (E-mail)" <pgsql-general(at)postgresql(dot)org>, Igal Sapir <igal(at)lucee(dot)org> |
Subject: | Re: Postgres for SQL Server users |
Date: | 2019-05-06 20:44:18 |
Message-ID: | 691242664.2245464.1557175458417@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Igal,
One relevant comment I found interesting a couple of years ago...
A New Zealand Govt agency was installing an institutional GIS system (several thousand potential users). It supported different back-end spatial databases. Previous installs of this system for other clients had used MS SQL Server, this was the first that was installed on a Postgres/Postgis back end.
As it was about to go into action as a live, production system, I was speaking to one of the team doing the installation, and asked how they had found working with Postgres instead of SQL Server. The reply was worth a few formal benchmarks:
"It's so easy to connect to and sh*t it's fast!"
Might be a useful comment for your presentation :-) A few years on & it is still working fine...
Cheers...
Brent Wood
On Tuesday, May 7, 2019, 7:21:40 AM GMT+12, Igal Sapir <igal(at)lucee(dot)org> wrote:
Next month I'll be making a presentation about Postgres to a SQL Server crowd in L.A. at their SQL Saturday event.
I was wondering if anyone has any tips that are specific for SQL Server users? Best features? Known issues? Common rebuttals?
Thanks,
Igal
From | Date | Subject | |
---|---|---|---|
Next Message | Ravi Krishna | 2019-05-06 20:44:52 | Re: Postgres for SQL Server users |
Previous Message | Tom Lane | 2019-05-06 20:21:36 | Re: Relaxing NaN/Infinity restriction in JSON fields |