Timeline for Performing large amounts of schema updates and transaction log issues
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2018 at 14:47 | history | edited | Craig Walker | CC BY-SA 4.0 | added 886 characters in body |
| May 23, 2018 at 14:43 | comment | added | Craig Walker | unfortunately we don't have control over the backups and the customers use anything from express to enterprise 2008 upwards. | |
| May 23, 2018 at 13:53 | vote | accept | Craig Walker | ||
| May 23, 2018 at 13:12 | answer | added | sepupic | timeline score: 0 | |
| May 23, 2018 at 12:57 | comment | added | Dan Guzman | Adding a new NOT NULL column with a default constraint and WITH VALUES is a meta-data only operation in Enterprise Edition, avoiding the excessive logging. | |
| May 23, 2018 at 12:32 | comment | added | Liya Tansky | 2. I would consider adding a column with Null, setting the default value in batches and only then adding the constraint and setting the NOT NULL | |
| May 23, 2018 at 12:31 | comment | added | Liya Tansky | 1. can your script run full backup and transaction log backup before you start running? | |
| May 23, 2018 at 12:24 | review | First posts | |||
| May 23, 2018 at 13:36 | |||||
| May 23, 2018 at 12:23 | history | asked | Craig Walker | CC BY-SA 4.0 |