SQL Server Q&A

Symptoms
If a query that returns many bit columns is run as a parallel query and the row size passed through one of the Parallelism physical operators in the plan exceeds approximately 8 KB in size, a handled access violation may occur.
Resolution
A Parallelism physical operator is limited to handling a row size greater than approximately 8 KB in size, and normally such plans are excluded from being run as a parallel plan. Due to a bug in the calculation of the row size when handling bit columns, the query is incorrectly allowed to run in parallel but overflows a buffer allocated for transferring the data between threads.

Symptoms
When you run a query in Microsoft SQL Server 2000 64-bit, you may experience an 8621 error condition. An 8621 error condition may cause the SQL Server 2000 64-bit program to close unexpectedly. When this problem occurs, the following messages are logged in the SQL Server error log:

2004-04-05 10:35:58.86 spid5104/05/04 10:35:58 Stack Overflow Dump not possible – Exception c00000fd E at 0×00000000007051E42004-04-05 10:35:58.86 spid51Address=7051e4 Exception Code = c00000fd2004-04-05 10:36:01.21 spid51<The query text follows.>…2004-04-05 10:37:07.82 spid512004-04-05 10:37:07.82 spid51TotalPhysicalMemory = 34349801472, AvailablePhysicalMemory = 70914375682004-04-05 10:37:07.82 spid51AvailableVirtualMemory = 7643227004928, AvailablePagingFile = 32936615936
This behavior has been observed in Microsoft SQL Server 2000 32-bit and in Microsoft SQL Server 2000 64-bit.
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211?(http://support.microsoft.com/kb/290211/) How to obtain the latest SQL Server 2000 service pack
Hotfix information The English version of this fix has the file attributes (or later) 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 tool in Control Panel.
SQL Server 2000 32-bit (x86)

DateTimeVersionSizeFile name————————————————————————-31-May-200318:452000.80.818.078,400Console.exe25-Mar-200422:272000.80.928.0315,968Custtask.dll30-Jan-200416:292000.80.911.033,340Dbmslpcn.dll25-Apr-200302:12786,432Distmdl.ldf25-Apr-200302:122,359,296Distmdl.mdf30-Jan-200301:55180Drop_repl_hotfix.sql12-Sep-200303:262000.80.859.01,905,216Dtspkg.dll26-Aug-200320:162000.80.854.0528,960Dtspump.dll23-Jun-200322:402000.80.837.01,557,052Dtsui.dll23-Jun-200322:402000.80.837.0639,552Dtswiz.dll24-Apr-200302:51747,927Instdist.sql03-May-200301:561,581Inst_repl_hotfix.sql30-Jan-200416:292000.80.911.090,692Msgprox.dll01-Apr-200302:071,873Odsole.sql30-Jan-200416:292000.80.911.062,024Odsole70.dll30-Jan-200416:292000.80.911.025,144Opends60.dll07-May-200318:47132,096Opends60.pdb30-Jan-200416:282000.80.911.057,904Osql.exe02-Apr-200323:152000.80.797.0279,104Pfutil80.dll04-Aug-200318:17550,780Procsyst.sql12-Sep-200300:3712,305Qfe469315.sql22-May-200322:5719,195Qfe469571.sql25-Mar-200421:031,104,848Replmerg.sql30-Jan-200416:292000.80.911.0221,768Replprov.dll30-Jan-200416:292000.80.911.0307,784Replrec.dll29-Jan-200423:242000.80.911.0159,813Replres.rll06-Sep-200300:001,087,150Replsys.sql13-Aug-200316:28986,603Repltran.sql30-Jan-200416:292000.80.911.0287,304Rinitcom.dll25-Mar-200422:272000.80.928.066,112Semmap.dll30-Jan-200416:292000.80.911.057,916Semnt.dll29-Jul-200320:132000.80.819.0492,096Semobj.dll31-May-200318:272000.80.818.0172,032Semobj.rll02-Jan-200419:422000.80.904.053,832Snapshot.exe09-Dec-200320:07117,834Sp3_serv_uni.sql05-Feb-200400:462000.80.913.028,672Sqlagent.dll05-Feb-200400:472000.80.913.0311,872Sqlagent.exe19-Feb-200418:022000.80.916.0168,001Sqlakw32.dll12-Mar-200404:342000.80.923.033,344Sqlctr80.dll30-Jan-200416:292000.80.911.04,215,360Sqldmo.dll07-Apr-200317:4425,172Sqldumper.exe29-Jan-200423:172000.80.911.028,672Sqlevn70.rll05-Mar-200417:132000.80.922.0180,792Sqlmap70.dll03-Sep-200302:562000.80.857.0188,992Sqlmmc.dll02-Sep-200323:032000.80.857.0479,232Sqlmmc.rll22-Oct-200300:082000.80.871.0401,984Sqlqry.dll30-Jan-200416:292000.80.911.057,920Sqlrepss.dll06-Apr-200420:062000.80.929.07,622,737Sqlservr.exe06-Apr-200420:0812,788,736Sqlservr.pdb30-Jan-200416:292000.80.911.0590,396Sqlsort.dll30-Jan-200416:292000.80.911.045,644Sqlvdi.dll30-Jan-200416:292000.80.911.0106,588Sqsrvres.dll30-Jan-200416:292000.80.911.033,340Ssmslpcn.dll30-Jan-200416:292000.80.911.082,492Ssnetlib.dll30-Jan-200416:292000.80.911.025,148Ssnmpn70.dll28-Oct-200304:212000.80.873.0123,456Stardds.dll30-Jan-200416:292000.80.911.0158,240Svrnetcn.dll30-Jan-200416:292000.80.911.076,416Svrnetcn.exe30-Apr-200323:522000.80.816.045,132Ums.dll30-Apr-200323:52132,096Ums.pdb30-Jan-200416:292000.80.911.098,872Xpweb70.dll
SQL Server 2000 64-bit (IA-64)

DateTimeVersionSizeFile name—————————————————————————16-Jul-200303:522000.80.818.056,832Dbmslpcn.dll03-May-200301:561,581Inst_repl_hotfix.sql11-Mar-200303:422000.80.782.0185,856Msgprox.dll16-Jul-200318:552000.80.818.0150,528Odsole70.dll16-Jul-200319:152000.80.818.0148,992Osql.exe26-Mar-200422:561,104,848Replmerg.sql11-Mar-200303:422000.80.782.0533,504Replprov.dll11-Mar-200303:422000.80.782.0767,488Replrec.dll27-Mar-200400:042000.80.928.0160,768Semmap.dll13-Mar-200408:072000.80.923.032,256Sqlctr80.dll01-Jun-200322:182000.80.818.0 13,845,504Sqldmo.dll16-Jul-200319:1339,936Sqldumper.exe11-Mar-200303:432000.80.782.023,040Sqlmap70.dll11-Mar-200303:432000.80.782.0152,064Sqlrepss.dll07-Apr-200415:422000.80.929.0 24,913,920Sqlservr.exe07-Apr-200415:4520,933,632Sqlservr.pdb11-Mar-200303:432000.80.782.0120,320Sqlvdi.dll16-Jul-200303:522000.80.818.053,760Ssmslpcn.dll01-Jun-200321:512000.80.818.0254,976Ssnetlib.dll02-Jun-200300:412000.80.818.020,992Ssnmpn70.dll01-Jun-200321:482000.80.818.0430,080Svrnetcn.dll01-Jun-200321:482000.80.818.0185,856Svrnetcn.exe31-Mar-200321:272000.80.778.0186,368Xpweb70.dllNoteBecause of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Symptoms
After you install a 64-bit version of Microsoft SQL Server 2005 on a 64-bit version of a Microsoft Windows operating system, the 32-bit entries for SQL Native Client Configuration and for SQL Server 2005 Network Configuration appear in SQL Server Configuration Manager.
Resolution
Some tools that are installed together with a 64-bit version of SQL Server 2005 are available only as 32-bit versions. When you install a 64-bit version of SQL Server 2005, the 32-bit versions of the following tools are installed:SQL Server Management StudioSQL Server Configuration ManagerDatabase Engine Tuning AdvisorThe following entries appear in SQL Server Configuration Manager:SQL Server 2005 Network Configuration (32bit)SQL Native Client Configuration (32bit)SQL Server 2005 Network ConfigurationSQL Native Client ConfigurationThe following table contains information about each entry.
Note Client Network Utility (Cliconfg.exe) is available in SQL Server 2000.In SQL Server 2005, the functionality of this tool is included in SQL Server Configuration Manager. However, to address backward compatibility issues, Client Network Utility is included in SQL Server 2005.
Collapse this tableExpand this table
Entry in SQL Server Configuration ManagerVersionResidence of aliases that are created in SQL Server Configuration ManagerCorresponding subkey in the registryApplications that are affected by the protocol settingsAvailability of aliases to applicationsResidence of aliases that are created by Client Network UtilitySQL Native Client Configuration (32bit)32-bitAliases that are created in this entry reside only in this entryHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectToNot applicableOnly 32-bit applications can use aliases in this entryNot applicableSQL Native Client Configuration64-bitAliases that are created in this entry reside only in this entryHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectToNot applicableOnly 64-bit applications can use aliases in this entryResides only in this entrySQL Server 2005 Network Configuration (32bit)32-bitNot applicableHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\SNI9.0Only 32-bit applications are affectedNot applicableNot applicableSQL Server 2005 Network Configuration64-bitNot applicableHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0Only 64-bit applications are affectedNot applicableNot applicable

Symptoms
On a 64-bit computer, you install an instance of the 32-bit (x86-based) version of Microsoft SQL Server 2008. On the same computer, you install an instance of the 64-bit version of SQL Server 2008. Ifyou then uninstall the 64-bit instance, you receive the following error message when you open SQL Server Configuration Manager:

Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager.
Invalid namespace [0x8004100e]This problem also occurs if you uninstall the 32-bit instance, and you then open SQL Server Configuration Manager.
Resolution
This problem occurs because the WMI provider is removed when you uninstall an instance of SQL Server 2008. The 32-bit instance and the 64-bit instance of SQL Server 2008 share the same WMI configuration file. This file is located in the %programfiles(x86)% folder.