Changes to the SQL Server compatibility mode cause sluggish performance in the user interface


Webtrends Analytics 8.5


It is necessary to change the SQL compatibility mode to a lower level (for example setting MS SQL 2005 to run in MS SQL 2000 mode). After making the change, Webtrends performs poorly when updating configuration options such as custom report hit filters.

Reset the compatibility mode back to the level used during install.
On the server running SQL, perform the following steps.

1. Open a command prompt by going to “Start” > “Run,” and type cmd and hit Enter.

2. Type sqlcmd and hit Enter to open the SQL command shell.

3. Type the following:

EXEC sp_dbcmptlevel wtmaster, 90;

Hit Enter, then type GO and hit Enter again.

4. Type the following:

EXEC sp_dbcmptlevel wt_sched, 90;

Hit Enter, then type GO and hit Enter again.

5. Type exit and hit Enter to end the session.

6. Close all browsers.

7. Restart all Webtrends services on all Webtrends servers.

Using a compatibility mode other than that used during the installation causes communications issues with the SQL server. While the user interface is still usable, it may be sluggish.

Following is a list of compatibility modes in SQL, the default for the version of SQL that comes with 8.5 is 90:

60 = SQL Server 6.0
65 = SQL Server 6.5
70 = SQL Server 7.0
80 = SQL Server 2000
90 = SQL Server 2005

Further information:
Always check the support guidelines for the version of Webtrends you are using. Most require a dedicated SQL server running in the default instance. Not all versions of MS SQL are supported. There should be no need to downgrade or change the compatibility level in MS SQL.