CTP5 Refresh Available!

Folks, we have produced a small patch that we are making available here designed to address some performance problems around the initial import of existing database schema into the project system, as well as the performance of project reopen scenarios. The improvement, depending on how “big” ( read number of database objects ) your database schema is, can be substantial. We’re not done tuning performance, but we felt that this was such a large step in the right direction, we wanted to share it with you.

I’m including the information that is also on the download page ( again go here to get the bits ) in this post to stress the importance of reading it. Understand that this patch requires CTP5 to be installed. Also, please please please understand that this patch has not gone through the same rigor of testing as our regular CTP releases. Again, we have made this available to garner more feedback from folks experiencing performance problems with the product.

If you do run into problems that you were not experiencing with the stand alone CTP5 bits, we have spent time in making sure that the uninstall of the patch takes you back to the original state of your CTP5 install in case you run into problems.

Here’s the information required for the patch:


After installing via the MSI you need to make sure that the SQL Server instance that is used for design time verification is running under a security account that has access to your project folder; you can change it to either LocalSystem or to the users machine or domain account. To change this, you need to use the SQL Server Configuration Manager, available through Start | Programs | Microsoft SQL Server 2005 | Configuration Tools | SQL Server Configuration Manager.

NOTE: Do not use the Windows Service Manager, since that will not change the ACL’s on the Registry correctly for SQL Server.

After this you need to login to SQL Server as a sysadmin role member and run:

use master
grant execute on sp_detach_db to public

Uninstalling the patch:
In order to uninstall the patch use the command file that is registered in the Visual Studio program folder (see Start | Programs | Microsoft Visual Studio 2005 | Uninstall VSDBPro CTP5 Patch), this will uninstall the patch, cleanup the GAC and repair Visual Studio Team Edition 2005 for Database Professionals CTP5 (it will ask for the install location of CTP5 when you removed this from your local disk).


As always, your feedback is greatly appreciated and welcome, so please, fire away!


Comments (6)

  1. Knaģis says:

    Thanks for the update. Although it does not resolve one particulary painful issue for me. The issue is it creating this script:

    CREATE TRIGGER [dbo].[ActivityHistoryTrigger] ON [dbo].[Activity]


    FOR INSERT, UPDATE, DELETE AS EXTERNAL NAME [ESPSSqlExt].[Triggers].[HistoryTrigger]


    Everything is sort of okay, except for [ESPSHistory] that really should be N’ESPSHistory’. Also it does not think that difference in EXECUTE AS argument is enough to update the specific object.

  2. Yes, this is a bug that we have corrected in the current build ( but not yet ready for public consumption ). Sorry ’bout that!

  3. rafet says:

    I applied the patach and changed the service account to use my domian name login.

    I have also granted the rights to sp_deptach to public and I still recieve an error message:


    Microsoft Visual Studio


    Could not locate entry in sysdatabases for database ‘Catalog_MillenaUS_DB_3a8f0cd8-0108-4409-a5fd-3ae20dce67b6’. No entry found with that name. Make sure that the name is entered correctly.


    OK   Cancel  


    Looking in the SQL exlorer there was another DB there but it had a different GUID after DB_ i renamed this db to the one the project was looking for [Catalog_MillenaUS_DB_3a8f0cd8-0108-4409-a5fd-3ae20dce67b6] I reopen the project and it reprots the same mesage but this time it actually DROPS the database that I have renamed. Reopening the project after that shows the same error.

    Any recomendations or should I uninstall the patch?

  4. MSDN Archive says:

    I had the same issue as rafet, tried a # of things to resolve it, but ultimately found that uninstalling the patch allows projects to be created correctly.

  5. Two things to try. The first is to verify that your local SQLExpress instance is running as LocalSystem ( not NetworkService ). The other is to install SQL Dev Edition and also run that as LocalSystem.

    Hope that helps!