In ArcGIS, by default, log file tables are used if the selection set contains 100 or more records. ArcMap, or any application that runs on top of ArcMap, such as ArcGIS for Maritime: Bathymetry, which performs selection sets, uses these log file tables. The geodatabase keeps track of large selections using the log file tables instead of the records being held in memory. The same applies when sorting, selecting, or updating records in the Bathymetry Information System (BIS) tables.
When working with results in the BIS workspace, it is best to understand the log file table configuration options so you can choose the right option for your database needs. There are four different geodatabase log file options: shared, session-based, stand-alone, and pools of session-based or stand-alone log files.
Common configuration options
Geodatabases in SQL Server use session-based log files created in the temporary database (tempdb) by default. This is the recommended setting and should be sufficient in most cases. However, if you want to change settings, see Alter log file table settings.
In most cases, the default geodatabase log file table configuration for your database management system (DBMS) should be sufficient and is the recommended setting.
Another common option is the shared log files. You would only use shared log files if you do not want to create tables in the tempdb, you have a large number of concurrent sessions, and each session connects using an individual DBMS account.
Either configuration option is acceptable for the BIS workspace, but if you choose to store the log tables in the user schema (shared log files), instead of the tempdb (session-based), be sure to give CREATE TABLE privileges to each user accessing the BIS tables.
Settings to control storage
Log file options are set using specific parameters in the SDE_server_config and SDE_dbtune tables.
For session-based log files, the DBTUNE SESSION_TEMP_TABLE parameter must be set to 1 (true) to allow the session-based log file table to be created in the tempdb. For shared log files, changing the SESSION_TEMP_TABLE parameter to 0 (false) will create the SDE_LOGFILES, SDE_LOGFILE_DATA, and SDE_SESSION<SDE_ID> tables in the connecting user's schema; hence, the user requires CREATE TABLE permission.
In SQL Server, the table created in the tempdb is in the format ##SDE_SESSION<SDE_ID>. This table is truncated when the connecting application deletes its log files, and the table is dropped when the session disconnects. When using the default setting, users do not require CREATE TABLE permission in the database for the session table to be created in the tempdb.
Your BIS workspace is now ready to store data and products and be accessed by other users.