Solved! Go to Solution.
Hi Wolseley,
Thinking of a workaround, a follow-up question please...
Are these ~30 file geodatabases created only for publishing map services, or for other users as well?
In case they are only for map services, and can be placed on the AGS Server machine(s), map services could receive the updates directly from the replica (synchronization), then you would not need to overwrite them.
Referring to the webhelp: Considerations for file geodatabases:
"File geodatabases are intended for read-only use with ArcGIS Server. Because of this, in scenarios where the file geodatabase is a publication geodatabase (in one-way replication workflows), replica synchronization needs to occur during periods of inactivity in the map service or by releasing the file geodatabase from being used by the map service."
Regards,
Mandar
Yes,
I believe, we are discussing the option of 'registering data with the server'.
If the file geodatabase is not registered with the server, the server creates its own copy for every map service. Hence there is a need to overwrite the service when the original fgdb is updated.
When you register the file geodatabase with the server, there would be no need to overwrite the service (since the server will use the same fgdb, there will not be a server copy).
Is your file geodatabase registered with the server?
(I was referring to this option and additional considerations when using this option.)
Some additional webhelp pointers:
Determining how the server will access service data:
Registering your data with ArcGIS Server using Manager
Regards,
Mandar
To register a file geodatabase on the 'Data Store' tab, use the '+' sign on the "Registered Folders" frame.
Attached screenshot for reference.
[ATTACH=CONFIG]25851[/ATTACH]