<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss Content Posted by Robert Davis
»
Data Typing Quandry
37 posts, Page 2 of 4
««
1
2
3
4
»
»»
Data Typing Quandry
Rate Topic
Display Mode
Topic Options
Author
Message
SanDroid
SanDroid
Posted Wednesday, November 17, 2010 7:23 AM
Ten Centuries
Group: General Forum Members
Last Login: Thursday, January 31, 2013 8:01 AM
Points: 1,232,
Visits: 1,046
Disapointing and Lame trick question.
The question asked which row had the "largest defined row size", not "the largest storage size".
The answer in the the reference material is for a differant question.
Storage size and defined size are two differant concepts.
The following quote is from the books online section on how to choose between ROW and PAGE compression.
Compression can allow more rows to be stored on a page, but does not change the maximum row size of a table or index.
http://msdn.microsoft.com/en-us/library/cc280449.aspx
So even though the maximum storage size of the data is less with compression on, the defined maximum row size of the data is not any differant.
Post #1022146
cy-dba
cy-dba
Posted Wednesday, November 17, 2010 7:29 AM
SSC Eights!
Group: General Forum Members
Last Login: Wednesday, August 17, 2011 7:09 AM
Points: 869,
Visits: 963
SanDroid (11/17/2010)
Disapointing and Lame trick question.
The question asked which row had the "largest defined row size", not "the largest storage size".
The answer in the the reference material is for a differant question.
Storage size and defined size are two differant concepts.
The following quote is from the books online section on how to choose between ROW and PAGE compression.
Compression can allow more rows to be stored on a page, but does not change the maximum row size of a table or index.
http://msdn.microsoft.com/en-us/library/cc280449.aspx
So even though the maximum storage size of the data is less with compression on, the defined maximum row size of the data is not any differant.
I was thinking along the same path, although I thought it still was a good question because I did learn something new.
Post #1022151
SanDroid
SanDroid
Posted Wednesday, November 17, 2010 7:41 AM
Ten Centuries
Group: General Forum Members
Last Login: Thursday, January 31, 2013 8:01 AM
Points: 1,232,
Visits: 1,046
chrs-513176 (11/17/2010)
I was thinking along the same path, although I thought it still was a good question because I did learn something new.
I had already learned the differance between Defined Row size and Storage Row size during my upgrading SQL server skills course.
The differance actually saved us from purchasing a recomended unecessary upgrade for a location.
They were having issues with maxing out the Network during the transfer of a large table that was filled with a lot of un-normalized data. Since the bottle-neck was not in the Disk-IO or the amount of storage being used compression would not have helped. Instead we normalized the data that was being requested from ten large tables joined by an excel formula to one table of just the data being requested using a view.
Creating the view cost less than SQL 2008 Enterprise.
Post #1022156
mtassin
mtassin
Posted Wednesday, November 17, 2010 8:58 AM
Hall of Fame
Group: General Forum Members
Last Login: Today @ 5:42 AM
Points: 3,250,
Visits: 65,542
SanDroid (11/17/2010)
Disapointing and Lame trick question.
The question asked which row had the "largest defined row size", not "the largest storage size".
Compression can allow more rows to be stored on a page, but does not change the maximum row size of a table or index.
http://msdn.microsoft.com/en-us/library/cc280449.aspx
So even though the maximum storage size of the data is less with compression on, the defined maximum row size of the data is not any differant.
I agree. I got this wrong for the same reason. The Row Size doesn't change, compression just lets more data be stored on a page.
--Mark Tassin
MCITP - SQL Server DBA
Proud member of the Anti-RBAR alliance.
For help with Performance click this link
For tips on how to post your problems
Post #1022217
UMG Developer
UMG Developer
Posted Wednesday, November 17, 2010 10:10 AM
SSCrazy
Group: General Forum Members
Last Login: Yesterday @ 2:49 PM
Points: 2,163,
Visits: 2,150
mtassin (11/17/2010)
I agree. I got this wrong for the same reason. The Row Size doesn't change, compression just lets more data be stored on a page.
But in this case compression actually makes it so less data fits on a page because of the metadata overhead.
Post #1022273
SanDroid
SanDroid
Posted Wednesday, November 17, 2010 10:18 AM
Ten Centuries
Group: General Forum Members
Last Login: Thursday, January 31, 2013 8:01 AM
Points: 1,232,
Visits: 1,046
UMG Developer (11/17/2010)
mtassin (11/17/2010)
I agree. I got this wrong for the same reason. The Row Size doesn't change, compression just lets more data be stored on a page.
But in this case compression actually makes it so less data fits on a page because of the metadata overhead.
How does that change that the questioned asked about the
"defined row size"
not the "storage row size"?
These are differant concepts and alters the answer completely.
Post #1022279
bitbucket-25253
bitbucket-25253
Posted Wednesday, November 17, 2010 10:19 AM
SSCertifiable
Group: General Forum Members
Last Login: Today @ 4:33 AM
Points: 5,122,
Visits: 20,365
Using SQL 2008 if one creates 4 tables (1 for each of the create statements in the question). Insert the same number of rows into each table, and then executes the procedure:
sp_estimate_data_compression_savings 'dbo', 'Flags1', NULL, NULL, 'ROW' ;
The answer does
NOT
support the "correct answer",
will the questions author please explain why the difference
If everything seems to be going well, you have obviously overlooked something.
Ron
Please help us, help you -before posting a question please
read
Before posting a performance problem please
read
Post #1022281
UMG Developer
UMG Developer
Posted Wednesday, November 17, 2010 10:25 AM
SSCrazy
Group: General Forum Members
Last Login: Yesterday @ 2:49 PM
Points: 2,163,
Visits: 2,150
SanDroid (11/17/2010)
UMG Developer (11/17/2010)
mtassin (11/17/2010)
I agree. I got this wrong for the same reason. The Row Size doesn't change, compression just lets more data be stored on a page.
But in this case compression actually makes it so less data fits on a page because of the metadata overhead.
How does that change that the questioned asked about the
"defined row size"
not the "storage row size"?
These are differant concepts and alters the answer completely.
I couldn't find any definition for "defined row size", do you have a link to a definition? Does it include metadata?
Post #1022286
SanDroid
SanDroid
Posted Wednesday, November 17, 2010 10:48 AM
Ten Centuries
Group: General Forum Members
Last Login: Thursday, January 31, 2013 8:01 AM
Points: 1,232,
Visits: 1,046
UMG Developer (11/17/2010)
[quote]
I couldn't find any definition for "defined row size", do you have a link to a definition? Does it include metadata?
Exactly my point. The term in the question is "defined row size".
Not storage row size or maximum row size.
Compression can allow more rows to be stored on a page, but does not change the maximum row size of a table or index.
http://msdn.microsoft.com/en-us/library/cc280449.aspx
Also I have noticed that, as has been pointed out by others, the storage concepts in the questions explination may not factual when executed.
Post #1022312
Cliff Jones
Cliff Jones
Posted Wednesday, November 17, 2010 12:09 PM
Hall of Fame
Group: General Forum Members
Last Login: Yesterday @ 2:31 PM
Points: 3,418,
Visits: 3,438
SanDroid (11/17/2010)
UMG Developer (11/17/2010)
[quote]
I couldn't find any definition for "defined row size", do you have a link to a definition? Does it include metadata?
Exactly my point. The term in the question is "defined row size".
Not storage row size or maximum row size.
Compression can allow more rows to be stored on a page, but does not change the maximum row size of a table or index.
http://msdn.microsoft.com/en-us/library/cc280449.aspx
Also I have noticed that, as has been pointed out by others, the storage concepts in the questions explination may not factual when executed.
Yes, I agree with this. Compression has an effect on the storage but does not change the defined row size.
Post #1022388
« Prev Topic
|
Next Topic »
37 posts, Page 2 of 4
««
1
2
3
4
»
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
