Comments
2 comments
-
Typically a no-op operation occurs when the working base is different from both the revision in source control and the DB, but where the DB and revision in source control is the same.
Can you try unlinking and re-linking the database?
Performing an unlink and re-link will create a new working base. -
Thanks for the help. I tried that procedure, but the problem persisted.
On 4/12/13 an an update for SQL Source Control became available (to 3.3.0.104) and after applying that, I was able to get latest changes.
Add comment
Please sign in to leave a comment.
Failed to update file from source control: [DatabaseObjectId: Name=BBLCustomer, Owner=dbo, ObjectType=Table]. Following objects were no-oped System.Collections.Generic.List`1[RedGate.SQLSourceControl.Engine.Model.DatabaseObjectId]. Last objects no-oped were System.Collections.Generic.List`1[RedGate.SQLSourceControl.Engine.Model.DatabaseObjectId].
If we use SQL Compare 10 directly, it works just fine. if we use SQL Data Compare, it works as well.