Database migration from SQL Server 2017 to Postgres

yockee — Fri, 17 Feb 2023 02:16:14 GMT

Hi,

I want to migrate from EGDB Sql Server into EGDB Postgresql. Here is the condition:

- EGDB Sql Server (non versioning) reside on VM. The size of the EGDB is not large, only 50GB

- EGDB Postgresql will be on the cloud

Questions:

1. What are the considerations I should take ? Is copy feature class to feature class suffice enough ?

2. There are BLOB fields containing photos. Will it be a smooth copying (say, using Export or Import tools or maybe feature class to feature class) between different databases ?

3. How can I do this in the quickest and most correct way possible ?

Thanks

Re: Database migration from SQL Server 2017 to Postgres

George_Thompson — Fri, 17 Feb 2023 11:47:38 GMT

The best (and safest) way I have seen this done is using the ArcGIS tools (copy / paste) from the old SQL Server (data owners) to the new PostgreSQL in the schemas that you want. Using that workflow will allow the conversion into the correct repository ("SDE / GDB") tables.

When you copy of the feature classes with the blobs, it should copy them over to the new EGDB without issue.

This is the quickest and safest way that I have seen.

No idea how long it will take to copy. It may be a safe idea to copy to a file geodatabase as a backup.

Referenced from my post here: https://community.esri.com/t5/geodatabase-questions/database-migration-from-oracle-12c-to-postgres/m-p/1256932/highlight/true#M8266

topic Database migration from SQL Server 2017 to Postgres in Geodatabase Questions

Database migration from SQL Server 2017 to Postgres

Re: Database migration from SQL Server 2017 to Postgres