nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Differences and benefits between SQL Server corporate geodatabase and PostgreSQL with PostGIS extension

FabioNeiraAlzate

Hello everyone,

I'm currently evaluating options for implementing a corporate geodatabase and I'm debating between two options: using Microsoft's SQL Server or PostgreSQL with the PostGIS extension, both with Esri's corporate geodatabase.

I'd like to hear your thoughts and experiences regarding the key differences between these two options, as well as the benefits each one offers in terms of performance, scalability, geospatial capabilities, interoperability with other applications, and any other relevant aspects I should consider.

I appreciate any input or recommendations you can share to help me make an informed decision.

Thank you!

Find more posts tagged with

Database Access

Enterprise geodatabase

Databases

Accepted answers

MMBR

My 2 cents to contribute to this discussion.

SQL Server - need to buy licenses, do not go with standard edition, you need enterprise edition because it has nice features like rebuild indexes online, parallelism, etc., backup and recovery is easier, can do point in time recovery really easy, Esri uses the native SQL Server Spatial data types to store the spatial data, there is no esri st_geometry spatial type in SQL Server, also get the SQL Server security updates and technical support. SQL Server supports Windows Authentication, very easy to setup. SQL Server can run on Windows and Linux as well.

PostgreSQL: free open source, but backup recovery not as easy, point in time recovery difficult, need to install PG updates and if using PostGIS then install the PostGIS updates as well, Esri has st_geometry spatial type for PostgreSQL, decision to use esri st_geometry or PostGIS is up to the customer to decide, many customers pay for the EnterpriseDB solutions on top of PostgreSQL for their deployments, and EnterpriseDB can help with paid technical support.

How to Upgrade the PostgreSQL and PostGIS version for the Enterprise Geodatabase on Windows
How to Upgrade the PostgreSQL and PostGIS version for the Enterprise Geodatabase on Linux
How to Configure Windows Authentication for the PostgreSQL Enterprise Geodatabase

I hope this helps.

Enterprise Geodatabases Best Practices visit my community.esri.com blog.

Mapping and Charting Solutions (MCS) Enterprise Da... - Esri Community

All comments

VinceAngelo

This is more like a religious issue than a technical one. The DBA should have a say in the process, since they'll be the one supporting the configuration.

Esri supports both (provided you're using the release documented as supported [and recognize "and higher" where appropriate]).

Benchmarking both for your requirements is not a bad idea.

- V

FabioNeiraAlzate

Thanks for your contribution

MMBR

How to Upgrade the PostgreSQL and PostGIS version for the Enterprise Geodatabase on Windows
How to Upgrade the PostgreSQL and PostGIS version for the Enterprise Geodatabase on Linux
How to Configure Windows Authentication for the PostgreSQL Enterprise Geodatabase

I hope this helps.

Enterprise Geodatabases Best Practices visit my community.esri.com blog.

Mapping and Charting Solutions (MCS) Enterprise Da... - Esri Community

PatOBrien

Hello @FabioNeiraAlzate

I have been using SQL Server based Geodatabases for the most part of 10 years. I think they are great from a technical perspective. For those that require heavy interrogation of Rasters at the database, SQL Server is void.

We have investigated PostGresSQL with PostGIS extension, specifcilally relating to Raster/Vector relationships, and the results are promising. Can rapidly solve a simple scenario such as calculate Z values for my vertices? IE. have a new polyline with 20,000 vertices where Z = unknown, have a DEM. PostGresSQL can fly through using PostGIS functions (ST_Force3DZ & ST_Value amonst others) and calc the Z (raster/vectors relatable in the DB. Done in seconds.
Could be a game changer when compared to processing Z and other raster data against ESRI Geoprocessing tools. FAR superior processing speed.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.