Article ID: 2920987 - View products that this article applies to.
Assume that you run a stored procedure on a database that passes many table-valued parameters in Microsoft SQL Server 2008 R2, SQL Server 2012, SQL Server 2008, or SQL Server 2014. In this situation, you experience high contention for the sys.sysprivs(2:1:101) and sys.syssoftobjrefs tables in the Tempdb database.
Note This issue also occurs when there is very heavy usage of Tempdb objects. For example, Tempdb objects are created and dropped frequently.
Service Pack informationTo resolve this issue, apply Microsoft SQL Server 2008 SP4. For more information about how to obtain SQL Server 2008 SP4, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/2979596/ )SQL Server 2008 Service Pack 4 release information
Hotfix for SQL Server 2008 SP3A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Cumulative update informationThe issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 1 for SQL Server 2014
|kbfix kbsurveynew kbexpertiseadvanced kbhotfixserver kbautohotfix KB2920987|