Configuring Log Server database options

Open the Database tab of the Email Log Server Configuration utility to configure how Log Server works with the Log Database.

Steps

  1. Choose a Log Insertion Method from the following options:

    • Open Database Connectivity (ODBC): Inserts records into the database individually, using a database driver to manage data between Log Server and Log Database.

    • Bulk Copy Program (BCP) (recommended): Inserts records into the Log Database in groups called batches. This option is recommended because it offers better efficiency than ODBC insertion.

    Note: The BCP option is available only if you install the SQL Server Client Tools on the Log Server machine.
    Important: If you plan to establish an encrypted database connection, you cannot use the BCP insertion method. Not using the batch method may affect Log Database performance. See Setting up an encrypted database connection, for information about encrypted connections.
  2. Select the Log Database for storing email traffic information from the email security software; click the button Connection.

    See Setting up the database connection page.

    ODBC Data Source Name (DSN) and ODBC Login Name display the settings established for the database connection.

  3. If you chose BCP as the log insertion method in step 1, set the following options If you chose ODBC as the log insertion method, skip this step.
    Option Description
    BCP file path location

    Directory path for storing BCP files. This must be a path where the Log Server service account has read and write access.

    This option is available only if Log Server is installed on the Log Database machine, or if the SQL Server Client Tools are installed on the Log Server machine.
    BCP file creation rate

    Maximum number of minutes Log Server spends placing records into a batch file before closing that batch file and creating a new one.

    This setting works in combination with the batch size setting: Log Server creates a new batch file as soon as either limit is reached.
    BCP maximum batch size

    Maximum number of log records before a new batch file is created.

    This setting works in combination with the creation rate setting: Log Server creates a new batch file as soon as either limit is reached.

    The BCP option for inserting records into the Log Database in batches cannot be used when you encrypt your database connection. See Setting up an encrypted database connection.

  4. Set the Maximum connections allowed to indicate how many internal connections can be made between Log Server and the database engine. The options available depend on the database engine being used.
    • SQL Server Express: Set to a number from 4 to 32, as appropriate for your SQL Server Express license.
    • SQL Server: Set to a number from 4 to 50, as appropriate for your SQL Server license. The minimum number of connections depends on the selected log insertion method.
      Note: Increasing the number of connections can increase processing speed for log records, but may impact other processes in the network that use the same SQL Server. In most cases, you should set the number of connections to fewer than 20. Contact your Database Administrator for assistance.
  5. Check or uncheck Enhanced logging to enable or disable this option, which controls how Log Server resumes logging after it has been stopped.

    When this option is deselected (the default), Log Server begins processing at the beginning of the oldest log cache file after a stop. This could result in some duplicate entries in the Log Database, but speeds Log Server processing.

    When this option is checked, Log Server tracks its location in the active log cache file. After a restart, Log Server resumes processing where it stopped. Enhanced logging can slow Log Server processing.

  6. Click Apply. The changes are saved.
  7. Stop and restart Log Server. See Stopping and starting Log Server.