FIX: The Transact-SQL debugger automatically saves changes to a script file when you run the script in debugging mode in SQL Server 2008 Management Studio

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

SYMPTOMS

Consider the following scenario. You use a language other than Transact-SQL to write a script. You open the script file in Microsoft SQL Server 2008 Management Studio (SSMS) and then change the script file. In this scenario, when you run the script in debugging mode, the Transact-SQL debugger automatically saves the changes that you made to the script file. That is, the Transact-SQL debugger does not prompt you to save the changes.

CAUSE

This issue occurs if you use the Transact-SQL debugger in SSMS. Although the Transact-SQL debugger uses the Visual Studio debugging interface for all script languages, this issue occurs especially for script languages other than Transact-SQL. The Transact-SQL debugger incorrectly inherits the same functionality as that of the script language.

RESOLUTION

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
958186 Cumulative update package 2 for SQL Server 2008
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

WORKAROUND

To work around this issue, make a backup of the original script file before you run the script file in debugging mode.

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 what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
958186 Cumulative update package 2 for SQL Server 2008

REFERENCES

For more information about the list of builds that are available after the release of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for 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 software update terminology, 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: 956216 - Last Review: August 21, 2008 - Revision: 1.1
APPLIES TO
  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Standard
Keywords: 
kbbug kbqfe kbfix kbexpertiseadvanced kbprb KB956216

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