When you create and then run a SQL Server trace in Microsoft SQL Server 2012, you experience poor performance in SQL Server 2012.
The issue occurs because the Sp_TraceGetdata stored procedure consumes excessive memory resources when you run the trace. Therefore, the size of the procedure cache grows continuously, and the procedure cache cannot cache object plans.
Cumulative update information
Cumulative update 3 for SQL Server 2012 Service SP1The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2812412 Cumulative update package 3 for SQL Server 2012 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 SP1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around the issue, stop and then restart the trace.
Article ID: 2803529 - Last Review: Mar 18, 2013 - Revision: 1
Microsoft SQL Server 2012 Service Pack 1, Microsoft SQL Server 2012 Developer, Microsoft SQL Server 2012 Enterprise, Microsoft SQL Server 2012 Standard