Select to view content in your preferred language

Is it safe to work with my Enterprise database through SQL

460
1
Jump to solution
03-29-2023 06:18 AM
Labels (2)
TomGeo
by
Occasional Contributor III

When working with database tables in ArcGIS Pro the processing seems pretty slow. I believe the culprits are the cursors (search, update, insert) and I would like to walk away from using those.

So I was wondering if I can simply switch to SQL in e.g. SQL Server Management Studio, work there and return later to ArcGIS Pro, without destroying something. By 'destroying something' I mean stuff in the GDB_*, SDE_* and i* tables.

Is it possible to work with Enterprise SQL databases purely in SQL, and if so, are there limitations on what I cannot do?

Bests Thomas

- We are living in the 21st century.
GIS moved on and nobody needs a format consisting out of at least three files! No, nobody needs shapefiles, not even for the sake of an exchange format. Folks, use GeoPackage to exchange data with other GIS!
0 Kudos
1 Solution

Accepted Solutions
George_Thompson
Esri Frequent Contributor

In general it is safe. There are some issues that can arrise with versioning, network datasets, utility network, etc.

I would recommend reviewing these doc pages: https://pro.arcgis.com/en/pro-app/latest/arcpy/get-started/executing-sql-using-an-egdb-connection.ht... & https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/sql-and-enterprise-geoda... for some more insight.

Again DO NOT  modify the repository tables via SQL, as you noted.

--- George T.

View solution in original post

1 Reply
George_Thompson
Esri Frequent Contributor

In general it is safe. There are some issues that can arrise with versioning, network datasets, utility network, etc.

I would recommend reviewing these doc pages: https://pro.arcgis.com/en/pro-app/latest/arcpy/get-started/executing-sql-using-an-egdb-connection.ht... & https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/sql-and-enterprise-geoda... for some more insight.

Again DO NOT  modify the repository tables via SQL, as you noted.

--- George T.