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
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. On This PageSUMMARYThis article describes the following about this hotfix
release:
SYMPTOMSConsider the following scenario. In Microsoft SQL Server 2000 Service Pack 4 (SP4), you perform one of the following tasks:
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.CAUSEThis 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. RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. 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.PrerequisitesYou 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 (http://support.microsoft.com/kb/290211/)
How to obtain the latest SQL Server 2000 service pack
Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to modify the registry.Hotfix file informationThis 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 versionsDate 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 versionDate 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-64Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files. WORKAROUNDTo work around this problem, set the IMPLICIT_TRANSACTIONS option to OFF before you run the sp_addalias procedure or the sp_dropalias procedure. STATUSMicrosoft
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 (http://support.microsoft.com/kb/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 (http://support.microsoft.com/kb/824684/)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
| Article Translations
|
Back to the top
