RTM of VSDB 2008 GDR R2

The QFE rollup release for the Visual Studio Team System 2008 Database Edition GDR release is now available.

You can download the SETUP.EXE from the regular location. (http://www.microsoft.com/downloads/details.aspx?FamilyID=bb3ad767-5f69-4db9-b1c9-8f55759846ed)

If you have the VS2008 RTM version of the Database Edition or the RTM version of the VSDB 2008 GDR release installed, this setup will automatically upgrade your installation. If you have the RC installed of the QFE rollup, you have to uninstall first and then re-install the GDR.

For more detail on what got fixed in the QFE rollup, please see my previous posting: http://blogs.msdn.com/gertd/archive/2009/03/26/release-candidate-of-gdr-qfe.aspx


The final version number of the is 9.1.40413.00, so you can check in your Help->About  to see if you have the latest version installed.


GertD @ www.DBProj.com

Comments (10)

  1. Visual Studio Team System 2008 Database Edition GDR R2 da oggi disponibile

  2. E' stato da poco rilasciato l' aggiornamento GDR R2 per Studio Team System 2008 Database Edition

  3. The QFE (quick fix engineering) rollup release for Visual Studio Team System 2008 Database Edition GDR

  4. Вчера стал доступен для скачивания GDR R2 для среды разработки Microsoft® Visual Studio Team…

  5. TallGuyNW says:

    Hi Gert

    I recently upgraded to version 9.1.40413.00 and had my first crash today.  We lost our network connectivity at work so I lost connectivity to the TFS server and the folder where my project files are stored.  I wasn’t sure how VSTS would react.  I’d expect to *not* be able to do anything during the outage, but I wasn’t expecting the following.  Perhaps a more graceful handling of this scenario would be better 🙂

    "The general distribution release (GDR) for Visual Studio Team System 2008 Database Edition has encountered a critical error and must exit.  Do you want to try to save your solution and any open documents before exiting?"

    .NET Runtime version 2.0.50727.3053 – Unspecified error

      at System.Data.SqlServerCe.SqlCeCommand.CompileQueryPlan()

      at System.Data.SqlServerCe.SqlCeCommand.ExecuteCommand(CommandBehavior behavior, String method, ResultSetOptions options)

      at System.Data.SqlServerCe.SqlCeCommand.ExecuteResultSet(ResultSetOptions options, SqlCeResultSet resultSet)

      at System.Data.SqlServerCe.SqlCeCommand.ExecuteResultSet(ResultSetOptions options)

      at Microsoft.Data.Schema.SchemaModel.ModelStore.CachedSqlCeCommand.ExecuteResultSet(ResultSetOptions options)

      at Microsoft.Data.Schema.SchemaModel.ModelStore.CachedSqlCeCommand.InsertIntoItemList[TReturn](ICollection`1 list, Converter`2 creator, ResultFilter filter)

      at Microsoft.Data.Schema.SchemaModel.ModelStore.ClearRelationshipEntriesExceptComposingForElementRHS(Int32 elementId, IList`1 elementsToSignal)

      at Microsoft.Data.Schema.SchemaModel.ModelStore.Element.CoreDelete(IList`1 elementsToSignal)

      at Microsoft.Data.Schema.SchemaModel.ModelStore.Element.DeleteWithComposedChildren(List`1& deletedChildren, IList`1 elementsToSignal)

      at Microsoft.Data.Schema.SchemaModel.ModelStore.Element.Delete()

      at Microsoft.Data.Schema.SchemaModel.ModelXmlSerializer.UnloadExternals(DataSchemaModel store, ErrorManager errors, String fileName)

      at Microsoft.Data.Schema.SchemaModel.DataSchemaModel.OnCustomDataRemoved(CustomSchemaData customData)

      at Microsoft.Data.Schema.Sql.SchemaModel.SqlServer.SqlSchemaModel.OnCustomDataRemoved(CustomSchemaData customData)

      at Microsoft.Data.Schema.SchemaModel.DataSchemaModel.RemoveCustomData(CustomSchemaData customData)

      at Microsoft.Data.Schema.Sql.SchemaModel.SqlServer.SqlModelBuilder.Delete(CustomSchemaData dataToDelete)

      at Microsoft.Data.Schema.SchemaModel.FileManager.RemoveCustomSchemaData(String fullPathFilename)

      at Microsoft.Data.Schema.Build.DatabaseTaskHost.RemoveCustomSchemaData(String fullPathFilename)

      at Microsoft.VisualStudio.Data.Schema.Project.Project.Features.FileManagerFeature.ProcessReferencesInQueue()

      at Microsoft.VisualStudio.Data.Schema.Project.Project.Features.FileManagerFeature.OnIdle()

      at Microsoft.VisualStudio.Data.Schema.Project.Project.DatabaseProjectNode.OnIdle()

      at Microsoft.VisualStudio.Data.Schema.Project.Project.DBProjectIdleProcessingComponent.FDoIdle(UInt32 grfidlef)

  6. ALZDBA says:

    I’m trying to figure out how to perform a decent impact analysis for a project if data types or data lengths need to be modified at db-level.

    Can I do that with Datadude GDR R2 or do I need extra add-ons.

    Are there plans on integrating a graphical interface (cfr SSMS database diagram) ?

  7. bayrak says:

    This is very good news was well informed that the followers of the issue I am. Thanks..

  8. Alec says:

    Hey there,

    I have Visual Studio Team System Team Suite 2008 with SP1, latest updates and

    Microsoft® Visual Studio Team System 2008 Database Edition GDR R2 (http://www.microsoft.com/downloads/details.aspx?FamilyID=bb3ad767-5f69-4db9-b1c9-8f55759846ed&displaylang=en) installed.

    In a database project, when I go t to Data -> Schema Compare -> New Schema Comparison, if I select a database that’s part of a web project inside my solution as either Source or Target Schema, I get an errror “Schema Compare does not support the specified database” This doesn’t happen if I select a Project as both Source and Target.

    This looks like a bug, so I posted it on MS Connect. Has anyone else experienced it?


  9. Walt Crosby says:

    We really love the GDR, however, we are seeing a couple of parsing errors.  It appears that the problematic queries have the following features:

    1.  Pivot By commands

    2.  Repeating clauses, without the use of a CTE

    3.  Dynamic SQL clauses

    We have some examples we can get to you if that will help, or should we post the messages on MS Connect?