Behavior related to new/dropped objects

syagla

I'm trying to understand the behavior of how SQL Source Control determines whether an object is new or whether it is old and should be dropped.

Suppose there are 5 objects missing from my working directory schema which are still in source control. If I go to the Get Latest tab, SQL Source Control lists those 5 objects as New and allows me to select them. That all makes sense. However, what if those 5 objects are *supposed* to be removed? If I go to the Commit tab, I would expect to see corresponding Drop actions for those 5 objects because I don't want those 5 objects to show up in source control anymore. I'm not seeing any such option showing up. 

Any advice?

AlexYates

The way it works behind the scenes is documented here:
https://documentation.red-gate.com/soc6/reference-information/how-sql-source-control-works-behind-the-scenes

If this was a fresh link to source control I normally see it come up as a conflict, since SQL Source Control does not know whether the source control or database version is the most up to date.

syagla

Alex - Thank you. Based on that documentation, I think I have an idea of what happened. I recently migrated to a different workstation. I suspect the reason I'm not getting the expected DROP actions under the Commit tab is because the changes to my local database were originally made when I was on my old workstation. I never transferred over any local AppData folder data, therefore SQL Source Control doesn't have the proper level of awareness as to what is going on.

So in this case, my solution was to remove the files from my working directory manually.