Bug
Connection and rendering issues are encountered after migrating an on-premises enterprise geodatabase in SQL Server to Azure SQL Database.
| Bug ID Number | BUG-000132592 |
|---|---|
| Submitted | July 27, 2020 |
| Last Modified | June 5, 2024 |
| Applies to | ArcSDE/Enterprise Geodatabase |
| Version found | 10.8 |
| Operating System | Windows OS |
| Operating System Version | 2019 64 Bit |
| Status | Known Limit |
Additional Information
This behavior is expected and has been explained in the technical article, 'How To: Migrate an on-premises enterprise geodatabase in SQL Server to Azure SQL Database'- https://support.esri.com/en/Technical-Article/000023991.Workaround
Use one of the following workarounds:- Ensure the original empty geodatabase is created in SQL Azure first, if the intended production target is SQL Azure.
- It is recommended to use Pro to upgrade the geodatabase.
- Replace the sde_purge_processes stored procedure using SQL.
Note: Workaround 2 and 3 must be tested thoroughly before being applied to a production environment especially if the database is using a collation other than SQL_Latin1_General_CP1_CI_AS.
Steps to Reproduce
Bug ID: BUG-000132592
Software:
- ArcSDE/Enterprise Geodatabase
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App