Article ID: 941278 - View products that this article applies to.
IntroductionThis article lists problems that are fixed in Microsoft Visual Studio 2005 Team System Database Professional Post Service Release 1 (SR1) Rollup Package 1.
This update resolves the following problems:
Inconsistent revalidation of database object definitions when you close and then reopen a Visual Studio database projectYou experience inconsistent behavior in the following two scenarios after you disable the Automatically synchronize files with the design-time validation database option in Visual Studio 2005.
A database project cannot be deployed if the project contains interdependent inline functionsWhen interdependent inline functions exist in a database project, the project cannot be deployed in Visual Studio 2005. For example, consider the following scenario. There are two inline functions in a project. The first function selects records from a table that is created in the second function. However, the second function depends on the first function. In this scenario, the project cannot be deployed in Visual Studio 2005.
If you use a four-part name to reference a table, you may receive an incorrect syntax exceptionConsider the following scenario. There are two projects in Visual Studio 2005. These projects are named A and B. The two projects use different databases. Project A references project B. Project A has a stored procedure that contains an ALTER statement. This ALTER statement uses a four-part name to reference a table in project B. Then, the stored procedure is executed. In this scenario, you may receive an incorrect syntax exception that resembles the following:
TSD2010: Incorrect syntax near Table_name. C:\Folder1\Folder2\TestA\Schema Objects\Stored Procedures\dbo.usp_EnableTriggerAcrossDatabase_Errors.proc.sql
Database Professional Interpreter does not handle the "sp_executesql" parameter correctlyWhen you save a stored procedure in a Visual Studio 2005-based project, you may receive a warning message that resembles the following:
Warning: sp_executedsql.@level could not be found
In a Visual Studio 2005 database, you cannot import a schema that was created by using the SQL Server 2000 compatibility modeConsider the following scenario. You have a SQL Server 2005 database schema that was created by using the SQL Server 2000 compatibility mode. The schema uses the old syntax "*=" for an outer join in a stored procedure. Then, you try to import the database schema into a Visual Studio 2005 database project. In this scenario, you may receive the following error messages.
Error message 1
Error message 2
TSD4027: The query uses non-ANSI outer join operators ("*=" or "=*"). To run this query without modification, please set the compatibility level for current database to 80 or lower, using stored procedure sp_dbcmptlevel. It is strongly recommended to rewrite the query using ANSI outer join operators (LEFT OUTER JOIN, RIGHT OUTER JOIN). In the future versions of SQL Server, non-ANSI join operators will not be supported even in backward-compatibility modes. (SQL error = 4147)
TSD2037: The script contains syntax that is not supported by the version of SQL Server that is associated with the database project.
Error message when you use Design-Time Extensibility (DTE) objects: "Do you want to reload"Consider the following scenario. You add some files to Visual Studio 2005 database projects. Or, you add global variables to Visual Studio 2005 database projects by using Design-Time Extensibility (DTE) objects. Then, you save the projects. In this scenario, you receive the following error message for when you try to save each project:
Note To work around this problem, click Ignore in the error message dialog box.
Do you want to reload?
Cross-database references cause slow performance when you load a projectWhen you load a Visual Studio Team System Database Edition project that contains cross-database references, you may experience slow performance. Additionally, Visual Studio 2005 may consume 90 percent or more of the CPU. This behavior occurs because cross-database references significantly increase the time that is required to load a database project.
Note Cross-database references are a new feature that was added in Visual Studio 2005 Team System Database Professional Service Release 1 (SR1).
Schema Compare crashes the Visual Studio IDE when databases contain different versions of assembliesWhen you compare two database schemas, Visual Studio 2005 may stop responding. This problem occurs when those databases contain different versions of the same binary assembly. Additionally, the following event it logged in the event log:
Event Type: clr20r3 Event Source: devenv.exe Event Category: Event ID: 8888 Description: system.indexoutofrangeexception
Schema Compare does not correctly generate the update script for a stored procedureWhen you use Schema Compare in Visual Studio 2005, the operation cannot correctly generate the update script for a stored procedure. This problem occurs when the schema is not a dbo schema.
Note To work around this problem, manually create the custom schema on the destination database. Then, manually transfer each object to that schema.
The schema script is not generated when triggers or views that have the same name existWhen you edit a schema in Visual Studio 2005, the schema script is not generated. This problem occurs when the other schemas contain triggers that are on the same table and that have the same trigger name.
Error message when you build a deployment script: "MSB4018: The 'SqlBuildTask' task failed unexpectedly"When you build a deployment script from the command line or from the Visual Studio 2005 IDE, you may receive the following error message:
Note This problem frequently occurs when you build a script against an existing database.
MSB4018: The "SqlBuildTask" task failed unexpectedly.
After Schema Compare obtains the latest project files from Source Control, Schema Compare indicates that databases are differentConsider the following scenario. The Schema Compare operation obtains the latest version of a Visual Studio 2005 project from Source Control. You check out the database of the project. You run Schema Compare between the checked-out version and the latest version. In this scenario, Schema Compare indicates that these two databases are different.
Rollup package 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:
Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.
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:
PrerequisitesYou must have Visual Studio 2005 Database Professional Service Release 1 (SR1) installed to install this rollup package.
Restart requirementYou do not have to restart the computer after you install this rollup package.
Hotfix replacement informationThis rollup package does not replace any other rollup packages.
File informationThe English version of this rollup package 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 item in Control Panel.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates