If we have detected a conflict, it must be in the head to...

penihelpenihel Posts: 2
edited November 30, 2015 11:58AM in SQL Source Control Previous Versions
I have a big problem.

When i link a database that is a customer backup (to fix erros). The SQL Source Control throws this message

If we have detected a conflict, it must be in the head to live set

So i can not run the "Get Latest Version" command. And also the "Commit" command

Someone have any idea ?

I tested with SQL Source Control 3.X and 4.X. The problema is the same in both
Tagged:
· Share on Twitter

Comments

  • Allen LeVanAllen LeVan Posts: 75
    Hello,

    Sorry for the issue you are having with SQL Source Control. We've opened a ticket for this issue so we can troubleshoot and find the cause of this error. You should receive an email from that system shortly, thanks.
    Allen LeVan
    Red Gate Software
    US Product Support
    · Share on Twitter
  • dlrhosseinmdlrhosseinm Posts: 1 New member
    Was there any resolution to this?
    · Share on Twitter
  • Pete_RuizPete_Ruiz Posts: 123 Silver 4

    A support ticket was opened for the customer who reported this issue and was resolved.

    The issue was caused by a stored procedure. The customer had to remove the offending object from source control and add re-add it.

    Are you experiencing the same issue? If so, you can try the following:

    1 - Unlink that database from Source Control
    2 - Close SSMS
    3 - Delete the contents of all subfolders inside %localappdata%\Red Gate\SQL Source Control 4\Caches
    (Please note that %localappdata% is a Windows Environment variable that usually corresponds to C:\Users\{username}\AppData\Local )
    4 - Use SQL Compare to synchronize your DB with the repository
    5 - Relink DB with the repository


    · Share on Twitter
Sign In or Register to comment.