tag:blogger.com,1999:blog-7129367241107972697.post420890161322425699..comments2014-04-30T13:47:17.082+02:00Comments on SQL Server Musings: Heaps Of TroubleSean Pearcehttps://plus.google.com/111863736979089341097noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7129367241107972697.post-70521506283941284372013-10-18T19:58:00.757+02:002013-10-18T19:58:00.757+02:00Thanks! Here I was thinking it was some clever wa...Thanks! Here I was thinking it was some clever way of establishing row size. I should have looked at the obvious. :)Jeffhttp://www.blogger.com/profile/13212106683775743802noreply@blogger.comtag:blogger.com,1999:blog-7129367241107972697.post-79190296881746942152013-10-18T19:16:08.612+02:002013-10-18T19:16:08.612+02:00That is the maximum possible row size for the data...That is the maximum possible row size for the data.<br />varchar(150)<br />varchar(15)<br />varchar(1)<br />So 166 single byte characters if each column was full, i.e. a worst case scenario.Sean Pearcehttp://www.blogger.com/profile/15769604002687268779noreply@blogger.comtag:blogger.com,1999:blog-7129367241107972697.post-32876149156607414592013-10-18T17:18:35.663+02:002013-10-18T17:18:35.663+02:00Sean,
In your above row size math you use X * 166...Sean,<br /><br />In your above row size math you use X * 166 to bytes. (And I understand this may be a bonehead question...) How did you derive that number?<br /><br />Thanks,<br /><br />-Jeff Jeffhttp://www.blogger.com/profile/13212106683775743802noreply@blogger.com