Select the product you need help with
FIX: Poor performance when table-valued functions use many table variables in SQL Server 2008 R2 or SQL Server 2008Article ID: 2566163 - View products that this article applies to. On This PageSymptomsAssume that you use many table variables in table-valued functions in Microsoft SQL Server 2008 R2 or in Microsoft SQL Server 2008. In this situation, you experience high contention for the sys.sysmultiobjrefs[2:1:103] table in the Tempdb database. Service Profile Identifier waits for the PAGELATCH_EX or PAGELATCH_SH wait types that latch the sys.sysmultiobjrefs table in large blocking chains. CauseThis issue occurs because the internal function that handles object dependency locks and then deletes rows even though, most of the time, no rows exist. Therefore, many exclusive page latches occur. ResolutionCumulative update informationCumulative Update 10 for SQL Server 2008 Service Pack 3The fix for this issue was first released in Cumulative Update 10. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:2814783 Note 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 2008 Service Pack 3 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:
(http://support.microsoft.com/kb/2814783/
)
Cumulative update package 10 for SQL Server 2008 Service Pack 32629969
(http://support.microsoft.com/kb/2629969/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was releasedSQL Server 2008 R2 Service Pack 1The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2591748 Note 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 2008 R2 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:
(http://support.microsoft.com/kb/2591748/
)
Cumulative Update package 3 for SQL Server 2008 R2 Service Pack 12567616
(http://support.microsoft.com/kb/2567616/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released SQL Server 2008 R2The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:2567713 Note 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 2008 R2 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:
(http://support.microsoft.com/kb/2567713/
)
Cumulative Update package 9 for SQL Server 2008 R2 981356
(http://support.microsoft.com/kb/981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was releasedHotfix informationA 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=support Note 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, you must have SQL Server 2008 R2 or SQL Server 2008 installed.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.SQL Server 2008 file informationCollapse this table
SQL Server 2008 R2 file informationCollapse this table
WorkaroundTo work around this issue, use one of the following methods:
StatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. More informationFor more information about table-valued user-defined functions, visit the following MSDN website: General information about table-valued user-defined functions
(http://msdn.microsoft.com/en-us/library/ms191165.aspx)
PropertiesArticle ID: 2566163 - Last Review: March 18, 2013 - Revision: 8.0 Applies to
| Article Translations
 |
Back to the top
