November 11, 2017 at 11:10 am
Comments posted to this topic are about the item Compressing tables
November 12, 2017 at 12:36 am
Good question thanks Steve,
...
November 13, 2017 at 4:20 am
Nice one, thanks Steve.
Enjoyed the red herrings....
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
November 13, 2017 at 6:16 am
That error mesage has apparently invented a new form of integer arithmentis, in which 8000 + 49 + 10 = 8061. Presumably the internal overhead is actually 12, not 10?
Tom
November 13, 2017 at 7:02 am
I was confused, like Tom. I got the answer correct, but not sure why because 8000 + 49 + 10 = 8059. I looked around for some other internal overhead that may add 2 bytes, but could not find anything. Are there row alignment issues that might add to the row size?
November 13, 2017 at 7:43 am
The error I get indicates 18 bytes of internal overhead:
Msg 1701, Level 16, State 1, Line 6
Creating or altering table 'CompressionTest' failed because the minimum row size would be 8069, including 18 bytes of internal overhead. This exceeds the maximum allowable table row size of 8060 bytes.
Be still, and know that I am God - Psalm 46:10
November 13, 2017 at 9:10 am
I also got 8069 in the error message. (Using 2008R2)
November 13, 2017 at 9:53 am
There may be different results on different versions. I get 8061 on 2014/2016 today.
November 13, 2017 at 10:43 am
For SQL Server 2014+ the minimum row size would be 8061 bytes. This include SQL Server 2017 as well.
For SQL Server 2008 & 2012 the minimum row size would be 8069 bytes.
November 14, 2017 at 6:42 am
What a great question. It's a reminder to always look at the whole picture.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply