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
| Marcelo Marques | Principal Product Engineer | Esri |
| Cloud & Database Administrator | OCP - Oracle Certified Professional |
I work with Enterprise Geodatabases since 1997.
“ I do not fear computers. I fear the lack of them." Isaac Isimov