Resolving TFS_SCHEMA_VERSION Errors In Team Foundation Server 2010 Collection Databases
Posted
by Jeff Ferguson
on Geeks with Blogs
See other posts from Geeks with Blogs
or by Jeff Ferguson
Published on Mon, 17 May 2010 20:09:36 GMT
Indexed on
2010/05/18
3:21 UTC
Read the original article
Hit count: 856
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.
© Geeks with Blogs or respective owner