Timeline for SQL Server - Adding non-nullable column to existing table - SSDT Publishing
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2020 at 15:22 | comment | added | Bob Horn | That makes sense. Thanks for the explanation. | |
| Jan 30, 2020 at 14:17 | comment | added | Josh Darnell | @BobHorn It's manual, and different depending on each project / organization's preferences. In my case, I have a step in my build pipeline that copies the script to a known location alongside my other published artifacts like "publish\database\pre-dac.sql"). When I deploy, before running sqlpackage.exe against the dacpac file, I run "pre-dac.sql" via sqlcmd.exe. Hope that helps, I should really write in more detail about this sometime. | |
| Jan 29, 2020 at 17:49 | comment | added | Bob Horn | You say: "In your deployment process, locate and run this script (or scripts) before the SSDT schema compare occurs." Is that a manual step? Or will a publish invoke it? | |
| Jun 12, 2018 at 19:51 | vote | accept | Elaskanator | ||
| Jun 12, 2018 at 18:56 | history | answered | Josh Darnell | CC BY-SA 4.0 |