SSC3 doesn't generate DROP statements?
Any advice would be greatly appreciated... :?
If the purpose of SSC3 is to capture and allow the perfect duplication of the end shape of a DB from TFS, then shouldn't it at least offer the option to drop objects that are in the target, but not the source (Drop DB or TFS)?
I'm not seeing this happening with SSC3 in my environment, so I think I'm either missing an option or a basic concept. This is how SQL Compare works Live DB to DB, but not DB to TFS. It WILL generate SQL drop statements based on a compare to TFS, but there seems to be no way to remove the deprecated object definitions from TFS. (Or, preferably, change the object definition to an IF EXISTS DROP to keep it's previous history?)
Shouldn't the SSC3 COMMIT CHANGES tab offer to either remove or alter the definition to a drop for object in TFS but not the DB?
At the very least, it seems that SSC3 should NOT show a DB with the sync icon if there are objects in TFS that are not in the DB.