The data source referenced by this stand-alone table, or data that is joined or related to this stand-alone table, has not been registered with the server. Referenced data will be copied to the server by default.
You may encounter this analyzer even though the source enterprise geodatabase or enterprise database has already been registered with the server. The reason for this is that the connection properties (user name, password, version, and so on) used by a layer or stand-alone table referencing the source enterprise geodatabase do not match the connection properties of the enterprise geodatabase registered with the server. In this case, you not only register an enterprise geodatabase, you also register the connection to the geodatabase. Registration is required for each separate connection.
For example, say you have an enterprise geodatabase named DB1 that has two versions: default and v1. You only register the connection to DB1 using the default version. If you attempt to publish a map containing layers or stand-alone tables pointing to the v1 version, and you have not registered this connection to DB1, you will encounter this analyzer. This would also occur if you have different connections to the geodatabase using different user names.
- Do nothing. The stand-alone table's source data, and all the tables related or joined to this stand-alone table, will be copied to the ArcGIS server. OLE DB data sources will be converted to file geodatabase tables.
If you are publishing a map service with either feature access or transaction-enabled WFS (WFS-T) capabilities, data will be copied to the enterprise geodatabase registered as a server-managed database. This includes data sources unsupported by feature or WFS-T services, such as shapefiles or file geodatabase feature classes. It does not include data referenced by query layers.
- If you do not wish to copy your data to the server you will need to register the original data source with the ArcGIS server.
OLE DB data sources cannot be registered with ArcGIS Server (Linux). The default behavior is that the data is always copied to the server and converted to file geodatabase tables.
Registering a data source with the server helps ensure that the server has access to all the data that the GIS service references. If a data source is not registered with the server, the data referenced by a stand-alone table in a map you are publishing will be copied to the server. If you are publishing a map service with either feature access or transaction-enabled WFS (WFS-T) capabilities, data will be copied to the server's managed database.