Timeline for Is automatic disabling of DML triggers possible during SSDT publish?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 8, 2018 at 21:08 | comment | added | Elaskanator | You might consider using a pre and post deploy scripting to manually search for and disable any triggers. My answer below gets you halfway there. You'll want to populate a temporary table with a list of the disabled triggers from the predeploy script then re-enable them in a postdeploy script (making sure to not leave leftover records that would mess up subsequent publishes. | |
| Apr 3, 2018 at 21:20 | answer | added | Elaskanator | timeline score: 1 | |
| Aug 9, 2016 at 14:46 | comment | added | Magier | Any further ideas? | |
| Feb 25, 2016 at 11:14 | comment | added | Magier | Because the whole table is getting re-created and I guess records are put into a temp table and re-inserted to the new table. This should fiire any insert triggers, shoudn't it? | |
| Feb 25, 2016 at 11:07 | comment | added | spaghettidba | Why are you suspecting that DML triggers are slowing you down? | |
| Feb 25, 2016 at 10:55 | history | asked | Magier | CC BY-SA 3.0 |