In what order do ArcSDE log file types get used?

The following diagram demonstrates the order in which ArcSDE tries to use log file tables:

The order in which ArcSDE will use types of log file tables

It is recommended you use the default log file settings for your DBMS, but if you change your log file configuration parameters, be aware there are situations in which you might end up using more than one type of log file at a time. For example, set the following parameters:

MAXSTANDALONELOGS=20

ALLOWSESSIONLOGFILE=true

LOGFILEPOOLSIZE=0

If all 20 log files are in use, when the request for another log file comes in, a session-based log file is used.

If you have the following settings in a SQL Server database, that session-based log file table is created in tempdb.

MAXSTANDALONELOGS=20

ALLOWSESSIONLOGFILE=true

LOGFILEPOOLSIZE=0

SESSION_TEMP_TABLE=1

Similarly, if you have the following settings and 15 log files are needed simultaneously, all 10 of the log file tables in the pool are used plus 5 shared log files are created.

MAXSTANDALONELOGS=0

ALLOWSESSIONLOGFILE=true

LOGFILEPOOLSIZE=10

If you have the same settings in a SQL Server database plus have SESSION_TEMP_TABLE set to 1, the 10 log file tables in the pool are used first, then the next 5 session-based log file tables are created in tempdb.