SQL Server Q&A

Symptoms
If you use a program that uses Performance Data Helper (PDH) APIs to collect the performance data of several instances of Microsoft SQL Server 2000 at the same time, an access violation may occur. For example, this problem occurs if you collect performance data from six or more instances of SQL Server. The performance data collection for the instances of SQL Server may also stop. Additionally, you may notice that the following registry key is created and the value of the registry key is set to 1:
HKey_Local_Machine\System\ControlSet001\Services\<InstanceOfSQLServer>\Performance\Disable Performance CountersNote The registry key is created for all the instances of SQL Server where the performance data is collected.
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 hotfix 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.

DateTimeVersionSizeFile name——————————————————————————-31-May-200305:152000.80.818.078,400Console.exe27-Oct-200314:512000.80.873.0315,968Custtask.dll30-Jan-200402:592000.80.911.033,340Dbmslpcn.dll24-Apr-200312:42786,432Distmdl.ldf24-Apr-200312:422,359,296Distmdl.mdf29-Jan-200312:25180Drop_repl_hotfix.sql11-Sep-200313:562000.80.859.01,905,216Dtspkg.dll26-Aug-200306:462000.80.854.0528,960Dtspump.dll23-Jun-200309:102000.80.837.01,557,052Dtsui.dll23-Jun-200309:102000.80.837.0639,552Dtswiz.dll23-Apr-200313:21747,927Instdist.sql02-May-200312:261,581Inst_repl_hotfix.sql30-Jan-200402:592000.80.911.090,692Msgprox.dll31-Mar-200312:371,873Odsole.sql30-Jan-200402:592000.80.911.062,024Odsole70.dll30-Jan-200402:592000.80.911.025,144Opends60.dll30-Jan-200402:592000.80.911.057,904Osql.exe02-Apr-200309:452000.80.797.0279,104Pfutil80.dll04-Aug-200304:47550,780Procsyst.sql11-Sep-200311:0712,305Qfe469315.sql22-May-200309:2719,195Qfe469571.sql29-Jan-200411:471,090,380Replmerg.sql30-Jan-200402:592000.80.911.0221,768Replprov.dll30-Jan-200402:592000.80.911.0307,784Replrec.dll29-Jan-200409:542000.80.911.0159,813Replres.rll05-Sep-200310:301,087,150Replsys.sql13-Aug-200302:58986,603Repltran.sql30-Jan-200402:592000.80.911.0287,304Rinitcom.dll30-Jan-200402:592000.80.911.057,916Semnt.dll29-Jul-200306:432000.80.819.0492,096Semobj.dll31-May-200304:572000.80.818.0172,032Semobj.rll02-Jan-200406:122000.80.904.053,832Snapshot.exe09-Dec-200306:37117,834Sp3_serv_uni.sql04-Feb-200411:162000.80.913.028,672Sqlagent.dll04-Feb-200411:172000.80.913.0311,872Sqlagent.exe19-Feb-200404:322000.80.916.0168,001Sqlakw32.dll11-Mar-200415:042000.80.923.033,344Sqlctr80.dll30-Jan-200402:592000.80.911.04,215,360Sqldmo.dll07-Apr-200304:1425,172Sqldumper.exe29-Jan-200409:472000.80.911.028,672Sqlevn70.rll05-Mar-200403:432000.80.922.0180,792Sqlmap70.dll02-Sep-200313:262000.80.857.0188,992Sqlmmc.dll02-Sep-200309:332000.80.857.0479,232Sqlmmc.rll21-Oct-200310:382000.80.871.0401,984Sqlqry.dll30-Jan-200402:592000.80.911.057,920Sqlrepss.dll11-Mar-200415:052000.80.923.07,618,641Sqlservr.exe30-Jan-200402:592000.80.911.0590,396Sqlsort.dll30-Jan-200402:592000.80.911.045,644Sqlvdi.dll30-Jan-200402:592000.80.911.0106,588Sqsrvres.dll30-Jan-200402:592000.80.911.033,340Ssmslpcn.dll30-Jan-200402:592000.80.911.082,492Ssnetlib.dll30-Jan-200402:592000.80.911.025,148Ssnmpn70.dll27-Oct-200314:512000.80.873.0123,456Stardds.dll30-Jan-200402:592000.80.911.0158,240Svrnetcn.dll30-Jan-200402:592000.80.911.076,416Svrnetcn.exe30-Apr-200310:222000.80.816.045,132Ums.dll30-Jan-200402:592000.80.911.098,872Xpweb70.dll19-Jun-200400:522000.80.952.0307,784Replrec.dll19-Jun-200400:522000.80.952.07,581,777Sqlservr.exeNote Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Symptoms
Microsoft distributes Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release.
Resolution
Consider the following scenario:You drop a column of a partitioned table in SQL Server 2008 R2.You create a new partition for the table. You try to insert data into the new partition of the table.In this scenario, an access violation may occur.

Symptoms
This article describes the following about this hotfix release:The issues that are fixed by the hotfix packageThe prerequisites for installing the hotfix packageWhether you must restart the computer after you install the hotfix packageWhether the hotfix package is replaced by any other hotfix packageWhether you must make any registry changesThe files that are contained in the hotfix package
Resolution
When you run the DBCC MEMORYSTATUS statement in Microsoft SQL Server 2005, a minidump file is generated. Additionally, the following error message is logged in the SQL Server 2005 error log:

Date Time SPID ***Stack Dump being sent to T:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
Date Time SPID SqlDumpExceptionHandler: Process 128 generated fatal exception c0000094 EXCEPTION_INT_DIVIDE_BY_ZERO. SQL Server is terminating this process.
Date Time SPID *
Date Time SPID *
Date Time SPID * BEGIN STACK DUMP:
Date Time SPID * 07/27/07 09:55:00 spid 128
Date Time SPID *
Date Time SPID *
Date Time SPID * Exception Address = 0000000001911CC8
Module(sqlservr+0000000000911CC8)
Date Time SPID * Exception Code = c0000094
EXCEPTION_INT_DIVIDE_BY_ZERO

Symptoms
Microsoft distributes Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release.
Resolution
Consider the following scenario:You start a SQL Server Extended Event session in Microsoft SQL Server 2008 R2.You perform actions that are bound to events in the Xevent session on a case-sensitive database.In this scenario, SQL Server may crash, and then a mini-dump file is generated. Additionally, the following exception is logged in the SQL Server error log file:?

Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION

Symptoms
Consider the following scenario:You have a database mirroring session in Microsoft SQL Server 2005. The database mirroring session does not have a witness. You set up a witness server. On the principal server and on the witness server, you do not use DNS together with DHCP for name resolution. Instead, you specify that a host file should be used for name resolution. On the principal server instance, you try to set the witness.In this scenario, you receive the following error message:

Msg 1456, Level 16, State 3, Line 1
The ALTER DATABASE command could not be sent to the remote server instance ‘TCP://ServerName:port’. The database mirroring configuration was not changed. Verify that the server is connected, and try again.
Resolution
A database mirroring session must use a fully qualified domain name (FQDN) to resolve the name of the witness server.

Symptoms
When you try toinstall Microsoft SQL Server 2005 Express Edition (SQL Server Express) or Microsoft SQL Server 2005 Express Edition with Advanced Services, the installation fails. Additionally, you receive the following error message:

Server SQL Server is terminating because of fatal exception c000001d.If you examine the SQL Server error log when this problem occurs, you see an error message that resembles one of the following:
Error message 1

SqlDumpExceptionHandler: Process 4 generated fatal exception c000001d EXCEPTION_ILLEGAL_INSTRUCTION. SQL Server is terminating this process.
Error message 2

2006-03-02 22:40:24.79 ServerError: 17311, Severity: 16, State: 1.
2006-03-02 22:40:24.79 ServerSQL Server is terminating because of fatal exception c000001d. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling.For more information about how to examine the SQL Server error log, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms187885.aspx(http://msdn2.microsoft.com/en-us/library/ms187885.aspx)
Resolution
This problem occurs because of one of the following reasons:The computer on which you try to install SQL Server Express or SQL Server Express with Advanced Services is equipped with a CPU that does not support cache prefetching.
The affected CPUs include VIA Eden CPUs and Transmeta CPUs. Typically, these CPUs are used in devices when low power consumption,low heat, or low noise is important.The media from which you try to install SQL Server Express or SQL Server Express with Advanced Services is corrupted.