Migrating from On-premises MS SQL Server to AWS Aurora PostgreSQL

Question

We are considering moving to Aurora PostgreSQL for our Enterprise Geodatabases. Posting to see if any one with experience in this type of migration will share any tips/recommendations.

I think the only spatial storage that works is PostGIS as ST_Geometry extension from ESRI cannot be used? Would this be a problem? Any other useful info is much appreciated.

Thanks in advance..

-J

SrinivasJasti · Answer

Thanks. I am aware of the ports and performance implications for desktop clients. What I am most interested in is the performance of serving spatial data using Aurora PostgreSQL vs MS SQL Spatial  when everything else is almost the same. We ran into performance issues with MS SQL Spatial types and ArcGIS.

Thank you for taking time to provide useful info. I guess I have some testing to do. I will update the post if I find any interesting info to share.

George_Thompson · Answer

When you move to AWS, make sure that the clients are in the same region/area to get the best performance.

You can connect to an enterprise geodatabase in an Amazon RDS instance from an on-premises installation of ArcGIS Pro; however, performance will be slower than if you connect from an ArcGIS Pro installation on an Amazon Elastic Compute Cloud (EC2) instance in the same AWS region as the RDS instance. Also, you must open ports in your security group to connect to the RDS instance from an on-premises machine.

Connect from an ArcGIS Server instance to an enterprise geodatabase—ArcGIS Enterprise on AWS | ArcGIS Enterprise

SrinivasJasti · Answer

Thanks again for the insights.

Are you accessing the data from a local (in office machine) to the DB in AWS?

>> Everything is local (data center) with users (ArcGIS Dektop, Pro) close to the DB & App servers right now but once DB and App servers are moved to AWS. We will have to evaluate the performance of desktop clients connecting to DB directly.