SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Data Typing Quandry


Data Typing Quandry

Author
Message
SanDroid
SanDroid
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2348 Visits: 1046
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.
cy-dba
cy-dba
SSCommitted
SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)

Group: General Forum Members
Points: 1515 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.
SanDroid
SanDroid
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2348 Visits: 1046
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.
mtassin
mtassin
SSCertifiable
SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)

Group: General Forum Members
Points: 7024 Visits: 72521
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
UMG Developer
UMG Developer
Hall of Fame
Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)

Group: General Forum Members
Points: 3898 Visits: 2204
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.
SanDroid
SanDroid
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2348 Visits: 1046
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.
bitbucket-25253
bitbucket-25253
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14993 Visits: 25280
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
UMG Developer
UMG Developer
Hall of Fame
Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)

Group: General Forum Members
Points: 3898 Visits: 2204
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?
SanDroid
SanDroid
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2348 Visits: 1046
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.
Cliff Jones
Cliff Jones
SSCertifiable
SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)

Group: General Forum Members
Points: 5127 Visits: 3648
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search