Article ID: 2458438 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release.
When you use Microsoft SQL Server Profiler to monitor an instance of SQL Server 2008 R2 Analysis Services, one or more of the following issues may occur.
When an Execute MDX Script trace event is triggered by a session other than Analysis Services, the ConnectionID and SPID attributes are incorrectly reported as 0. Therefore, the session that triggers the event is not logged.
The Execute MDX Script Current event that is triggered for every sub command of a script incorrectly contains the whole script in the TextData column. Therefore, the script part that is related to the event is not indicated.
Current trace information does not indicate which resources are consumed by a particular command or by a query.
In SQL Server Profiler, the Locks category that contains lock operation information logs only the following two events:
This update introduces some new trace events to SQL Server Profiler to resolve these issues. For more information, see the "More Information" section.
Service pack information for SQL Server 2008 R2To resolve this problem, obtain the latest service pack for SQL Server 2008 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2527041Note This fix for issue was first released in SQL Server 2008 R2 Service Pack 1.
(http://support.microsoft.com/kb/2527041/ )How to obtain the latest service pack for SQL Server 2008 R2
The new Execute MDX Script Command eventThe current SQL Server 2008 R2 Analysis Services supports the following events for the Execute MDX script operation:
New trace events to track resource usageCurrent trace information does not indicate which resources are consumed by a particular command. After you install this update, the new Resource Usage event class is introduced to include information about CPU usage and I/O operations. This information is logged in a separate event or in additional columns on the Command End event or on the Query End event. The following information can be included in the TextData column of the event:
Trace events that track any locking activitiesSQL Server 2008 R2 Analysis Services supports the following two events that track any locking activities:
LockListThe LockList node contains the following information:
The following is an example of the LockList node:
In this example, the transaction requests three locks, obtains one, and waits for the second lock.
WaitListThe WaitList node lists the waiting transactions that are ahead of the current transaction. The following is an example of the WaitList node:
HoldListThe HoldList node lists transactions that hold a lock that the current transaction tries to obtain. The following is an example of the HoldList node:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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:
935897For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/935897/ )An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
822499For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/ )New naming schema for Microsoft SQL Server software update packages
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates