Many Conflicts in GetLatest and Commit tab pages
I've created new link to some DB, then commint changes. Then... i've linked some other DB to prevously created link. Now i have many conflicts. For example:
"create procedure dbo.proc1" a version in DB and "create procedure proc1" a version in source control. In my opinion by linking to existing DB in source control get lates step should be done. To equal both versions.
If your database matches what is in source control, we now update your underlying working folder after you link a db so that you don’t see these conflicts on the Commit/Get tabs.
There are some known issues when linking a non-empty db to an existing source control repository. It's hard for us to know which version the db is at. We try to match objects by type and name. If the objects in the db exactly match the latest version in source control, then we can update your local source control version information and the identical objects should NOT appear on the Commit/Get Latest tabs. At this point, you can start working with SQL Source Control from both dbs.
Do you see identical objects on your Commit/Get Latest tabs? Or, have they been slighlty changed? If the objects are actually identical, then we are having a problem parsing the objects. Could you email firstname.lastname@example.org a copy of the objects that are in your db?
For now, you could link an empty db to source control and get latest. This should allow you to keep working, but the contents of the db will be empty. (You could use our SQL Data Compare to synchronize the data from your old db to this new db.)
You could also take a backup of the current db that is linked to source control correctly and has nothing on the Get Latest tab. Then restore this to a second location and try linking this. This should link the db successfully and nothing should be on the Get Latest tab since the db you just restored was an exact copy of the latest source control version.