|
|
|
Logging is a critical background task that must be done. When exceptional events happen you expect to immediately trace them through available log files. A challenge with logs is that they grow, and sometimes unbounded. This impacts storage space, which must not be completely consumed.
FairCom DB provides options to keep logs within configurable sizes and purge log data as it rolls over. Two central logs can be managed in this regard.
CTSTATUS.FCS
CTSTATUS.FCS is your "go to" log for all things FairCom DB. Any exceptional event encountered by server operation is logged to this text based file. It is critical to know the immediate locaiton of this file at all times. Any time you request FairCom support, we will likely ask for this file as it contains valuable information about the running parameters of your server. This file can grow very large in some environments. For example, when logging dynamic backup events for every file, this file gets exceptionally large.
To limit the size of this file, CTSTATUS_SIZE is included as a default configured size of 32MB.
sql_server.log
sql_server.log maintains log information specifically for SQL operations. This can be dynamically enabled when needed for statement audit logging or logging stored procedure operations. For example SQL_DEBUG LOG_STMT enables statement logging.
Now, you can limit the size of sql_server.log. When it fills to the configured limit, a new file is created, the current log is marked as sql_server.bak and the prior backup purged. That is, one active and one backup log is always maintained. Configure your sql_server.log with the SQL_SERVER_LOG_SIZE configuration.
