- You have installed Microsoft SQL Server 2005 Service Pack 2 (SP2) Cumulative Update 9 or a later SP2 cumulative update for SQL Server 2005 Analysis Services. Or, you have installed SQL Server 2005 SP3 or a later SP3 cumulative update for SQL Server 2005 Analysis Services.
- You set up a query log on the server.
- You synchronize a database on the server.
Note This problem also exists in SQL Server 2008 and in SQL Server 2008 R2. For more information, see the "More Information" section.
The fix for this issue was first released in Cumulative Update 3 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
In SQL Server 2008, there is no internal indicator to suggest to the synchronization threads that the refreshed database schema design has or has not been altered, compared with the existing database schema design. Therefore, each synchronization truncates the OlapQueryLog table. Usually, the OlapQueryLog table should be truncated when the database design (cube, dimension, measure group) has changed structure to prevent the outdated query usage information in prior revisions from misleading the aggregation design wizard to make the wrong suggestions.
One workaround is to create a user-defined "after insert" trigger on the OlapQueryLog table in your relational database to duplicate the newly inserted rows into your own table. This table can be manually maintained as you want. For example:
create trigger SaveQueryLog on OlapQueryLog after insert
as insert into dbo.CopyOfQueryLog select * from inserted
When you use the workaround, you have to manually maintain the CopyOfQueryLog table in order to keep accurate historical information on database query activity recorded. You must manually truncate the table at any time that an Analysis Services database schema change is made, or at least delete those affected objects from the CopyOfQueryLog. This maintenance is required to stop the activity against old schema revisions from influencing aggregation design on newer revisions of the Analysis Services database.
Note The name of the query log table may vary in your environment. The name is specified in the configuration setting QueryLog\QueryLogTableName.
For more information about server log files, visit the following Microsoft Developer Network (MSDN) website:
For more information about how to configure the Analysis Services query log, visit the following Microsoft TechNet website:
For more information about the list of builds that are available after SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for SQL Server 2005
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
New naming schema for Microsoft SQL Server software update packages
Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 968381 - Last Review: Aug 12, 2010 - Revision: 1