Skip to main content
Frank Stauffer
Participating Frequently
Oct 2, 2025 2:08 PM UTC

Migrating ArcGIS Enterprise geodatabase from SQL Server 2016 to SQL Server 2022 any considerations for our Cityworks deployment

We are in the process of migrating our ArcGIS Enterprise geodatabase from SQL Server 2016 to SQL Server 2022.

 

It looks like we need to repoint and republish map services consumed by Cityworks, but I was not sure if there are any Cityworks configurations that tie directly to our Enterprise geodatabase.

 

From a Cityworks perspective, are there any configuration changes in the Designer or Admin panels we need to make, or other considerations that need to be taken into account?

 

I have not done a SQL Server migration before any insights would be helpful.

Thanks

    2 replies

    Steven Sushka
    Known Participant
    Oct 2, 2025 4:11 PM UTC

    @frank stauffer? We haven't had direct GDB connections for a while, which was back in our Desktop days. All new Cityworks web versions work with GIS web services regardless of the underlying RDBMS hosting the enterprise GDB - i.e., it could be a PostgreSQL GDB if you wanted, even though we only support SQL Server and Oracle for Cityworks. Only custom reports or integrations you've built that could still directly pull data from the enterprise GDB. Otherwise, just be sure to update the DB compatibility version to SQL Server 2022 once you restore the SQL Server 2016 .bak in the SQL Server 2022 instance from the SQL Server 2016 instance.

    Translate
    Frank StaufferAuthor
    Participating Frequently
    Oct 2, 2025 4:11 PM UTC

    @steven sushka? Thank you for your insight. It did not seem like there should be any direct connection to the GDB, but I wanted to double-check.

    We do have some custom Crystal Reports... I am waiting to hear back from our administrator if our reports are pulling data from the database we are planning to upgrade, or if they are only pulling data from the Cityworks SQL instance.

    Translate
    Terms & ConditionsAccessibility statement