Brent,
On Tue, May 7, 2019 at 12:42 PM Brent Wood wrote:
> I have not used SS for spatial data, but I don't have a Postgres database
> without Postgis installed. The OSGEO ecosystem and synergies with other
> FOSS GIS tools is fantastic.
>
> And it does not stop with the Postgis extension. For t
I have not used SS for spatial data, but I don't have a Postgres database
without Postgis installed. The OSGEO ecosystem and synergies with other FOSS
GIS tools is fantastic.
And it does not stop with the Postgis extension. For time series data (anything
from fleet management to sensor data) Po
> 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?
PosgreSQL is more than a "database", it's
Igal Sapir schrieb am 07.05.2019 um 07:58:
> GIS is a good feature but it's a niche feature, so while I'll mention
> it with extensions I am looking for more general-purpose comparisons
> and areas where Postgres is as-good or better than SQL Server.
I have a comparison of various DBMS products on
For me, another very useful featureset in Postgres is the extensive set of
datatypes and functions, including the strong JSONB support.
Also, i would focus on the widespread support of Postgresql by services
such as Amazon, Google, Heroku,
Another place to focus on would be the really extensive l
Tony,
On Mon, May 6, 2019 at 10:35 PM Tony Shelver wrote:
> I have to agree on the geospatial (GIS) features.
> I converted from SQL Server to Postgresql for our extended tracking
> database. The SS geospatial feature set doesn't seem nearly as robust or
> complete or perfoirmant as that suppli
Ron,
On Mon, May 6, 2019 at 12:54 PM Ron wrote:
> On 5/6/19 2:47 PM, Igal Sapir wrote:
> > but I want to instill confidence in them that anything they do with SQL
> > Server can be done with Postgres.
>
> Right off the top of my head, here are some things you can't (easily and
> trivially) do in
Brent,
On Mon, May 6, 2019 at 1:44 PM Brent Wood wrote:
> 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
> databa
I have to agree on the geospatial (GIS) features.
I converted from SQL Server to Postgresql for our extended tracking
database. The SS geospatial feature set doesn't seem nearly as robust or
complete or perfoirmant as that supplied by PostGIS.
The PostGIS ecosystem of open source / 3rd party tools
On Mon, May 6, 2019 at 2:49 PM Adam Brusselback
wrote:
> I think the main "gotcha" when I moved from SQL Server to Postgres was I
> didn't even realize the amount of in-line t-sql I would use to just get
> stuff done for ad-hoc analysis. Postgres doesn't have a good way to emulate
> this. DO bloc
Ravi Krishna schrieb am 06.05.2019 um 23:56:
I recently had to write an equivalent of UNPIVOT.
UNPIVOT is actually quite easy with Postgres:
https://blog.sql-workbench.eu/post/unpivot-with-postgres/
Thomas
> I think the main "gotcha" when I moved from SQL Server to Postgres was
> I didn't even realize the amount of in-line t-sql I would use to just get
> stuff done
> for ad-hoc analysis.
T-SQL is an exceptionally powerful SQL based language. Add to it, the many
functions
SS has. I recently had
I think the main "gotcha" when I moved from SQL Server to Postgres was I
didn't even realize the amount of in-line t-sql I would use to just get
stuff done for ad-hoc analysis. Postgres doesn't have a good way to emulate
this. DO blocks cannot return resultsets, so short of creating a function
and
more:
1. No db level backup/restore in PG, at least no easy way.
2. No cross db query.
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 S
On 5/6/19 2:47 PM, Igal Sapir wrote:
but I want to instill confidence in them that anything they do with SQL
Server can be done with Postgres.
Right off the top of my head, here are some things you can't (easily and
trivially) do in Postgres:
- Transparent Data Encryption
- Block level full,
Ravi,
On Mon, May 6, 2019 at 12:28 PM Ravi Krishna 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 a
> 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 e
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
19 matches
Mail list logo
