I know in the past I have risked corrupting my ESRI Enterprise Geodatabase as I have added/removed tables using SQL, this was a hard learned lesson as I didnt know there were references to these tables, in other tables (table registry etc).
When it comes to adding or dropping fields, can I do this using SQL rather than using the arcpy or geoprocessing tools? I am finding my map services are creating locks on my datasets, and the tools fail to run.
I know in the past if I use SQL this will bypass the locks and fields can be added/removed with no issues, but I am now fearful that as this is an ESRI database, could this have knock on effects that come back to bite me later.
Any thoughts with this?
Solved! Go to Solution.
I would recommend disabling schema locking. This will allow you to make schema changes without having to stop the service: