Timeline for Table size increase after data alter
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 9, 2016 at 20:33 | history | edited | Martin Smith | CC BY-SA 3.0 |
added 50 characters in body
|
Aug 9, 2016 at 17:38 | history | edited | Martin Smith | CC BY-SA 3.0 |
deleted 58 characters in body
|
Aug 9, 2016 at 17:37 | comment | added | dfundako | You're a gentleman and a scholar. Thanks for the sagely wisdom. | |
Aug 9, 2016 at 17:37 | vote | accept | dfundako | ||
Aug 9, 2016 at 17:36 | comment | added | Martin Smith | @dfundako - yes. | |
Aug 9, 2016 at 17:36 | history | edited | Martin Smith | CC BY-SA 3.0 |
added 130 characters in body
|
Aug 9, 2016 at 17:35 | comment | added | dfundako | Ahhhh. So this is something that could be potentially avoided if there was a sufficient amount of space given by a fill factor to accommodate the additional bytes from the data type change? If the page was 80% full instead of 99%, it would not have to page split? | |
Aug 9, 2016 at 17:31 | history | edited | Martin Smith | CC BY-SA 3.0 |
added 130 characters in body
|
Aug 9, 2016 at 17:23 | comment | added | Martin Smith | @dfundako - It's internalsviewer.codeplex.com but unfortunately is no longer maintained and only works with old versions of SSMS. Will take a look at the link... | |
Aug 9, 2016 at 17:22 | comment | added | dfundako | Very cool row breakdown tool. What do you use? I usually go look straight at the page through DBCC. The MVCE is in the link in the OP that was just published on SQL Server Central using a sample set of data and table from AdventureWorks2014. The leaf offset in your example I can see is 10 bytes of NULL since it was dropped, but in the example through the link the offset only changes by 4. | |
Aug 9, 2016 at 17:08 | history | answered | Martin Smith | CC BY-SA 3.0 |