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 SP4

Article translations Article translations
Article ID: 901212 - View products that this article applies to.
Bug #: 474394 (SQL Server 8.0)
Microsoft distributes Microsoft SQL Server 2000 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 2000 fix release.
Expand all | Collapse all

On This Page

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for installing the hotfix package
  • Whether you must restart the computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package

SYMPTOMS

Consider the following scenario. In Microsoft SQL Server 2000 Service Pack 4 (SP4), you perform one of the following tasks:
  • You use the sp_addalias procedure to add an alias in the user database.
  • You use the sp_dropalias procedure to remove an alias from the user database.
In this scenario, you receive an error message that is similar to the following:
Server: Msg 266, Level 16, State 2, Procedure sp_dropalias, Line 31 Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 0, current count = 1.
Server: Msg 15002, Level 16, State 1, Procedure sp_dropalias, Line 30 The procedure 'sp_dropalias' cannot be executed within a transaction.
This problem occurs when you set the IMPLICIT_TRANSACTIONS option to ON.

CAUSE

This problem occurs because the sp_addalias and sp_dropalias procedures incorrectly run operations that start transactions before the procedures verify that the IMPLICIT_TRANSACTIONS option is set to ON.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have SQL Server 2000 Service Pack 4 (SP4) installed to apply this hotfix.

For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to modify the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) 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 versions
   Date         Time   Version         Size       File name
   ---------------------------------------------------------------
   06-Jun-2005  22:46  8.11.50523.0      239,104  Mssdi98.dll      
   17-May-2005  01:51  2000.80.1025.0     57,904  Osql.exe         
   12-Jul-2005  17:24  2000.80.2148.0    430,080  Pfclnt80.dll     
   17-Jun-2005  00:15                    552,068  Procsyst.sql
   17-Jun-2005  00:15                     18,810  Sp4_serv_qfe.sql
   08-Jul-2005  01:50  2000.80.2148.0    323,584  Sqlagent.exe     
   08-Jul-2005  02:51  2000.80.2148.0    118,784  Sqldiag.exe      
   08-Jul-2005  02:09  2000.80.2148.0    102,400  Sqlfth75.dll     
   08-Jul-2005  16:07  2000.80.2148.0  9,154,560  Sqlservr.exe     
SQL Server 2000 64-bit version
   Date         Time   Version         Size        File name     Platform
   ----------------------------------------------------------------------
   12-Jul-2005  19:42  8.11.50523.0       758,784  Mssdi98.dll   IA-64
   12-Jul-2005  19:41  7.10.3052.4        348,160  Msvcr71.dll   x86
   12-Jul-2005  19:41  2000.80.2148.0   1,187,840  Pfclnt80.dll  IA-64
   12-Jul-2005  19:42                     552,068  Procsyst.sql
   12-Jul-2005  19:42  2000.80.2148.0   1,061,376  Sqlagent.exe  IA-64
   12-Jul-2005  19:42  2000.80.2148.0     334,336  Sqldiag.exe   IA-64
   12-Jul-2005  19:42  2000.80.2148.0     246,784  Sqlfth75.dll  IA-64
   12-Jul-2005  19:42  2000.80.2148.0  30,181,888  Sqlservr.exe  IA-64
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

WORKAROUND

To work around this problem, set the IMPLICIT_TRANSACTIONS option to OFF before you run the sp_addalias procedure or the sp_dropalias procedure.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about the terminology that Microsoft uses when Microsoft corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 901212 - Last Review: October 9, 2011 - Revision: 4.0
APPLIES TO
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Workgroup Edition
Keywords: 
kbautohotfix kbfix kbbug kbhotfixserver kbqfe KB901212

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com