Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
You may experience performance and consistency issues with SQL Server when certain modules are loaded into SQL Server address space
Article ID: 2033238 - View products that this article applies to.
You may encounter the following symptoms when certain modules are loaded into the SQL Server process address space [sqlservr.exe]
Applications installed on a SQL Server computer can load certain modules into the SQL Server process [sqlservr.exe]. This may be done to achieve a specific business logic requirement, an enhanced functionality or for intrusion monitoring. These modules might perform unsupported activities that include detouring key Win32 API’s and SQL Server routines and calling risky API’s. In addition there could be some inherent problems within these modules that may lead to corruption of various memory structures that are key for the SQL Server process to function properly. Alll these factors can lead to various problems that are discussed in the Symptoms section of this article.
Following is a general approach that you can use to resolve these situations in your environment:
Microsoft Customer Support and Services (CSS) team has identified the following modules that can cause the symptoms specified in this article. The list will be updated when new issues are found. This list is provided to help with the identification process mentioned earlier in the Resolution section of this article. Finding the problematic module typically involves collecting an iterative set of diagnostic and tracing data for the duration of the problem.
he following modules can cause performance and stability issues when they are loaded inside the SQL Server process:
SQL Server support policy:
The use of third-party detours or similar techniques is not supported in SQL Server
For more information about the SQL Server process, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/906205/ )How to run a DLL-based COM object outside the SQL Server process
(http://support.microsoft.com/kb/243428/ )How to move extended stored procedures out of process
The following table provides more information about the products or tools that automatically check for this condition in your instance of SQL Server and in the versions of SQL Server against which the rule is evaluated.
Collapse this tableExpand this table
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
The information and the solution in this document represents the current view of Microsoft Corporation on these issues as of the date of publication. This solution is available through Microsoft or through a third-party provider. Microsoft does not specifically recommend any third-party provider or third-party solution that this article might describe. There might also be other third-party providers or third-party solutions that this article does not describe. Because Microsoft must respond to changing market conditions, this information should not be interpreted to be a commitment by Microsoft. Microsoft cannot guarantee or endorse the accuracy of any information or of any solution that is presented by Microsoft or by any mentioned third-party provider.
Microsoft makes no warranties and excludes all representations, warranties, and conditions whether express, implied, or statutory. These include but are not limited to representations, warranties, or conditions of title, non-infringement, satisfactory condition, merchantability, and fitness for a particular purpose, with regard to any service, solution, product, or any other materials or information. In no event will Microsoft be liable for any third-party solution that this article mentions.
Article ID: 2033238 - Last Review: April 2, 2012 - Revision: 4.0