Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««1234»»

Data Typing Quandry Expand / Collapse
Author
Message
Posted Wednesday, November 17, 2010 12:32 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, June 16, 2014 9:38 AM
Points: 2,163, Visits: 2,189
Cliff Jones (11/17/2010)
Yes, I agree with this. Compression has an effect on the storage but does not change the defined row size.


But what is the definition for the "defined row size"? Does it include metadata? (Is it a real SQL Server term, or is it just made up?)
Post #1022402
Posted Wednesday, November 17, 2010 12:44 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 7:45 AM
Points: 3,879, Visits: 3,622
UMG Developer (11/17/2010)
Cliff Jones (11/17/2010)
Yes, I agree with this. Compression has an effect on the storage but does not change the defined row size.


But what is the definition for the "defined row size"? Does it include metadata? (Is it a real SQL Server term, or is it just made up?)


Good point. I could not find a reference to that term so I suspect it is made up so therefore the ambiguity. I started to answer correctly, until I noticed that the question was referring to the "defined row size".
Post #1022413
Posted Wednesday, November 17, 2010 2:23 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 8:59 AM
Points: 5,930, Visits: 8,181
Cliff Jones (11/17/2010)
UMG Developer (11/17/2010)
Cliff Jones (11/17/2010)
Yes, I agree with this. Compression has an effect on the storage but does not change the defined row size.


But what is the definition for the "defined row size"? Does it include metadata? (Is it a real SQL Server term, or is it just made up?)


Good point. I could not find a reference to that term so I suspect it is made up so therefore the ambiguity. I started to answer correctly, until I noticed that the question was referring to the "defined row size".

Since, as far as I know, this is not a reserved SQL Server term, I decided to go wild and employ my English language parser.
In my opinion, "defined row size" should refer to the size of the row as defined. And if I look at the table definition, I can't help but notice the "With (Data_Compression = Row)"

So please stop this babbling about a perceived ambiguity, the question is perfectly clear.
All regulars know that I won't hesitate te criticise a question that I feel does not make the bar. This is no such question.



Hugo Kornelis, SQL Server MVP
Visit my SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
Post #1022476
Posted Wednesday, November 17, 2010 2:29 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 7:45 AM
Points: 3,879, Visits: 3,622
Hugo Kornelis (11/17/2010)
Cliff Jones (11/17/2010)
UMG Developer (11/17/2010)
Cliff Jones (11/17/2010)
Yes, I agree with this. Compression has an effect on the storage but does not change the defined row size.


But what is the definition for the "defined row size"? Does it include metadata? (Is it a real SQL Server term, or is it just made up?)


Good point. I could not find a reference to that term so I suspect it is made up so therefore the ambiguity. I started to answer correctly, until I noticed that the question was referring to the "defined row size".

Since, as far as I know, this is not a reserved SQL Server term, I decided to go wild and employ my English language parser.
In my opinion, "defined row size" should refer to the size of the row as defined. And if I look at the table definition, I can't help but notice the "With (Data_Compression = Row)"

So please stop this babbling about a perceived ambiguity, the question is perfectly clear.
All regulars know that I won't hesitate te criticise a question that I feel does not make the bar. This is no such question.


Thanks, I trust your judgment.
Post #1022480
Posted Wednesday, November 17, 2010 2:50 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, January 31, 2013 8:01 AM
Points: 1,232, Visits: 1,046
Hugo Kornelis (11/17/2010)
[quote]
So please stop this babbling about a perceived ambiguity, the question is perfectly clear.
All regulars know that I won't hesitate te criticise a question that I feel does not make the bar. This is no such question.


Hugo,
We would prefer your respect by not calling our criticism babbling.

The with clause in the Table create statements has no relation to if the question is about the Maximum Row size or the Storage Size of the row when stored in a data page.

Some agree with your view, but most that posted about the question do not.
Post #1022492
Posted Wednesday, November 17, 2010 10:28 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, June 30, 2014 2:51 AM
Points: 1,977, Visits: 369
very nice question... thanks
Post #1022619
Posted Thursday, November 18, 2010 1:57 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Thursday, July 3, 2014 2:45 AM
Points: 2,531, Visits: 536
Excellent question, I learned something new.

/Håkan Winther
MCITP:Database Developer 2008
MCTS: SQL Server 2008, Implementation and Maintenance
Post #1022674
Posted Thursday, November 18, 2010 11:01 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 3:55 PM
Points: 13,357, Visits: 10,222
SanDroid (11/17/2010)
Hugo Kornelis (11/17/2010)
[quote]
So please stop this babbling about a perceived ambiguity, the question is perfectly clear.
All regulars know that I won't hesitate te criticise a question that I feel does not make the bar. This is no such question.


Hugo,
We would prefer your respect by not calling our criticism babbling.


We would prefer your respect for the effort that the author has made to create a question so that people could learn about compression, instead of calling it "dissapointing and lame".

As I've learned something from this question, I find it an excellent question and I thank the author for his contribution.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1023061
Posted Thursday, November 18, 2010 12:12 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, January 31, 2013 8:01 AM
Points: 1,232, Visits: 1,046
da-zero (11/18/2010)
[quote]SanDroid (11/17/2010)
[quote]We would prefer your respect for the effort that the author has made to create a question so that people could learn about compression, instead of calling it "dissapointing and lame".


If you look at some of these posts several people asked the author to respond to the fact that they where not able to replicate what he described.

Why where no responses were made?
Did you learn something that was real?
Did you test the concept?

I made an opinionated response about the question and it's content and that is On Topic discussion.

IMHO: Attacking those opinions and calling them Babble and putting Off Topic mis information in the same paragraph helps nobody learn and clarifies nothing.
Post #1023104
Posted Thursday, November 18, 2010 12:43 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, June 16, 2014 9:38 AM
Points: 2,163, Visits: 2,189
SanDroid (11/18/2010)
If you look at some of these posts several people asked the author to respond to the fact that they where not able to replicate what he described.


I can't replicate showing that it actually uses more space, but not having a real definition for "defined row size" doesn't help. (Along with my lack of knowledge of internal storage.)

But the BOL link appears to support the question with these quotes: "In some cases, the metadata overhead might be larger than the old storage format." and "bit: The metadata overhead brings this to 4 bits."
Post #1023120
« Prev Topic | Next Topic »

Add to briefcase «««1234»»

Permissions Expand / Collapse