Specify how log records are processed into the database

Click Log Record Creation to specify how Log Server adds records to the Log Database.

ODBC (Open Database Connectivity) inserts records into the database individually, using a database driver to manage data between Log Server and Log Database.
If you select this option, also set the Maximum number of connections to specify how many internal connections can be made between Log Server and the database engine.

Select a value between 4 and 50, as appropriate for your SQL Server license.

Note: Increasing the number of connections can increase processing speed for log records, but could 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.

BCP (Bulk Copy Program) (recommended) inserts records into the Log Database in batches. This option offers better efficiency than ODBC insertion, and is selected by default if the bcp.exe file is found on the machine.

The BCP option is available only if you install the SQL Server Native Client and Command Line Utilities on the Log Server machine. To allow the BCP option to be available by default, when Log Server is installed on a machine, the SQL tools are installed also.

BCP cannot be used when SQL Server SSL encryption is used.

If you select the BCP option, also specify:

Option	Description
BCP file location	Directory path for storing BCP files. Log Server must have read and write access to the location. (The default folder is C:\Program Files\Websense\Web Security\bin\Cache\BCP.) After entering the path, click Test Location to verify that the location is accessible.
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.
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.

Option

Description

BCP file location

Directory path for storing BCP files. Log Server must have read and write access to the location. (The default folder is C:\Program Files\Websense\Web Security\bin\Cache\BCP.)

After entering the path, click Test Location to verify that the location is accessible.

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.

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.

After selecting a log record insertion method, click Log Cache Files to specify where and how log cache files are created. These provide temporary storage for log records that have not yet been processed into the Log Database or moved to BCP files.

Steps

For Cache location, indicate where on the Log Server machine logging cache files are stored (C:\Program Files\Websense\Web Security\bin\Cache\, by default).
Click Test Location to verify that the path is accessible.
For Cache file creation rate, indicate the maximum number of minutes (1, by default) Log Server should spend sending Internet access information to a log cache file before closing it and creating a new file.
For Maximum cache file size, specify how large a log cache file should be before Log Server closes it and creates a new one.

The file creation rate and maximum file size settings work in combination: Log Server creates a new log cache file as soon as either limit is reached.