Log file tables configuration

Disponible avec une licence Production Mapping.

Enterprise geodatabases use log file tables to maintain lists of selected records. Records are written to log file tables for later use by the application in the following situations:

• You create a selection set of a specific size (more than 100 records in ArcMap; more than 1,000 records in ArcGIS Pro; more than 1,000 records when ObjectIDs are requested from a feature service).
• You reconcile or post to a versioned geodatabase.
• A client application checks out data for disconnected editing.

ArcGIS clients create temporary log file tables in geodatabases in SQLServer when needed.

Temporary log file tables

ArcGIS creates log files as temporary tables in the SQLServer temporary database (tempdb) whenever log file tables are needed. Tables are created per session.

Tables created for temporary log file tables

One table is created in tempdb in the format ##SDE_SESSION<SDE_ID >_<DBID>. The <SDE_ID> is the unique session ID from the SDE_process_information table. The <DBID> is the database ID from SQL Server. This table is truncated when the connecting application deletes its log files, and the table is dropped when the session disconnects. Be aware that you cannot see temporary objects in Object Explorer in Management Studio.

Permissions to use temporary log file tables

The following permissions are required to use shared log file tables in SQL Server:

• CONNECT

Remarque :

The CONNECT privilege is granted by default to all users; therefore, you only need to explicitly grant this permission if you have revoked it from PUBLIC.

Shared log files

Héritage :

Prior to ArcGIS 10.5, shared log file tables could also be used in geodatabases in SQL Server. Shared log files are shared by all sessions that connect as the same user. If you have multiple users connecting with the same user account, all those sessions insert records into and delete records from the same log file data table.

For more information, see What's new in ArcMap.