Log file tables configuration (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 whenever a selection of a specific size is made, a reconciliation or post on a versioned database is performed, or a disconnected editing checkout is done in a client application. The log file tables store the ObjectIDs of the selected features so they can be redisplayed. This allows for faster analysis and processing of information.
In ArcGIS, by default, log file tables are used if the selection set contains 100 or more records. This selection threshold of 100 features is set in the registry. It can be changed; however, Esri does not recommend you do so. There is no proven performance reason for changing it, and doing so could cause performance problems.
Log file options are set using specific parameters in the SDE_server_config and SDE_dbtune tables.
For SQL Server, the default log file configuration is session-based log files created in the temporary database (tempdb).
Parameters in these tables are altered using the sdeconfig and sdedbtune commands, respectively. These commands and the other ArcSDE administration command line tools must be downloaded from the Esri Customer Care Portal with the ArcSDE application server. Syntax and examples for how to use the commands are provided in the ArcSDE Administration Command Reference, which is provided with the ArcSDE application server installation.
In most cases, the default ArcSDE log file table configuration for your database management system (DBMS) should be sufficient and is the recommended setting.