[SOLVED] SSC Not seeing changes, but SQL Compare can

jarofclay

It's not the exclusion list because both of them show those as being excluded. What could be happening that would cause us not to be able to see the changes in SSC?

We have tried unlinking and relinking the database as shared or dedicated and none of those seem to work.

jarofclay

Bump. This just happened recently with the last update. I'm not sure why we need Source Control if it can't detect changes??

James B

Hi,

Just to confirm, you've upgraded and now, no matter what change you make to your database, nothing shows up on the commit tab?

Is this the case even forcing a click of the refresh button?

If you unlink and then link to an "evaluation repository", can you see everything and commit? And can you then make further changes?

jarofclay

Just to confirm, you've upgraded and now, no matter what change you make to your database, nothing shows up on the commit tab?

Correct, even after pushing refresh, linking and unlinking, etc

If you unlink and then link to an "evaluation repository", can you see everything and commit? And can you then make further changes?

Now this will show us the changes if we point to an empty created repository (we are using Mercurial) and so we know that is working, but as soon as we point back to our existing repo it stops seeing anything new. We even deleted the repo and recreated it and still no changes. Any ideas? We are trying to push out new schema changes to a bunch of systems and we have become to reliant on SSC working!

jarofclay

I think we found a bug. We have some objects that we ignore when testing that we start with an underscore "_". So we have a filter rule that ignores those.

We played around with this and removed that filter and everything showed up (even object names that don't start with the underscore) so something seems off with the filter.

We can work around it for now since we now see and can commit changes (Whew!), but there might be something going on there with the filters.

Cheers.

James B

Thanks for the update- you may be right, I think i've seen a bug logged with Compare that sounds pretty similar.
SQL Source Control should get fixed once it inherits the fixed Compare engine, so one of the next updates should sort it.