Latest Contributions by ShannonShields

Feature datasets are specific to storing spatial data that participates in a controller dataset. Non-spatial tables are not part controller datasets and therefore will not be part of feature datasets. For more information on feature datasets and their intended use please see https://pro.arcgis.com/en/pro-app/latest/help/data/feature-datasets/feature-datasets-in-arcgis-pro.htm. ... View more

We do not have any plans to modify the ArcGIS data model to support multiple entity types in a single feature class. ... View more

This is functionality that is already available to a DBA. There are many tools available to perform security audits at the database level. ... View more

This information is available on the Database Properties under Enterprise License Expiration https://pro.arcgis.com/en/pro-app/latest/help/data/databases/database-properties-dialog.htm   ... View more

The ability to grant permission on an object that the connected user does not own is not supported in a geodatabase. The supported functionality from deprecated ArcSDE administration commands has been implemented. Functions that were not moved into GP tools are not supported. ... View more

This applied to upgrade behavior that is now the default in SQL Server geodatabases. It has been documented in What's New, blog posts, and core documentation. ... View more

The SDO_GEOMETRY type cannot store all types of geometric elements that ArcGIS storage must support. These additional elements are written to the SE_ANNO_CAD_DATA field for Oracle Spatial data, the GDB_GEOMATTR_DATA field for SQL Server Geometry & Geography data, and PostgreSQL PostGIS data. These fields are not optional for data that is registered with the geodatabase. ... View more

The SDO_GEOMETRY type cannot store all types of geometric elements that ArcGIS storage must support. These additional elements are written to the SE_ANNO_CAD_DATA field for Oracle Spatial data, the GDB_GEOMATTR_DATA field for SQL Server Geometry & Geography data, and PostgreSQL PostGIS data. These fields are not optional for data that is registered with the geodatabase. ... View more

Logs can be generated to capture communication between the DBMS and individual clients. These will not be aggregated and automatically stored within the geodatabase itself. ... View more

Tools to replace commonly used ArcSDE commands have been created and have been available for several releases. ... View more

ArcGIS supports connecting to Azure SQL Database using Microsoft Entra Password, Entra MFA or Entra Integrated.  https://pro.arcgis.com/en/pro-app/latest/help/data/databases/connect-sqlserver.htm   ... View more

Licensing for Workgroup geodatabases is no longer available and there are no plans to support a geodatabase implementation on Oracle Database XE. ... View more

Stephen, changing the .sde file in a project is not going to change the connection information stored in each individual layer. If you are using the UpdateConnectionProperties to swap out the .sde file, that is only changing the .sde file in the project. You'd have to update the individual layers one at a time. However, when using Entra MFA the user is still going to need to supply their credentials at least once. If all the layers are from the same database, the first prompt to supply credentials should then apply to all the remaining layers. Have you tried testing simply creating a project with a few layers pulled from a single connection made with MFA and with 'save user/password' unchecked and having another user open the project? In my testing (using ArcGIS Pro 3.3) I am only prompted for my MFA credentials once when opening a project containing layers that I have permission to see but that were added by another MFA login. -Shannon ... View more

Annette, when tables or feature classes are part of a SQL Server geodatabase and created via ArcGIS then the ObjectID values are managed/generated by two stored procedures and a table that allow for IDs to be generated in larger blocks, and also manage multiple simultaneous users adding features. There is a stored procedure sde.next_rowid() (or dbo.next_rowid) that takes a geodatabase table/feature class as input and returns the next value for the ObjectID field. It uses the related stored procedures and ID table so IDs do not get reused and the sequence of subsequent IDs is preserved. That might be an option for the ETL operation. But, do these tables need to be registered with the geodatabase? You can still interact with them in a read-only capacity without them having to be registered. Then you are free to manage a unique identifier field however you want - you can make the ObjectID an Identity field and have it auto-increment that way. -Shannon ... View more

Using the JOIN syntax makes things a little easier to understand - you can see what each join is based on, and you can also specify that all records in a table are returned even with no matches (those NULL records you indicated were problematic) by using an outer join - LEFT JOIN or RIGHT JOIN syntax. -Shannon ... View more