Skip To Content

Migrate to ArcGIS Data Store relational data store

Beginning with ArcGIS Enterprise 10.6, your portal's hosting server needs to use the relational data store provided through ArcGIS Data Store. If you want to upgrade your ArcGIS Enterprise deployment to 10.6 from a 10.5.1 or earlier release, and your hosting server currently uses an enterprise geodatabase you registered as the managed database, switch to using the relational data store before you upgrade. Use one of the following options to make this switch:

  • Preserve existing feature services by changing the existing managed database to a registered database.

    Use this option if you are happy with the existing performance and functionality of the existing hosted feature layers and if these layers are used in a large number of maps and apps in which it would be impractical for you to reset sharing and symbology and republish the apps.

  • Export data and republish your hosted feature layers.

    If you cannot keep the existing managed database as a registered database or you want even your existing hosted feature layers to have the additional functionality available when you use a relational data store, export the data from the existing hosted feature layers, delete the layers, replace the managed database with a relational data store, and republish. Be aware that this method creates new services and layers, which requires you to reset sharing and other properties on the new hosted feature layers, reapply styles to layers in maps, re-create presentations, and republish apps.

Option 1: Change the existing managed database to a registered database

You can remove the existing managed database and add it back to your ArcGIS GIS Server site as a registered database. With this option, the data in the layers is preserved in the enterprise geodatabase, the services that power the layers still exist on the GIS Server site, but the feature layers will no longer be hosted layers. Once you've configured the enterprise geodatabase as a registered database, you can install ArcGIS Data Store and configure a relational data store with your hosting server.

In this scenario, your existing geodatabase becomes a system of record rather than a data store for hosted features.

Pros of using this option include the following:

  • The styles and sharing settings applied to the feature layers persist.
  • You don't have to rebuild the apps that contain the feature layers.

Cons of using this option are as follows:

  • You must continue to maintain the enterprise geodatabase.
  • The layers continue to have limited functionality. For example, you cannot calculate values for fields in this layer in the portal map viewer or manage editor tracking or attachment settings in the portal website.
  • Although the feature layers are no longer hosted, they still run on the GIS Server site you have designated as your portal's hosting server, and the services appear in the Hosted folder in ArcGIS Server Manager. This may prove confusing to publishers or subsequent administrators.

Follow these steps to change the existing managed database to a registered database and preserve the existing feature services.

  1. Sign in to your portal as a member of the default administrator role.
  2. Set the hosting server to No hosting server.
    1. Click Edit Settings on the Organization page.
    2. Click Servers.
    3. Choose No hosting server from the Hosting Server drop-down list.
    4. Click Save.
  3. Sign in to ArcGIS Server Manager as the portal administrator and open the Data Stores page (Site > Data Stores.

Option 2: Republish

Republishing gets all your hosted feature layer data in the same data store and provides all your hosted feature layers with the same level of functionality. However, it involves a few more steps since you are replacing the existing layers. Follow the steps in each of these sections to republish:

  1. Export the data from existing hosted feature layers.
  2. Delete existing feature layers.
  3. Replace the managed database with a relational data store.
  4. Republish hosted feature layers.
  5. Reset sharing and other properties on the new hosted feature layers, resymbolize layers in maps, re-create presentations, and republish apps.

Note:

Hosted feature layers published from ArcMap or an ArcGIS Pro map to your portal can be republished from ArcMap or ArcGIS Pro, but only if the hosted feature layer was never used for editing. If any edits were made through the hosted feature layers, those edits are lost when you republish.

If you are positive no edits were made through the hosted feature layers published from ArcMap or ArcGIS Pro, you can republish from the maps in these clients to preserve layer symbology and sharing properties.

Export data

Export the data from existing hosted feature layers before you remove the managed database from the GIS Server site you have registered as your portal's hosting server. This ensures you have the most current version of the data.

The portal administrator can perform these steps to export all hosted feature layer data before you configure ArcGIS Data Store. Alternatively, each portal member who owns hosted feature layers can export the data for each of their hosted feature layers.

You must export the data from the hosted feature layers because, if any edits were made to the hosted feature layers, those edits would be lost if you republished from the original data source, such as a shapefile, CSV, or file geodatabase.

  1. Sign in to your portal.
    • If you sign in as the portal administrator, click Actions Actions next to the first portal member's name and click Manage Items. This opens a list of all content owned by this member.
    • If you sign in as the hosted feature layer owner, open My Content.
  2. Open the item details for the first hosted feature layer you want to migrate.
  3. Export to file geodatabase. Click Export > Export to FGDB.

    This creates a file geodatabase containing a feature class for each layer in the hosted feature layer. The item details for the new file geodatabase opens.

  4. Repeat these steps for every hosted feature layer you want to preserve and move to an ArcGIS Data Store relational data store.

Next, delete the existing hosted feature layers, remove the managed database, configure ArcGIS Data Store, and republish from the exported files.

Delete existing layers

Hosted feature layer names must be unique, so owners must delete the existing hosted feature layers before republishing.

Caution:

When you delete hosted feature layers, the data is also deleted from the managed database. Before you have the owners delete their hosted feature layers, create a backup of the managed database. This provides you with another copy of the data in case you find there are any problems with the data exported in the previous section.

Once the existing hosted feature layers are deleted, maps and apps that used these layers will no longer function. You must re-create them after configuring ArcGIS Data Store and republishing.

The portal administrator or hosted feature layer owners must delete the same hosted feature layers they exported in the previous section.

  1. Sign in to your portal.
    • If you sign in as the portal administrator, click Actions next to the first portal member's name and click Manage Items. This opens a list of all content owned by this member.
    • If you sign in as the hosted feature layer owner, open My Content.
  2. Check the box next to every hosted feature layer you are migrating and click Delete.

Next, remove the existing managed database and configure ArcGIS Data Store.

Replace the managed database

Remove and replace the existing managed database with ArcGIS Data Store.

First, remove the existing managed database.

  1. Sign in to ArcGIS Server Manager as an administrator.
  2. Click Site at the top of ArcGIS Server Manager.
  3. Click Data Store.
  4. Click the X next to the existing managed database to remove it from the GIS Server site.
  5. Click Yes to confirm that you want to unregister this database.

Next, install ArcGIS Data Store and configure a relational data store with the GIS Server site.

Once you have configured ArcGIS Data Store, all newly published hosted feature layer data is stored in relational data store.

Republish hosted feature layers

Publishers need to republish hosted feature layers from the file geodatabases they exported earlier. Be sure the new hosted feature layers have the same names as the old hosted feature layers.

Note:

Whoever publishes the data owns the hosted feature layer item in the portal. If you exported the data as the portal administrator but you want individual portal members (publishers) to continue to own the hosted feature layer, share the file geodatabases to a group to which publishers belong.

  1. Open the item details for an exported file geodatabase.
  2. Click Publish.
  3. Reset properties, such as sharing, editing, and delete protection, on the new hosted feature layer. See Manage hosted feature layers in the Portal for ArcGIS help for instructions.
  4. Repeat these steps for every exported file geodatabase.

Update maps and republish apps

The new hosted feature layers have different IDs than the ones they replaced. You need to replace the hosted feature layers in existing maps, reset styling in the map, re-create presentations in the maps, and republish apps that used these maps.