Microsoft Addresses Handle Leak, Identity Propagation Problem, and Access Violation

Three recent Microsoft articles address a SQL Server handle leak related to repeated connects and disconnects, a problem propagating IDENTITY columns when you use the SQLXMLBulkLoad object, and a Access Violation that occurs when you use impersonation and XML for Analysis (XMLA) connection pooling. The article "FIX: Handle Leak Occurs in SQL Server When Service or Application Repeatedly Connects and Disconnects with Shared Memory Network Library" ( http://support.microsoft.com/default.aspx?scid=kb;[LN];317748 ) explains why a handle leak in the SQL Server process might occur when a service or an application quickly and repeatedly connects to and disconnects from a local SQL Server 2000 database. These leaks occur in the SQL Server 2000 Service Pack 2 (SP2) version of the shared memory network library (Dbmslpcn.dll version 2000.80.534.0). To resolve the problem, you need to obtain the latest service pack for SQL Server 2000.

The article "PRB: 'No Data Was Provided for Column' Error Message When You Propagate Identity Column with SQLXMLBulkLoad" ( http://support.microsoft.com/default.aspx?scid=kb;[LN];330582 ) reports that when you try to use the SQLXMLBulkLoad object to propagate an IDENTITY value, you'll receive an error message. The article explains several resolutions to the problem.

The article "FIX: Access Violation May Occur When You Use Impersonation and XMLA Connection Pooling" ( http://support.microsoft.com/default.aspx?scid=kb;[LN];330058 ) explains that when you use connection pooling from the XMLA SDK to impersonate users who connect to Analysis Services, the connection won't work if you try to connect to the server with a previously used connection and the application might experience an Access Violation. Microsoft has a supported fix to correct the problem and recommends that you apply the fix only to systems experiencing this specific problem.