SQL Server Q&A

Symptoms
This article discusses the reasons for “out of sync” error messages when you have log shipping configured for SQL Server 2000.
One of the following error messages may be logged in the SQL Server error log:
Error message 14420
Error: 14420, Severity: 16, State: 1
The log shipping destination %s.%s is out of sync by %s minutes.Error message 14421
Error: 14421, Severity: 16, State: 1
The log shipping destination %s.%s is out of sync by %s minutes.If you are using SQL Server 2005, the description for these error messages are different:
Error message 14420

Error: 14420, Severity: 16, State: 1
The log shipping primary database %s.%s has backup threshold of %d minutes and has not performed a backup log operation for %d minutes. Check agent log and logshipping monitor information.Error message 14421

Error: 14421, Severity: 16, State: 1
The log shipping secondary database %s.%s has restore threshold of %d minutes and is out of sync. No restore was performed for %d minutes. Restored latency is %d minutes. Check agent log and logshipping monitor information.
Resolution
Log shipping uses Sqlmaint.exe to back up and to restore databases. When SQL Server creates a transaction log backup as part of a log shipping setup, Sqlmaint.exe connects to the monitor server and updates the log_shipping_primaries table with the last_backup_filename information. Similarly, when you run a Copy or a Restore job on a secondary server, Sqlmaint.exe connects to the monitor server and updates the log_shipping_secondaries table.
As part of log shipping, alert messages 14220 and 14221 are generated to track backup and restoration activity. The alert messages are generated depending on the value of Backup Alert threshold and Out of Sync Alert threshold respectively.
The alert message 14220 indicates that the difference between current time and the time indicated by the last_backup_filename value in the log_shipping_primaries table on the monitor server is greater than value that is set for the Backup Alert threshold.
The alert message 14221 indicates that the difference between the time indicated by the last_backup_filename in the log_shipping_primaries table and the last_loaded_filename in the log_shipping_secondaries table is greater than the value set for the Out of Sync Alert threshold.
Troubleshooting Error Message 14420 By definition, message 14420 does not necessarily indicate a problem with log shipping. The message indicates that the difference between the last backed up file and current time on the monitor server is greater than the time that is set for the Backup Alert threshold.
There are serveral reasons why the alert message is generated. The following list includes some of these reasons: The date or time (or both) on the monitor server is different from the date or time on the primary server. It is also possible that the system date or time was modified on the monitor or the primary server. This may also generate alert messages.When the monitor server is offline and then back online, the fields in the log_shipping_primaries table are not updated with the current values before the alert message job runs.The log shipping Copy job that is run on the primary server might not connect to the monitor server msdb database to update the fields in the log_shipping_primaries table. This may be the result of an authentication problem between the monitor server and the primary server.You may have set an incorrect value for the Backup Alert threshold. Ideally, you must set this value to at least three times the frequency of the backup job. If you change the frequency of the backup job after log shipping is configured and functional, you must update the value of theBackup Alert threshold accordingly.The backup job on the primary server is failing. In this case, check the job history for the backup job to see a reason for the failure.
Troubleshooting Error Message 14421 By definition, message 14421 does not necessarily indicate a problem with Log Shipping. This message indicates that the difference between the last backed up file and last restored file is greater than the time selected for the Out of Sync Alert threshold.
There are serveral reasons why the alert message is raised. The following list includes some of these reasons: The date or time (or both) on the primary server is modified such that the date or time on the primary server is significantly ahead between consecutive transaction log backups.The log shipping Restore job that is running on the secondary server cannot connect to the monitor server msdb database to update the log_shipping_secondaries table with the correct value. This may be the result of an authentication problem between the secondary server and the monitor server.You may have set an incorrect value for the Out of Sync Alert threshold. Ideally, you must set this value to at least three times the frequency of the slower of the Copy and Restore jobs. If the frequency of the Copy or Restore jobs is modified after log shipping is set up and functional, you must modify the value of the Out of Sync Alert threshold accordingly.Problems either with the Backup job or Copy job are most likely to result in “out of sync” alert messages. If “out of sync” alert messages are raised and if there are no problems with the Backup or the Restore job, check the Copy job for potential problems. Additionally, network connectivity may cause the Copy job to fail.It is also possible that the Restore job on the secondary server is failing. In this case, check the job history for the Restore job because it may indicate a reason for the failure.

Symptoms
This article contains a list of the Microsoft SQL Server 2000 hotfixes. You can use this list to determine which hotfixes are included in a specific hotfix build. Unless otherwise specified, all the hotfixes in earlier builds are included in later builds. The list includes all the public hotfixes that have been released since the release of Microsoft SQL Server 2000 Service Pack 4 (SP4).
Important notes: Before you apply any hotfix in this list, you must have SQL Server 2000 SP4 installed. To determine which version of SQL Server you have, see the following article in the Microsoft Knowledge Base:
321185?(http://support.microsoft.com/kb/321185/) How to identify your SQL Server version and editionTo obtain SQL Server 2000 SP4, visit the following Microsoft Download Center Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-99a9-b7f0213f8bc5(http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-99a9-b7f0213f8bc5)For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591?(http://support.microsoft.com/kb/119591/) How to obtain Microsoft support files from online servicesMicrosoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.Hotfixes that are not part of a security release or a public roll-up package can only be obtained by contacting Microsoft Product Support Services.
For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.This list does not contain the hotfixes for Microsoft Data Access Components (MDAC) or for Microsoft SQL Server 2000 Analysis Services.This article also describes a list of the SQL Server 2000 SP3-based hotfixes that are not included in SQL Server 2000 SP4. The reason is that the ship date of these hotfixes is later than the ship date of SQL Server 2000 SP4. These hotfixes are first included in this build.
Resolution
The following list includes all public SQL Server 2000 hotfixes that have been released since the release of SQL Server 2000 SP4.
SQL Server 2000 build 8.00.2040
899761?(http://support.microsoft.com/kb/899761/) FIX: Not all memory is available when AWE is enabled on a computer that is running a 32-bit version of SQL Server 2000 Service Pack 4SQL Server 2000 build 8.00.2040 includes the same hotfix that SQL Server 2000 build 8.00.2141 includes. SQL Server 2000 build 8.00.2040 isa general distribution release (GDR) update. The hotfix that is included inSQL Server 2000 build 8.00.2040 is the first hotfix that was released after SQL Server 2000 SP4.
For more information about a GDR, click the following article number to view the article in the Microsoft Knowledge Base:
935897?(http://support.microsoft.com/kb/935897/) An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
SQL Server 2000 build 8.00.2145
836651?(http://support.microsoft.com/kb/836651/) FIX: You receive query results that were not expected when you use both ANSI joins and non-ANSI joins
898626?(http://support.microsoft.com/kb/898626/) FIX: An access violation may occur when a deadlock graph is written to the error log in SQL Server 2000
899430?(http://support.microsoft.com/kb/899430/) FIX: An access violation may occur when you run a SELECT query and the NO_BROWSETABLE option is set to ON in Microsoft SQL Server 2000
899431?(http://support.microsoft.com/kb/899431/) FIX: An access violation occurs in the Mssdi98.dll file, and SQL Server crashes when you use SQL Query Analyzer to debug a stored procedure in SQL Server 2000 Service Pack 4
900390?(http://support.microsoft.com/kb/900390/) FIX: The Mssdmn.exe process may use lots of CPU capacity when you perform a SQL Server 2000 full text search of Office Word documents
900404?(http://support.microsoft.com/kb/900404/) FIX: The results of the query may be returned much slower than you expect when you run a query that includes a GROUP BY statement in SQL Server 2000
900470?(http://support.microsoft.com/kb/900470/) FIX: You may receive an error message when you perform transactional replication in SQL Server 2000
900629?(http://support.microsoft.com/kb/900629/) FIX: You receive a “Failed to open a table” error message when you try to open a trace table by using SQL Profiler after you upgrade to SQL Server 2000 Service Pack 4
901200?(http://support.microsoft.com/kb/901200/) FIX: You may receive a “Server: Msg 7358, Level 16, State 1, Line 1” error message after you run a linked server query in SQL Server 2000 Service Pack 4
901212?(http://support.microsoft.com/kb/901212/) FIX: You receive an error message if you use the sp_addalias or sp_dropalias procedures when the IMPLICIT_TRANSACTIONS option is set to ON in SQL Server 2000 Service Pack 4
902955?(http://support.microsoft.com/kb/902955/) FIX: You receive a “Getting registry information” message when you run the Sqldiag.exe utility after you install SQL Server 2000 Service Pack 4
SQL Server 2000 build 8.00.2146
909100?(http://support.microsoft.com/kb/909100/) FIX: The performance of the statement that raises an error differs from the performance of the statement that does not raise an error when you trace exception events in SQL Server 2000 on an IA-64 computer
SQL Server 2000 build 8.00.2148
895123?(http://support.microsoft.com/kb/895123/) FIX: You may receive error message 701, error message 802, and error message 17803 when many hashed buffers are available in SQL Server 2000
899410?(http://support.microsoft.com/kb/899410/) FIX: You may experience slow server performance when you start a trace in an instance of SQL Server 2000 that runs on a computer that has more than four processors
902150?(http://support.microsoft.com/kb/902150/) FIX: Some 32-bit applications that use SQL-DMO and SQL-VDI APIs may stop working after you install SQL Server 2000 Service Pack 4 on an Itanium-based computer
903086?(http://support.microsoft.com/kb/903086/) FIX: The batch job stops running, and job output is truncated when you run a Transact-SQL script as a SQL Server Agent job in SQL Server 2000
SQL Server 2000 build 8.00.2151
903742?(http://support.microsoft.com/kb/903742/) FIX: You receive an “Error: 8526, Severity: 16, State: 2” error message in SQL Profiler when you use SQL Query Analyzer to start or to enlist into a distributed transaction after you have installed SQL Server 2000 Service Pack 4
905417?(http://support.microsoft.com/kb/905417/) FIX: Error message when you try to open SQL Server 2000 Data Transformation Services (DTS) packages in SQL Server Management Studio: “SQL Server 2000 DTS Designer components are required to edit DTS packages”
904244?(http://support.microsoft.com/kb/904244/) FIX: Incorrect data is inserted unexpectedly when you perform a bulk copy operation by using the DB-Library API in SQL Server 2000 Service Pack 4
SQL Server 2000 build 8.00.2156
906790?(http://support.microsoft.com/kb/906790/) FIX: You receive an error message when you try to rebuild the master database after you have installed hotfix builds in SQL Server 2000 SP4 64-bit
906890?(http://support.microsoft.com/kb/906890/) FIX: You receive an access violation error message when a user-defined function is in a high-stress scenario in SQL Server 2000
909379?(http://support.microsoft.com/kb/909379/) FIX: You receive a 17883 error message when you run a complex query against SQL Server 2000
909380?(http://support.microsoft.com/kb/909380/) FIX: Error message 17883 may be logged in the error log when you try to manually update table statistics in SQL Server 2000
SQL Server 2000 build 8.00.2159
887700?(http://support.microsoft.com/kb/887700/) FIX: Server Network Utility may display incorrect protocol properties in SQL Server 2000
891017?(http://support.microsoft.com/kb/891017/) FIX: SQL Server 2000 may stop responding to other requests when you perform a large deallocation operation
891201?(http://support.microsoft.com/kb/891201/) FIX: Performance is significantly reduced when you set trace flag 9134 to prevent error message 601 in SQL Server 2000
891268?(http://support.microsoft.com/kb/891268/) FIX: You receive a 17883 error message and SQL Server 2000 may stop responding to other requests when you perform large in-memory sort operations
891585?(http://support.microsoft.com/kb/891585/) FIX: Database recovery does not occur, or a user database is marked as suspect in SQL Server 2000
892205?(http://support.microsoft.com/kb/892205/) FIX: You may receive a 17883 error message when SQL Server 2000 performs a very large hash operation
892392?(http://support.microsoft.com/kb/892392/) FIX: Query performance may be slower if the query contains both a GROUP BY clause and a DISTINCT keyword on the same column
892551?(http://support.microsoft.com/kb/892551/) FIX: You receive a SqlException error message when you call the sp_addmergepublication stored procedure when the Active Directory directory service is not available in SQL Server 2000
892840?(http://support.microsoft.com/kb/892840/) FIX: 17883 errors may be written to the SQL Server error log when you run a query that generates many floating point exception errors in SQL Server 2000
892923?(http://support.microsoft.com/kb/892923/) FIX: Differential database backups may not contain database changes in the Page Free Space (PFS) pages in SQL Server 2000
892935?(http://support.microsoft.com/kb/892935/) FIX: You experience slow performance when you join local partitioned views with a table in SQL Server 2000
892940?(http://support.microsoft.com/kb/892940/) FIX: You experience delays and receive a 17883 error message when SQL Server 2000 performs a large and complex query plan that uses hash operators
893172?(http://support.microsoft.com/kb/893172/) FIX: An access violation may occur when you use the READPAST lock hint and you use a non-clustered index in your query in SQL Server 2000
894257?(http://support.microsoft.com/kb/894257/) FIX: You receive an “Incorrect syntax near ‘)’” error message when you run a script that was generated by SQL-DMO for an Operator object in SQL Server 2000
896985?(http://support.microsoft.com/kb/896985/) FIX: The Subscriber may not be able to upload changes to the Publisher when you incrementally add an article to a publication in SQL Server 2000 Service Pack 3
897572?(http://support.microsoft.com/kb/897572/) FIX: You may receive a memory-related error message when you repeatedly create and destroy an out-of-process COM object within the same batch or stored procedure in SQL Server 2000
897578?(http://support.microsoft.com/kb/897578/) FIX: Only the master database and the tempdb database are listed when you try to create a new job in SQL Server Enterprise Manager
900625?(http://support.microsoft.com/kb/900625/) FIX: The error message that the SELECT statement returns may contain user data in SQL Server 2000
907250?(http://support.microsoft.com/kb/907250/) FIX: You may experience concurrency issues when you run the DBCC INDEXDEFRAG statement in SQL Server 2000
892310?(http://support.microsoft.com/kb/892310/) FIX: The results are different every time that you run a complex query that contains a hash outer join operator in SQL Server 2000
SQL Server 2000 build 8.00.2162
887700?(http://support.microsoft.com/kb/887700/) FIX: Server Network Utility may display incorrect protocol properties in SQL Server 2000
891017?(http://support.microsoft.com/kb/891017/) FIX: SQL Server 2000 may stop responding to other requests when you perform a large deallocation operation
891201?(http://support.microsoft.com/kb/891201/) FIX: Performance is significantly reduced when you set trace flag 9134 to prevent error message 601 in SQL Server 2000
891268?(http://support.microsoft.com/kb/891268/) FIX: You receive a 17883 error message and SQL Server 2000 may stop responding to other requests when you perform large in-memory sort operations
891585?(http://support.microsoft.com/kb/891585/) FIX: Database recovery does not occur, or a user database is marked as suspect in SQL Server 2000
891866?(http://support.microsoft.com/kb/891866/) FIX: The query runs slower than you expected when you try to parse a query in SQL Server 2000
892205?(http://support.microsoft.com/kb/892205/) FIX: You may receive a 17883 error message when SQL Server 2000 performs a very large hash operation
892310?(http://support.microsoft.com/kb/892310/) FIX: The results are different every time that you run a complex query that contains a hash outer join operator in SQL Server 2000
892392?(http://support.microsoft.com/kb/892392/) FIX: Query performance may be slower if the query contains both a GROUP BY clause and a DISTINCT keyword on the same column
892551?(http://support.microsoft.com/kb/892551/) FIX: You receive a SqlException error message when you call the sp_addmergepublication stored procedure when the Active Directory directory service is not available in SQL Server 2000
892840?(http://support.microsoft.com/kb/892840/) FIX: 17883 errors may be written to the SQL Server error log when you run a query that generates many floating point exception errors in SQL Server 2000
892923?(http://support.microsoft.com/kb/892923/) FIX: Differential database backups may not contain database changes in the Page Free Space (PFS) pages in SQL Server 2000
892935?(http://support.microsoft.com/kb/892935/) FIX: You experience slow performance when you join local partitioned views with a table in SQL Server 2000
892940?(http://support.microsoft.com/kb/892940/) FIX: You experience delays and receive a 17883 error message when SQL Server 2000 performs a large and complex query plan that uses hash operators
892985?(http://support.microsoft.com/kb/892985/) FIX: You may experience unexpected delays in query execution and unexpected time-out situations, and you may receive error message 17883 when you use the BULK INSERT command in SQL Server 2000
893172?(http://support.microsoft.com/kb/893172/) FIX: An access violation may occur when you use the READPAST lock hint and you use a non-clustered index in your query in SQL Server 2000
894254?(http://support.microsoft.com/kb/894254/) FIX: A complex query that includes a UNION ALL operator and an EXISTS clause may fail in SQL Server 2000
894257?(http://support.microsoft.com/kb/894257/) FIX: You receive an “Incorrect syntax near ‘)’” error message when you run a script that was generated by SQL-DMO for an Operator object in SQL Server 2000
895187?(http://support.microsoft.com/kb/895187/) FIX: You receive an error message when you try to delete records by running a Delete Transact-SQL statement in SQL Server 2000
896425?(http://support.microsoft.com/kb/896425/) FIX: The BULK INSERT statement silently skips insert attempts when the data value is NULL and the column is defined as NOT NULL for INT, SMALLINT, and BIGINT data types in SQL Server 2000
896980?(http://support.microsoft.com/kb/896980/) FIX: The query plan may take longer than expected to compile, and you may receive error message 701, error message 8623, or error message 8651 in SQL Server 2000
896985?(http://support.microsoft.com/kb/896985/) FIX: The Subscriber may not be able to upload changes to the Publisher when you incrementally add an article to a publication in SQL Server 2000 Service Pack 3
897572?(http://support.microsoft.com/kb/897572/) FIX: You may receive a memory-related error message when you repeatedly create and destroy an out-of-process COM object within the same batch or stored procedure in SQL Server 2000
897578?(http://support.microsoft.com/kb/897578/) FIX: Only the master database and the tempdb database are listed when you try to create a new job in SQL Server Enterprise Manager
898115?(http://support.microsoft.com/kb/898115/) FIX: The subquery in a CASE function is evaluated even if the condition in the WHEN expression is false in SQL Server 2000
898709?(http://support.microsoft.com/kb/898709/) FIX: Error message when you use SQL Server 2000: “Time out occurred while waiting for buffer latch type 3″
900335?(http://support.microsoft.com/kb/900335/) FIX: The SQL Server 2000 automatic database recovery operation may not succeed if an index contains a FLOAT data type or a REAL data type, and this data type contains a NaN value
900416?(http://support.microsoft.com/kb/900416/) FIX: A 17883 error may occur you run a query that uses a hash join in SQL Server 2000
900625?(http://support.microsoft.com/kb/900625/) FIX: The error message that the SELECT statement returns may contain user data in SQL Server 2000
902851?(http://support.microsoft.com/kb/902851/) FIX: SQL Server 2000 may intermittently appear to stop responding (hang) during a scheduled maintenance DBCC DBREINDEX operation
902852?(http://support.microsoft.com/kb/902852/) FIX: Error message when you run an UPDATE statement that uses two JOIN hints to update a table in SQL Server 2000: “Internal SQL Server error”
905765?(http://support.microsoft.com/kb/905765/) FIX: A view is corrupted after you run the DBCC DBREINDEX Transact-SQL statement to rebuild the clustered index on a view in SQL Server 2000
SQL Server 2000 build 8.00.2164
909089?(http://support.microsoft.com/kb/909089/) FIX: An access violation may occur when you try to run a Transact-SQL query in SQL Server 2000
SQL Server 2000 build 8.00.2166
909734?(http://support.microsoft.com/kb/909734/) FIX: An error message is logged, and new diagnostics do not capture the thread stack when the SQL Server User Mode Scheduler (UMS) experiences a nonyielding thread in SQL Server 2000 Service Pack 4
SQL Server 2000 build 8.00.2171
908156?(http://support.microsoft.com/kb/908156/) FIX: You receive an error message when MS DTC for SQL Server 2000 reuses a server process identifier (SPID) to enlist in a distributed transaction
909369?(http://support.microsoft.com/kb/909369/) FIX: Automatic checkpoints on some SQL Server 2000 databases do not run as expected
910392?(http://support.microsoft.com/kb/910392/) FIX: You may receive incorrect results when you run a Transact-SQL query in SQL Server 2000
910895?(http://support.microsoft.com/kb/910895/) FIX: You may receive an error message when you set the database collation to Thai_CI_AS and you try to run a Transact-SQL update query in SQL Server 2000
SQL Server 2000 build 8.00.2172
910707?(http://support.microsoft.com/kb/910707/) FIX: When you query a view that was created by using the VIEW_METADATA option, an access violation may occur in SQL Server 2000
910710?(http://support.microsoft.com/kb/910710/) FIX: You receive an error message when a Visual Basic application opens a dynamic cursor on a GROUP BY query in SQL Server 2000 Service Pack 4
SQL Server 2000 build 8.00.2175
911569?(http://support.microsoft.com/kb/911569/) FIX: You may receive an access violation error message when you run a linked server query that includes a subquery
911677?(http://support.microsoft.com/kb/911677/) FIX: A query may run more slowly against SQL Server 2000 post-Service Pack 3 hotfix build 8.00.0988 than a query that you run against SQL Server 2000 post-Service Pack 3 hotfix builds that are earlier than build 8.00.0988
911678?(http://support.microsoft.com/kb/911678/) FIX: No rows may be returned, and you may receive an error message when you try to import SQL Profiler trace files into tables by using the fn_trace_gettable function in SQL Server 2000
SQL Server 2000 build 8.00.2177
912468?(http://support.microsoft.com/kb/912468/) FIX: The connection that processes the cube stops responding, and the cube is locked in SQL Server 2000 Analysis Services
913049?(http://support.microsoft.com/kb/913049/) FIX: The result set contains data for the whole relational source when you execute a query to retrieve a drillthrough result set in SQL Server 2000 Analysis Services
SQL Server 2000 build 8.00.2180
913684?(http://support.microsoft.com/kb/913684/) FIX: You may receive error messages when you use linked servers in SQL Server 2000 on a 64-bit Itanium processor
913789?(http://support.microsoft.com/kb/913789/) FIX: The password that you specify in a BACKUP statement appears in the SQL Server Errorlog file or in the Application event log if the BACKUP statement does not run in SQL Server 2000
SQL Server 2000 build 8.00.2181
914085?(http://support.microsoft.com/kb/914085/) FIX: You may receive an error message when you try to use a Japanese user name or a Korean user name to connect to an Analysis Services server
SQL Server 2000 build 8.00.2184
913991?(http://support.microsoft.com/kb/913991/) FIX: Hotfix files may not be copied to remote nodes when you install a 32-bit hotfix, and hotfix files may not be removed from remote nodes on a computer that is running SQL Server 2000 in an MSCS environment
914298?(http://support.microsoft.com/kb/914298/) FIX: You may receive an error message, and the SQL Server process may crash when you copy or transfer SQL Server 2000 data
914384?(http://support.microsoft.com/kb/914384/) FIX: The database status changes to Suspect when you perform a bulk copy in a transaction and then roll back the transaction in SQL Server 2000
SQL Server 2000 build 8.00.2185
914439?(http://support.microsoft.com/kb/914439/) FIX: The synchronization process may take a long time when you synchronize merge replication publications in SQL Server 2000
915340?(http://support.microsoft.com/kb/915340/) FIX: A deadlock occurs when the scheduled SQL Server Agent job that you add or that you update is running in SQL Server 2000
SQL Server 2000 build 8.00.2187
914298?(http://support.microsoft.com/kb/914298/) FIX: You may receive an error message, and the SQL Server process may crash when you copy or transfer SQL Server 2000 data
SQL Server 2000 build 8.00.2189
913438?(http://support.microsoft.com/kb/913438/) FIX: The SQL Server process may end unexpectedly when you turn on trace flag -T1204 and a profiler trace is capturing the Lock:DeadLock Chain event in SQL Server 2000 Service Pack 4
915436?(http://support.microsoft.com/kb/915436/) FIX: Error message when you run a complex insert query or a stored procedure in SQL Server 2000: “Internal SQL Server error”
916652?(http://support.microsoft.com/kb/916652/) FIX: An access violation may occur when you run a query on a table that has a multicolumn index in SQL Server 2000
916653?(http://support.microsoft.com/kb/916653/) FIX: An access violation may occur intermittently in the CQList::Remove function when you run a query in SQL Server 2000
SQL Server 2000 build 8.00.2190
916097?(http://support.microsoft.com/kb/916097/) FIX: You may not be able to use Analysis Manager to change server properties for an instance of SQL Server 2000 Analysis Services that is running on an IA-64 server computer after you install Windows Server 2003 S916097 on a client computer
SQL Server 2000 build 8.00.2191
916698?(http://support.microsoft.com/kb/916698/) FIX: Error message when you run SQL Server 2000: “Failed assertion = ‘lockFound == TRUE’”
916950?(http://support.microsoft.com/kb/916950/) FIX: You may experience heap corruption, and SQL Server 2000 may shut down with fatal access violations when you try to browse files in SQL Server 2000 Enterprise Manager on a Windows Server 2003 x64-based computer
SQL Server 2000 build 8.00.2192
917593?(http://support.microsoft.com/kb/917593/) FIX: The “Audit Logout” event does not appear in the trace results file when you run a profiler trace against a linked server instance in SQL Server 2000
917606?(http://support.microsoft.com/kb/917606/) FIX: You may notice a decrease in performance when you run a query that uses the UNION ALL operator in SQL Server 2000 Service Pack 4
SQL Server 2000 build 8.00.2194
893312?(http://support.microsoft.com/kb/893312/) FIX: You may receive a “SQL Server could not spawn process_loginread thread” error message, and a memory leak may occur when you cancel a remote query in SQL Server 2000
917565?(http://support.microsoft.com/kb/917565/) FIX: Error 17883 is logged in the SQL Server error log, and the instance of SQL Server 2000 temporarily stops responding
917972?(http://support.microsoft.com/kb/917972/) FIX: You receive an access violation error message when you try to perform a read of a large binary large object column in SQL Server 2000
SQL Server 2000 build 8.00.2196
919165?(http://support.microsoft.com/kb/919165/) FIX: A memory leak occurs when you run a remote query by using a linked server in SQL Server 2000
SQL Server 2000 build 8.00.2197
919068?(http://support.microsoft.com/kb/919068/) FIX: The query may return incorrect results, and the execution plan for the query may contain a “Table Spool” operator in SQL Server 2000
919133?(http://support.microsoft.com/kb/919133/) FIX: Each query takes a long time to compile when you execute a single query or when you execute multiple concurrent queries in SQL Server 2000
919399?(http://support.microsoft.com/kb/919399/) FIX: A profiler trace in SQL Server 2000 may stop logging events unexpectedly, and you may receive the following error message: “Failed to read trace data”
SQL Server 2000 build 8.00.2199
919221?(http://support.microsoft.com/kb/919221/) FIX: SQL Server 2000 may take a long time to complete the synchronization phase when you create a merge publication
SQL Server 2000 build 8.00.2200
920121?(http://support.microsoft.com/kb/920121/) FIX: Error message when you add a calculated member to a cube in SQL Server 2000 Analysis Services Service Pack 4: “Unable to update the calculated member”
SQL Server 2000 build 8.00.2201
920930?(http://support.microsoft.com/kb/920930/) FIX: Error message when you try to run a query on a linked server in SQL Server 2000
SQL Server 2000 build 8.00.2203
922040?(http://support.microsoft.com/kb/922040/) FIX: You cannot uninstall SQL Server 2000 build 2187 when SQL Server 2000 build 2187 is configured as a Microsoft Cluster Service (MSCS) node
SQL Server 2000 build 8.00.2204
921929?(http://support.microsoft.com/kb/921929/) BUG: When you click “Build Query” in the “Execute SQL Task Properties” dialog box of the SQL Server 2000 DTS package designer, SQL Server 2005 Management Studio unexpectedly closes
SQL Server 2000 build 8.00.2207
923344?(http://support.microsoft.com/kb/923344/) FIX: A SQL Server 2000 session may be blocked for the whole time that a Snapshot Agent job runs
SQL Server 2000 build 8.00.2209
923327?(http://support.microsoft.com/kb/923327/) FIX: You may receive an access violation error message when you import data by using the “Bulk Insert” command in SQL Server 2000
923563?(http://support.microsoft.com/kb/923563/) FIX: Error message when you configure an immediate updating transactional replication in SQL Server 2000: “Implicit conversion from datatype ‘text’ to ‘nvarchar’ is not allowed”
923796?(http://support.microsoft.com/kb/923796/) FIX: Data in a subscriber of a merge publication in SQL Server 2000 differs from the data in the publisher
SQL Server 2000 build 8.00.2215
924662?(http://support.microsoft.com/kb/924662/) FIX: The query performance may be slow when you query data from a view in SQL Server 2000
SQL Server 2000 build 8.00.2216
925000?(http://support.microsoft.com/kb/925000/) FIX: An access violation may occur in SQL Server 2000 Analysis Services when you try to use a 2007 Office system program to open an offline local cube
SQL Server 2000 build 8.00.2217
924664?(http://support.microsoft.com/kb/924664/) FIX: You cannot stop the SQL Server service, or many minidump files and many log files are generated in SQL Server 2000
SQL Server 2000 build 8.00.2218
925297?(http://support.microsoft.com/kb/925297/) FIX: The result may be sorted in the wrong order when you run a query that uses the ORDER BY clause to sort a column in a table in SQL Server 2000
SQL Server 2000 build 8.00.2220
925745?(http://support.microsoft.com/kb/925745/) FIX: The members of a role that uses dynamic security cannot access the SQL Server 2000 Analysis Services database when you run a query against a cube
SQL Server 2000 build 8.00.2223
925678?(http://support.microsoft.com/kb/925678/) FIX: Error message when you schedule a Replication Merge Agent job to run after you install SQL Server 2000 Service Pack 4: “The process could not enumerate changes at the ‘Subscriber’”
925419?(http://support.microsoft.com/kb/925419/) FIX: The server stops responding, the performance is slow, and a time-out occurs in SQL Server 2000
SQL Server 2000 build 8.00.2226
925684?(http://support.microsoft.com/kb/925684/) FIX: You may experience one or more symptoms when you run a “CREATE INDEX” statement on an instance of SQL Server 2000
925732?(http://support.microsoft.com/kb/925732/) FIX: You may receive inconsistent comparison results when you compare strings by using a width sensitive collation in SQL Server 2000
SQL Server 2000 build 8.00.2229
927186?(http://support.microsoft.com/kb/927186/) FIX: Error message when you create a merge replication for tables that have computed columns in SQL Server 2000 Service Pack 4: “The process could not log conflict information”
SQL Server 2000 build 8.00.2231
928079?(http://support.microsoft.com/kb/928079/) FIX: The Sqldumper.exe utility cannot generate a filtered SQL Server dump file when you use the Remote Desktop Connection service or Terminal Services to connect to a Windows 2000 Server-based computer in SQL Server 2000
SQL Server 2000 build 8.00.2232
928568?(http://support.microsoft.com/kb/928568/) FIX: SQL Server 2000 stops responding when you cancel a query or when a query time-out occurs, and error messages are logged in the SQL Server error log file
SQL Server 2000 build 8.00.2234
929131?(http://support.microsoft.com/kb/929131/) FIX: In SQL Server 2000, the synchronization process is slow, and the CPU usage is high on the computer that is configured as the Distributor
929440?(http://support.microsoft.com/kb/929440/) FIX: Error messages when you try to update table rows or insert table rows into a table in SQL Server 2000: “644″ or “2511″
SQL Server 2000 build 8.00.2238
929410?(http://support.microsoft.com/kb/929410/) FIX: Error message when you run a full-text query in SQL Server 2000: “Error: 17883, Severity: 1, State: 0″
931932?(http://support.microsoft.com/kb/931932/) FIX: The merge agent fails intermittently when you use merge replication that uses a custom resolver after you install SQL Server 2000 Service Pack 4
SQL Server 2000 build 8.00.2239
930484?(http://support.microsoft.com/kb/930484/) FIX: CPU utilization may approach 100 percent on a computer that is running SQL Server 2000 after you run the BACKUP DATABASE statement or the BACKUP LOG statement
SQL Server 2000 build 8.00.2241
932697?(http://support.microsoft.com/kb/932697/) FIX: A calculated member that uses the DistinctCount function always returns 0 when you query a virtual cube that contains the calculated member after you install SQL Server 2000 Analysis Services Service Pack 4
SQL Server 2000 build 8.00.2244
934203?(http://support.microsoft.com/kb/934203/) FIX: A hotfix for Microsoft SQL Server 2000 Service Pack 4 may not update all the necessary files on an x64-based computer
SQL Server 2000 build 8.00.2245
933573?(http://support.microsoft.com/kb/933573/) FIX: You may receive an assertion or database corruption may occur when you use the bcp utility or the “Bulk Insert” Transact-SQL command to import data in SQL Server 2000
SQL Server 2000 build 8.00.2246
935465?(http://support.microsoft.com/kb/935465/) An updated version of Sqlvdi.dll is now available for SQL Server 2000
SQL Server 2000 build 8.00.2248
935950?(http://support.microsoft.com/kb/935950/) FIX: The foreign key that you created between two tables does not work after you run the CREATE INDEX statement in SQL Server 2000
SQL Server 2000 build 8.00.2249
936232?(http://support.microsoft.com/kb/936232/) FIX: An access violation may occur when you try to log in to an instance of SQL Server 2000

Symptoms
The sqlmaint utility does not generate a message when attempting to back up the transaction log from a database that has the truncate log on checkpoint option set. This is also true when using the Database Maintenance Plan Wizard.
The backup of the log takes place and a blank file is created. However, if you run the backup by using the SQL Query Analyzer, the following error message occurs:

Server: Msg 4208, Level 16, State 1, Line 1
BACKUP LOG is not allowed while the trunc. log on chkpt. option is enabled. Use BACKUP DATABASE or disable the option using sp_dboption.
Server: Msg 3013, Level 16, State 1, Line 1
Backup or restore operation terminating abnormally.
Resolution
You can get SQL Server to report an error message if you have it write to either an HTML file or to a table in the msdb database. Use the following Sqlmaint.exe parameters:HtmlRpt, which writes to an HTML file.
-or-
WriteHistory, which writes a history to msdb.dbo.sysdbmaintplan_history.For example:

C:\MSSQL7\Binn>sqlmaint -D pubs -S servername -U sa -BkUpLog “c:\temp\pubslog.bak” -BkUpMedia DISK -UseDefDir -HtmlRpt “c:\temp\sqlmaint.htm”

Symptoms
The following error message may be returned to a Transact-SQL debugger, and reported in the SQL Server Errorlog, when you attempt to debug a Transact-SQL statement or a stored procedure:

SqlDumpExceptionHandler: Process %i generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.The preceding error message appears in the Transact-SQL debugger included with Microsoft Visual C++, while the following error message appears in the Transact-SQL debugger included with Microsoft Visual Basic:

Process %i generated fatal exception c0000005Because the client applications parse the error message, the exact error message may vary from client to client. The Transact-SQL debuggers included in various development environments in this case.
Resolution
This error message occurs when the Configuration Function @@Servername returns Null.
To verify this, open Query Analyzer, connect to the server, and then run the following statement:

Select @@Servername Normally, this code returns the Microsoft Windows NT machine name of the server.

Symptoms
When using SQL CLR stored procedures, user defined functions, user defined data types, or user defined aggregates, you many notice one or more of the following error messages being logged in the SQL server error log when running on a 32 bit instance of either SQL Server 2005 or 2008 
Error message 1
Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0×8007000e.
You may fix the problem and try again later.
Error message 2
Msg 6511, Level 16, State 20, Line 1
Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0×80131022.
You may fix the problem and try again later.
Error message 3
Msg 6512, Level 16, State 27, Line 2
Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0×80004005.
You need to restart SQL server to use CLR integration features.
Error message 4
Msg 6513, Level 16, State 27, Line 1
Failed to initialize the Common Language Runtime (CLR) v2.0.50727 due to memory pressure.
Please restart SQL server in Address Windowing Extensions (AWE) mode to use CLR integration
features.
Error message 5
6513: Failed to initialize the Common Language Runtime (CLR) v2.0.50727 due to memory pressure.
This is probably due to memory pressure in the MemToLeave region of memory.
For more information, see the CLR integration documentation in SQL Server Books Online.
Error message 6
Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0×80131522.
You need to restart SQL server to use CLR integration features.
Additionally, you may see the above error messages with SQL Server 2008 features which use SQL CLR internally, like DMF (Declarative Management Framework) and spatial data types.
Resolution
The error message and HRESULT of the CLR exception can be used to identify the probable cause and likely resolution of the exception
For error messages 1 through 5 above, the most probable cause of these errors is SQL CLR encountering memory pressure. For further information on how to resolve these errors refer to the following article: 969962  Various memory errors are logged to SQL Server error log when using SQL CLR objects
For error message 6, one probable resolution is to reinstall.NET Framework 2.0. To obtain the .NET Framework 2.0, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

Symptoms
Consider the following configuration of a Log Shipping environment:Server A hosts primary server instance and the databaseServer B  hosts secondary server instance and the database Server C hosts a monitor server instance where in the Log Shipping Monitor job is configured to use an impersonated proxy account  for the connections to Server A and Server B.
When you use this configuration, Log Shipping Monitor job incorrectly raises error message 14420 instead of 14421 when the secondary database is out of sync. The description of these error messages in SQL Server 2005 and SQL Server 2008 is as follows:
Error message 14420
Error: 14420, Severity: 16, State: 1
The log shipping primary database %s.%s has backup threshold of %d minutes and has not performed a backup log operation for %d minutes. Check agent log and logshipping monitor information.
Error message 14421
Error: 14421, Severity: 16, State: 1
The log shipping secondary database %s.%s has restore threshold of %d minutes and is out of sync. No restore was performed for %d minutes. Restored latency is %d minutes. Check agent log and logshipping monitor information.
The alert message 14221 indicates that the difference between current time (UTC) and the last_restored_date_utc value in the log_shipping_monitor_secondary table on the monitor server is greater than value that is set for the Restore Alert threshold whereas the alert message 14220 indicates that the difference between current time (UTC) and the last_backup_date_utc value in the log_shipping_monitor_primary table on the monitor server is greater than value that is set for the Backup Alert threshold.
Resolution
The issue happens because of a problem in the Log Shipping user interface. When creating the monitor job for the secondary, 14220 is passed instead of 14221.