In ArcSDE, a number of configuration parameters control how much resources ArcSDE can allocate to each type of log file. Thus, it is the ArcSDE server that determines how a particular log file CREATE request will be implemented. The logic flow in this decision is best described with an illustration:



This flowchart shows some optimizations that are performed. For example, if creating a stand-alone or session table fails once, the gsrvr won't keep trying to create one for each subsequent log file CREATE request. Similarly, if the gsrvr discovers that the session pool is set to zero, it won't keep checking for an available session pool log file. Note that "8.x logfile system" refers to shared log files.

When checking for a free log file in the session pool, ArcSDE checks for orphaned log files if there are no available log files.

In addition, orphaned log files for the current user will be detected when a gsrvr starts. In ArcSDE 9 or higher, the log file's implementation is checked to determine what action will be taken. If it's a stand-alone table, it is dropped. If it's from the session log file pool, the table is made available. In ArcSDE 8.x, when an orphaned log file was found, the logfile_data table was deleted.