Fix Slow Connections and Query Failures

Microsoft released two hotfixes for SQL Server. The first fix corrects a problem of slow connections to Analysis Services. The article "FIX: HTTP Connections to Analysis Services Server Computers Running Windows Server 2003 Are Slow" explains that HTTP connections to Analysis Services server computers running Microsoft Windows Server 2003 are slower than HTTP connections to Analysis Services server computers running Windows 2000. The problem occurs because of a change in Active Server Pages (ASP) behavior in Microsoft Internet Information Services (IIS) 6.0, which is included with Windows Server 2003. You can obtain the hotfix for this problem at http://support.microsoft.com/default.aspx?scid=kb;en-us;822652 .

The second fix corrects a problem of cross-database query failures. The article "FIX: Cross Database Query Fails with Error 3624 and an Assertion Occurs in the Dbtable.cpp File" describes a query failure that occurs because of a retail assertion that prevents the query from running. To improve performance and avoid excessive locking operations, SQL Server 2000 caches database locks for each connection. The database-lock cache size is fixed. If a cross-database query holds more locks than the cache size allows, SQL Server doesn't cache the additional locks. However, when the cache is available, SQL Server sometimes attempts to put the uncached locks into the cache. This attempt is what causes the retail assertion. You can obtain the hotfix for this problem at http://support.microsoft.com/default.aspx?scid=kb;en-us;330307 .