Disable drop constraints steps?
I recently ran into an issue trying to use SQL compare to deploy some changes to a test environment. I was adding a nullable column to a table containing a large number of records (hundreds of millions) and it took hours to complete. I retired the same operation manually and it took less than 5 minutes.
The problem was that I stupidly didn't review the generated code before deploying it and missed the fact that the script was dropping a handful of constraints and indexes on the table, adding the column and then re initializing the indexes and constraints. This wasn't acceptable for us. Is there a way to disable this either universally or for specific tables?