Add support for "Prevent saving changes that require table re-creation" option in SqlPackage / SSDT
See original GitHub issueIn SQL Server Management Studio, there’s a designer option called “Prevent saving changes that require table re-creation”.
It would be extremely useful to have a similar option in SqlPackage.exe
as well, as it could stop dangerous deployments that could potentially re-create very large tables and severely impact production environments while doing so.
NOTE: This is a re-submission of the Azure feedback item:
Issue Analytics
- State:
- Created 2 years ago
- Comments:17 (5 by maintainers)
Top Results From Across the Web
Add support for "Prevent saving changes that require table ...
In SQL Server Management Studio, there's a designer option called "Prevent saving changes that require table re-creation".
Read more >“Prevent saving changes that require the table to be re- ...
Select or clear the Prevent saving changes that require the table re-creation check box, and then click OK. Share.
Read more >Prevent Saving Changes That Require Table Re-creation ...
Open SQL Server Management Studio; Go to Tools menu then Options; On Options Tree view, Click Designers; Unchecked Prevent saving changes that require...
Read more >Sql Server Prevent Saving Changes That Require Table to ...
The simplest way to bypass this error is to go into Option – Designers and uncheck the option Prevent saving changes that require...
Read more >'Saving changes is not permitted' error when you try to ...
Open SQL Management Studio as an administrator · Go to Tools, then options then "Designer" · Uncheck the Prevent saving changes that require...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We have separate publish profiles for dev and prod. We would likely add this parameter to block on table recreation to both profiles.
Developers deploy to their local db using SSDT + dev publish profile in VS.
I’d imagine developers hitting any issues locally during development, and make necessary adjustments. The production profile would block when deploying to production as a safety net.
Oh! Yes, of course! 😅
Thank you, @ErikEJ for the clarification.
Sorry, @dzsquared , yeah the proposal sounds good to me.
Alternatively, for the sake of consistency, perhaps it would be preferable to make it similar to the “Block…” parameters such as
BlockOnPossibleDataLoss
andBlockWhenDriftDetected
.So, something like /p:BlockOnTableRecreation, maybe?