Latest Contributions by ShannonShields

The backup & restore tools provided by each supported DBMS platform are the preferred way to backup and restore enterprise geodatabases. An Enterprise geodatabase should be backed up according to the recovery point objectives of your organization by using the tools provided by the DBMS vendor. ... View more

Support for a Hibernate Dialect for enterprise geodatabases is not in the product plan. ... View more

There have been several new features in the 15 years since this idea was first raised that extend geodatabase functionality to either support or provide equivalency to additional dbms functionality:  query layers, support for database views, contingent values, attribute rules, sequences etc. This idea is somewhat vague in terms of which dbms components to support, and in what capacity.  ... View more

Support for column-level permissions in enterprise geodatabases is not in the product plan.  ... View more

This idea has been closed due to inactivity. ... View more

Support for a geodatabase in MySQL is not in the product plan. ... View more

ArcGIS Desktop is no longer under active development. If similar functionality is required for ArcGIS Pro, please submit a new idea. ... View more

ArcGIS Desktop is no longer under active development. If similar functionality is required for ArcGIS Pro, please submit a new idea. ... View more

When data is not versioned, and not archived it is possible to support individual insert or update or delete permissions for edits made directly from ArcGIS Pro. However, when the data is archived or registered for versioned editing the model does not support individual permissions. While it may appear that edit operations are inserts, updates, or deletes the model used by ArcGIS may not translate to the same DBMS-level operations. For example updates and deletes to versioned data are actually inserts at the database level. For a user to successfully edit using traditional or branch versioning, or non-versioned archiving, all permissions must be present. For edits made via feature services, it is the service publisher that is actually executing the edit in the database, rather than the portal user who is performing the edits.  ... View more

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