locked
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operatio

    Question

  •  

    Hello,

     

    I upgraded from TFS 2005 SP1 to TFS 2008, also moved from a Single Server to a Dual Server Deploy.  Everything went well, with the exception of a SQL 2005 collation conflict between the SQL TempDB and the TFS Version Control database, found when a developer attempted to add source files to a project in TFS 2008.

     

    Apparently this is a known issue:

     

    In November 2007, the CodeAssassin posted that "Unfortunately collation settings were missed by the TFS team on one of their temp table definitions, it wasn't picked up by testing, dogfooding, or the beta program":

     

    http://www.codeassassin.com/blog/default,month,2007-11.aspx

     

    Also posted here by a TFS Dev member:

    "Yes this problem is occurring because there is a collation difference between your tempdb and the TFSVersionControl db. We try and include the collation in temp table definitions, but it looks like we are missing one in prc_iiUndoPendingChanges. Rebuilding your master db to match your TFSVersionControl db collation will resolve this problem."

     

    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2470181&SiteID=1

     

    This appears to be a well known issue-- is there an ETA for a fix anytime soon in a Hotfix or a Service Pack?

     

    The solution is suggested to be "backup all your databases, uninstall all of SQL Server, reinstall it with the right collation, reapply the service pack, restore all your databases, rebuild the data warehouse and generally do all the rest of the necessary steps."

     

    I cannot do that, as the SQL Server TFS is on is a Line of Business server with many databases.

     

    What I will need to do is create a new instance of SQL 2005 with the correct collations, apply SP2, detach and attach databases, ensure that logins are correct, make changes on Team Foundation Application Tier, etc, etc.

     

    That is alot of work, plus the added (and needless) overhead of another SQL 2005 instance.  *Sigh*

     

    Monday, February 04, 2008 7:03 PM

Answers

  • This is a known issue that Microsoft is aware of, ETA for the fix is unknown.

     

    Two workarounds:

     

    1. Install a separate SQL 2005 instance with the collation that matches the TFSVersion Control database and move the Team Foundation DBs there

     

    2. Rebuild your master db to match your TFSVersionControl db collation

    Wednesday, February 06, 2008 3:27 PM

All replies

  • This is a known issue that Microsoft is aware of, ETA for the fix is unknown.

     

    Two workarounds:

     

    1. Install a separate SQL 2005 instance with the collation that matches the TFSVersion Control database and move the Team Foundation DBs there

     

    2. Rebuild your master db to match your TFSVersionControl db collation

    Wednesday, February 06, 2008 3:27 PM
  • Some DETAILED steps of how to do either of these would be most appreciated while we wait for what should be a SIMPLE hotfix!!

     

    Thursday, March 06, 2008 7:45 PM
  • Just a note that I posted detailed steps in another thread and it seems MS now has a hotfix for this issue.

     

    See:

    http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=2961513&SiteID=1

     

    Monday, March 10, 2008 11:50 PM