About managed database in Server

487
5
Jump to solution
01-27-2020 09:28 AM
SoratoSouza_e_Silva
Occasional Contributor II

Hi,

What is the difference between managed and registered database? What is the managed database for? When should I not use the enterprise database as managed?

Thank´s

Tags (1)
1 Solution

Accepted Solutions
KimPeter
Occasional Contributor III

Hi Sorato,

If you're wondering about the registration options in ArcGIS Server Manager specifically, registering a managed database here means you provide and maintain an enterprise geodatabase into which data will be copied when you publish a feature service to that stand-alone ArcGIS Server site.  (In ArcGIS Pro, you need to choose the Copy data option when publishing.)

Publishing to an ArcGIS Server site that has a managed database that you provide is a narrow use case.  A managed database is useful when you need to get on-premises data into a geodatabase in the cloud or outside your firewall. When you publish a feature service to an ArcGIS Server site that has a managed database, the data is copied from the source into the managed database. The service accesses the data that was copied to the managed database, not the source data.

Registering a database with the ArcGIS Server site is a far more common workflow. You would do this any time you want the services on your ArcGIS Server site (stand-alone or federated) to access the source data in your enterprise geodatabase or database. The data stays in this database and is not copied when you publish. (In ArcGIS Pro, you need to choose to reference registered data when you publish.) That means people who work with the data through a database connection and those who access the published services are working with the same data.

View solution in original post

5 Replies
DerekLaw
Community Moderator

Hi Sorato,

Please review this esri whitepaper, Data in ArcGIS: User Managed and ArcGIS Managed

Hope this helps,

KimPeter
Occasional Contributor III

Hi Sorato,

If you're wondering about the registration options in ArcGIS Server Manager specifically, registering a managed database here means you provide and maintain an enterprise geodatabase into which data will be copied when you publish a feature service to that stand-alone ArcGIS Server site.  (In ArcGIS Pro, you need to choose the Copy data option when publishing.)

Publishing to an ArcGIS Server site that has a managed database that you provide is a narrow use case.  A managed database is useful when you need to get on-premises data into a geodatabase in the cloud or outside your firewall. When you publish a feature service to an ArcGIS Server site that has a managed database, the data is copied from the source into the managed database. The service accesses the data that was copied to the managed database, not the source data.

Registering a database with the ArcGIS Server site is a far more common workflow. You would do this any time you want the services on your ArcGIS Server site (stand-alone or federated) to access the source data in your enterprise geodatabase or database. The data stays in this database and is not copied when you publish. (In ArcGIS Pro, you need to choose to reference registered data when you publish.) That means people who work with the data through a database connection and those who access the published services are working with the same data.

SoratoSouza_e_Silva
Occasional Contributor II

Hi, kpeter-esristaff 

Can I use a managed database, for example, a Postgres and also an relational Arcgis DataStore in the same ArcGIS Server Manager?

Thank´s

0 Kudos
KimPeter
Occasional Contributor III

No.  The relational ArcGIS Data Store is for use with the portal's hosting server. A managed database that you maintain and add can be used with a stand-alone or federated server only, not with the hosting server. 

SoratoSouza_e_Silva
Occasional Contributor II

Thank you. I am very grateful for your explanations