Is there any reason to save the schema compare file once you are done comparing, creating scripts or just simply updating?
Sql-server – Visual Studio 2013 and up – Database Project Schema Compare File
sql servervisual studio 2015visual-studio-2013
Related Solutions
Certainly appears you can do that in Visual Studio 2012. I just created a Database Project "database1", then added another database project to the same Solution, named "database2".
I then right-clicked the "Database1" project, clicked "Add Database Reference" and selected the "Database2" project. Then, under "Database Location" I chose "Same Database".
The OBJECTPROPERTY call requires a schema stability (Sch-S) lock, which is only incompatible with a schema modification (Sch-M) lock.
The BULK INSERT will take a Sch-M lock in some circumstances. These are listed in the "Table Locking and Logging During Bulk Import" section of Guidelines for Optimizing Bulk Import in Books Online:
If the destination table is clustered, you may find enabling trace flag 610 helps. Please read the whole series of those posts and the Data Loading Performance Guide and test thoroughly if you decide to go this route.
I have no idea why SSDT checks the IsEncrypted property for tables. I cannot imagine a scenario where that makes sense, but that's a question for the SSDT people.
Best Answer
Short answer, maybe. If being able to open a previously saved .scmp file makes life easier through time savings or consistency, I'd say it's worth saving.
With a schema compare window open, there is a cog wheel icon which opens the
Schema Compare Optionsdialog. There are quite a few options underGeneralandObject Types. Some are selected, others are not selected, by default. If you find yourself repeating compares that require changing the same default settings each time, that would be a compare worth saving.The compare also saves source and target. If one found that when comparing one's
local machine.MyDBtoDevelopment.MyDB, one didn't want to see differences inObjectType X, but one did want to see those differences when comparingDevelopment.MyDBtoQA.MyDB, one could save two separate compares.A .scmp file can also be added to source control, if one found value in doing that as well.
There very well could be other advantages I'm not aware of, but that's about the extent of my limited experience with database projects so far.