Fixes Ferret Out SQL Server Bugs

 
 
By Lisa Vaas  |  Posted 2003-03-06
 
 
 

Microsoft Corp. has put out hot fixes for two known bugs in its SQL Server database software.

The first bug is explained in a Microsoft online article entitled "FIX: Cannot Remove Microsoft SQL Server 2000 Desktop Engine After You Upgrade to MSDE 2000 SP2". According to the article, users who originally used a particular build of MSDE and then upgraded to MSDE 2000 SP2 (Service Pack 2) cannot remove MSDE 2000 from their computers.

The build in question, 8.00.194.01, ships in the \MSDE folder on the CD-ROMs of all incarnations of SQL Server 2000: Personal, Evaluation, Developer, Standard and Enterprise. The bug manifests itself when users access the Add/Remove Program applet to remove MSDE 2000. One of two errors result: "The instance name specified is invalid," or "Fatal error during installation."

A similar error results from using the SQL Server 2000 Desktop Engine Setup program (Setup.exe) with the uninstall command line option (/x switch). The problem occurs only when upgrading the MSDE RTM (release to manufacturing) build (194.01) directly to SP2. The problem doesnt occur on any other editions of MSDE 2000, according to Microsoft, of Redmond, Wash. Neither does the problem occur if users first upgrade from the RTM version to MSDE 2000 SP1, then upgrade to MSDE 2000 SP2. The problem can be fixed by installing SP3. The article also provides a hot-fix that was available before the company released the latest SQL Server service pack.

The second bug describes a rare condition in which SQL Server gives the error message "2003-02-10 17:02:54.39 ods The Scheduler 2 appears to be hung. PSS 0x5F8B3110, EC 0x5F8B32C0, UMS Context 0x050D07D8." The Microsoft article "FIX: SQL Server 7.0 Scheduler May Periodically Stop Responding During Large Sort Operation" states that when SQL Server processes a query that includes a large, long-running sort operation, this error message can repeat as frequently as once per minute while the query is running. In some cases, SQL Server might also be slow to respond to other requests.

The article notes that, although Microsoft does support a fix for this problem, it should be applied only to specific machines that are experiencing the scheduler response problem. The hot-fix can be obtained by contacting Microsoft Product Support Services. A complete list of Microsoft Product Support Services phone numbersand information about support costs is on Microsofts Web site.

Latest Security News: Latest Microsoft News:

Search for more stories by Lisa Vaas.
For more Microsoft scoops, check out Ziff Davis Microsoft Watch.

Rocket Fuel