Hi @Eitan Blumin ,
Unfortunately, the Azure feedback is in a RIP state now.
Please chime in here: https://learn.microsoft.com/en-us/answers/questions/520845/where-does-one-report-sql-server-or-t-sql-bugs-now.html?childToView=521162#answer-521162
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
In 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:
https://feedback.azure.com/forums/908035-sql-server/suggestions/43852278-add-support-for-prevent-saving-changes-that-requi
Hi @Eitan Blumin ,
Unfortunately, the Azure feedback is in a RIP state now.
Please chime in here: https://learn.microsoft.com/en-us/answers/questions/520845/where-does-one-report-sql-server-or-t-sql-bugs-now.html?childToView=521162#answer-521162
The way to prevent that is to use "IgnoreColumnOrder" option during deployment or stop adding/removing columns to the middle of tables.
The ordinal position of columns in SQL Server has no meaning, except when you use SELECT *.