Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control

Categories

JUMP TO ANOTHER FORUM

(thinking…)

BUG? "Changes to commit" icon, however, there are no changes

We have some databases that get hammered overnight, tables are created, dropped so on (don’t ask, 3rd party databases = fail). Anyways, by the following day the database is back to its original state (schema wise). The databases have a "changes to commit" icon, however, when i right click and select "commit changes to source control..." it never finds anything different and i get "No objects with changes to be committed to source control".

This is repeatable and happens most mornings.

8 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Jordon Pilling shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Jordon Pilling commented  ·   ·  Report

    If you have problems downloading the screen recording, try right-clicking and using "Save Target As..."

  • Jordon Pilling commented  ·   ·  Report

    Hello Chris, Sorry for the delay, only just spotted your comment!

    I am aware of the grey blobs and have no problem with them, the issue outlined above is separate to the grey blobs. It happens every morning, I came in this morning, Unlocked my computer, and hey presto, our main database server has a blue blob on a database, i right-click, Select "Commit Changes", i then wait for ages whilst its checks (its a very big database). After a minute or so, it finds no differences and the blue blob disappears!

    I took the liberty of running a screen capture of this, you can download the recording here:

    http://www.heavencore.co.uk/filehub/Videos/RedGate2.wmv

    Please advise.

  • AdminChris Auckland (Admin, Redgate) commented  ·   ·  Report

    Thanks for your post.

    When you first open SSMS each database that is linked to a repository should have a 'grey' blob in front of the green database indicator. This doesn't mean that there are changes needing to be committed, but rather that SQL Source Control hasn't checked for differences yet.

    If you click on the database name, or expand the database, then the 'grey' blob should start spinning and turn blue if there is anything to commit, or disappear if there isn't.

    Does this explain what's happening, or do you have blue blobs appearing when there is nothing to commit?