Geeks With Blogs
Jeff Ferguson Irritating other people since 1967

I recently backed up a Team Foundation Server 2010 project collection database and restored it onto another server. All of that went well, until I tried to use the restored database on the new server. As it turns out, the old server was running the Release Candidate of TFS 2010 and the new server is running the RTM version of TFS 2010. I ended up with an error message shown on the new server's Team Web Access site about the project collection's TFS_SCHEMA_VERSION property not containing the appropriate value.

As it turns out, TFS_SCHEMA_VERSION is an extended property on the project collection database. I ran the following SQL script against the project collection database restored onto the new server:

EXEC [Tfs_DefaultCollection].sys.sp_dropextendedproperty @name=N'TFS_PRODUCT_VERSION'
GO
EXEC [Tfs_DefaultCollection].sys.sp_addextendedproperty @name=N'TFS_PRODUCT_VERSION', @value=N'10.0.30319.1'
GO
EXEC [Tfs_DefaultCollection].sys.sp_dropextendedproperty @name=N'TFS_SCHEMA_VERSION'
GO
EXEC [Tfs_DefaultCollection].sys.sp_addextendedproperty @name=N'TFS_SCHEMA_VERSION', @value=N'Microsoft Team Foundation Server 2010 (RTM)'
GO

Now, all is well. I can now navigate to http://newserver:8080/tfs/ and see the restored project collection and its contents.

Posted on Monday, May 17, 2010 10:09 PM | Back to top


Comments on this post: Resolving TFS_SCHEMA_VERSION Errors In Team Foundation Server 2010 Collection Databases

# re: Resolving TFS_SCHEMA_VERSION Errors In Team Foundation Server 2010 Collection Databases
Requesting Gravatar...
Please not that this is not recommended nor supported by Microsoft.
Changing the extended properties will only deceive TFS and make him think that the databases have the right schema, but they will not. This could cause troubles in the future and, most important, will leave the TFS databases in an unsupported status.
The right way to migrate a collection from TFS 2010 RC to a TFS 2010 RTM would be to change upgrade the original server to RTM first, and then use the usual procedure to restore the database on the new server.
Left by César Álvarez on Jul 16, 2010 9:38 AM

# re: Resolving TFS_SCHEMA_VERSION Errors In Team Foundation Server 2010 Collection Databases
Requesting Gravatar...
It might not be supported, but this helped me tremendously.. It was a little less risky for me because I was trying to migrate a Project collection from a stand-alone server to an existing enterprise farm. Just as a Note.. the stand-alone server WAS upgraded from RC to RTM.. but the Version numbers WERE different.. also the SCHEMA version property (the real problem) said RTM but it said RTM without the Pararenthesis...

Anyway.. this worked great.. thanks!!
Left by Jesse on Nov 23, 2010 11:57 AM

Your comment:
 (will show your gravatar)


Copyright © Jeff Ferguson | Powered by: GeeksWithBlogs.net