Usage Import Does Not Import IIS Logs from SQL Server 7.0 Database

• Microsoft SQL Server version 7.0
• Microsoft Site Server version 3.0

SYMPTOMS

When you attempt to import Web server log files using Site Server Usage Import from an ODBC data source that connects to a SQL Server 7.0 database, Usage Import does not import any records.

CAUSE

Some or all of the VARCHAR fields in the table have the TrimTrailingBlanks property set to no.

If the SQL Server Query Analyzer is used to run the SQL Server script to create the table, the default connection setting for Use ANSI nulls, paddings and warnings is on. Creating the table with this setting enabled causes the VARCHAR fields in the table to have the TrimTrailingBlanks property set to no.

Site Server Usage Import is unable to import log files from a SQL Server 7.0 database when the TrimTrailingBlanks property is set to no.

RESOLUTION

To execute the SQL Server script in the SQL Server Query Analyzer that ships with SQL Server 7.0, you must modify the SQL Server script provided with Windows NT Option pack so that set ansi_padding off appears at the top of the script. You must do this when creating the table and before logging data into the database.

If data has already been imported, you must create a new table and transfer the data to the new table. Alternatively the connection settings in SQL Server 7.0 Server Query Analyzer can be changed so that the Connection settings option Use ANSI nulls, padding and warnings is not selected.

MORE INFORMATION

When you run the script in SQL Server Query Analyzer the Connection Settings option Use ANSI nulls, padding and warnings is enabled by default. The result is that the created table will have the TrimTrailingBlanks property set to no.

ISQL_w does not use these options as the default and the VARCHAR fields are created with the TrimTrailingBlanks property set to yes.

Additional query words: SQL 7 Usage Import SP2 Site Server ODBC IIS Logging

Keywords :
Version : winnt:3.0,7.0
Platform : winnt
Issue type : kbprb