nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Tips for migrating geodatabase to new SQL Instance

Jay_Gregory

We are doing some SQL consolidation, and are migrating our current enterprise geodatabase (the current data store for Server and Portal for ArcGIS 10.3) to a different SQL Instance. Our DBO is comfortable migrating the database, users, etc. to a different instance under the same database name and setting, but I am worried about the ArcGIS for Server services, since the services seemed to be tied to the SQL Server / Instance. Am I going to have to change all the data sources in my Map Documents and republish services once the database is migrated?

Thanks!

Najděte více příspěvků označených jako

Accepted answers

All comments

JakeSkinner

Hi Jay,

You should just have to change the instance name in the Database Connection file. Your map documents will not have any broken data sources, and your map services will read the data correctly.

One thing I would double check is that the Data Store validates successfully to the new instance.

Jay_Gregory

Thanks Jake - I'll give it a try and see if that works. The reason I'm concerned is because if I look in ArcGIS Server Manager at the Service Workspace of one of my map services, I can see it is tied to the SQL Instance (see attached screenshot showing SQL Server name / instance name). I can change the instance name in the Database Connection file in ArcCatalog, but I don't see how that would change the setting in ArcGIS for Server without republishing the services via the map documents.

Thanks!

JoeHershman

Jay Gregory‌ did the process described above work? We need to do the same task and wanted to know if it is as simple as described. Once a service is published I don't think it still references the original map document so I question the Jake Skinner solution would work

Thanks

-Joe

JakeSkinner

I don't think my initial solution will work with just changing the instance in the database connection file. I believe the database connection information is stored within the layer within the MXD. You could use the following script to update your MXDs with the new database connection to the new SQL Server instance:

<SPAN class="keyword token">import</SPAN> arcpy<SPAN class="punctuation token">,</SPAN> os
<SPAN class="keyword token">from</SPAN> arcpy <SPAN class="keyword token">import</SPAN> env
<SPAN class="keyword token">from</SPAN> arcpy <SPAN class="keyword token">import</SPAN> mapping

<SPAN class="comment token"># Parent directory to MXDs.  Script will iterate through Child directories</SPAN>
env<SPAN class="punctuation token">.</SPAN>workspace <SPAN class="operator token">=</SPAN> r<SPAN class="string token">"D:\Temp\Python\MXDs"</SPAN>

<SPAN class="comment token"># New Enterprise Geodatabase</SPAN>
newDataSource <SPAN class="operator token">=</SPAN> r<SPAN class="string token">"Database Connections\SQLSERVER - DBO@GIS.sde"</SPAN>

env<SPAN class="punctuation token">.</SPAN>overwriteOutput <SPAN class="operator token">=</SPAN> <SPAN class="token boolean">True</SPAN>

<SPAN class="keyword token">for</SPAN> <SPAN class="punctuation token">(</SPAN>path<SPAN class="punctuation token">,</SPAN> dirs<SPAN class="punctuation token">,</SPAN> files<SPAN class="punctuation token">)</SPAN> <SPAN class="keyword token">in</SPAN> os<SPAN class="punctuation token">.</SPAN>walk<SPAN class="punctuation token">(</SPAN>env<SPAN class="punctuation token">.</SPAN>workspace<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">:</SPAN>
    <SPAN class="keyword token">for</SPAN> file <SPAN class="keyword token">in</SPAN> files<SPAN class="punctuation token">:</SPAN>
        <SPAN class="keyword token">if</SPAN> <SPAN class="string token">".mxd"</SPAN> <SPAN class="keyword token">in</SPAN> file<SPAN class="punctuation token">.</SPAN>lower<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">:</SPAN>
            mxd <SPAN class="operator token">=</SPAN> os<SPAN class="punctuation token">.</SPAN>path<SPAN class="punctuation token">.</SPAN>join<SPAN class="punctuation token">(</SPAN>path<SPAN class="punctuation token">,</SPAN> file<SPAN class="punctuation token">)</SPAN>
            <SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>mxd <SPAN class="operator token">+</SPAN> <SPAN class="string token">" is being processed"</SPAN><SPAN class="punctuation token">)</SPAN>
            mxd <SPAN class="operator token">=</SPAN> mapping<SPAN class="punctuation token">.</SPAN>MapDocument<SPAN class="punctuation token">(</SPAN>mxd<SPAN class="punctuation token">)</SPAN>
            <SPAN class="keyword token">for</SPAN> df <SPAN class="keyword token">in</SPAN> mapping<SPAN class="punctuation token">.</SPAN>ListDataFrames<SPAN class="punctuation token">(</SPAN>mxd<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"*"</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">:</SPAN>
                <SPAN class="keyword token">for</SPAN> lyr <SPAN class="keyword token">in</SPAN> mapping<SPAN class="punctuation token">.</SPAN>ListLayers<SPAN class="punctuation token">(</SPAN>mxd<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"*"</SPAN><SPAN class="punctuation token">,</SPAN> df<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">:</SPAN>
                    <SPAN class="keyword token">try</SPAN><SPAN class="punctuation token">:</SPAN>
                        <SPAN class="keyword token">if</SPAN> lyr<SPAN class="punctuation token">.</SPAN>supports<SPAN class="punctuation token">(</SPAN><SPAN class="string token">"DATASOURCE"</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">:</SPAN>
                            <SPAN class="keyword token">if</SPAN> lyr<SPAN class="punctuation token">.</SPAN>serviceProperties<SPAN class="punctuation token">[</SPAN><SPAN class="string token">'Database'</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">:</SPAN>
                                <SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="string token">"\tUpdating "</SPAN> <SPAN class="operator token">+</SPAN> str<SPAN class="punctuation token">(</SPAN>lyr<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN>
                                lyr<SPAN class="punctuation token">.</SPAN>replaceDataSource<SPAN class="punctuation token">(</SPAN>newDataSource<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"SDE_WORKSPACE"</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="string token">""</SPAN><SPAN class="punctuation token">)</SPAN>
                                <SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="string token">"\tSuccessfully updated data source"</SPAN><SPAN class="punctuation token">)</SPAN>
                    <SPAN class="keyword token">except</SPAN> AttributeError<SPAN class="punctuation token">:</SPAN>
                        <SPAN class="keyword token">pass</SPAN>
            mxd<SPAN class="punctuation token">.</SPAN>save<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>

<SPAN class="keyword token">del</SPAN> mxd<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

The services will have to be re-published afterwards as well.

JoeHershman

I already have a script that changes the maps data source of maps, so that parts not an issue. Even have a script to republish the services. But what we really were hoping is to be able to make the database move without the need to republish services.

One big issue is that in Portal when you do a republish of a service the item id changes (so it is actually creating a new Portal Item, event though the service endpoint doesn't change). So Web Maps will break because they reference the Portal Item not just the service endpoint, we have not tried in 10.7 so maybe that is no longer the case, but in previous versions that is what we saw happen. That means all our web maps need to be re-created, which would be a lot of work

Thanks

-Joe

Jay_Gregory

At this point I kind of forget what I did. I might have just republished everything, although at this point I wouldn't be able to do that because it would generate new item ids for all my Portal content (we had JUST started using Portal three years ago so it wasn't as much of an issue). I could involve Esri support if possible.

JakeSkinner

One big issue is that in Portal when you do a republish of a service the item id changes

This should not occur if you are overwriting the service when you republish. What version of Portal and Server are you using?

JoeHershman

I was incorrect in my description after discussing with someone involved in the process. If during a republish you change a property of the service it would seem it creates a new item. What does occur on republish is that settings get overwritten. So if you have configured the popups this all needs to be redone. We do have a tool to make these changes external to Portal and update the items, however, it will be a significant pain to do with all our web maps

BillFox

AGOL vs Portal but this issue may be involved.

https://community.esri.com/thread/219119-arcgis-online-overwrite-feature-service-from-arcgis-enterprise-and-new-layer-does-not-show-up-in-agol-web-map

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.