Maximum bytes per row?

Question

Post reply

Maximum bytes per row?

rhunt

SSCertifiable

Points: 5868
More actions
March 1, 2005 at 8:43 am

#162876

I am curious about the maximum bytes per row of 8060 for SQL 7.0 and SQL 2000. What EXACTLY are the rules for this?. I seems rather self explanatory, but one text or image column with a maximum of 2GB would not be possible if there were no exceptions.
Is the limit only on character data? If so, does this mean that two CHAR(4031) columns would exceed the max capacity for the row?
Thanks in advance.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

rhunt SSCertifiable Points: 5868 More actions · Answer 1

Disregard. I finally found exactly what I was looking for in BOL.

Ryan

Jeff Moden SSC Guru Points: 1004415 More actions · Answer 2

What's the lookup in BOL that proved so useful?

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

rhunt SSCertifiable Points: 5868 More actions · Answer 3

A combination of:

SQL Server Architecture --> Pages and Extents

and...

Accessing and Changing Relational Data --> Managing ntext, text, and image data.

Jeff Moden SSC Guru Points: 1004415 More actions · Answer 4

Thanks for the info!

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Frank Kalis SSC Guru Points: 111183 More actions · Answer 5

While 8060 is the max size, there are circumstances where this doesn't hold true, if I understand it correct.

This might provide additional interesting informations:

http://www.sql.co.il/ug/01/Row%20Size%20Riddle.ppt

http://www.sqlservercentral.com/columnists/sjones/pagesize.asp

--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

Jeff Moden SSC Guru Points: 1004415 More actions · Answer 6

After reading the links that Frank posted and reading "Estimating Table Size" in BOL AND reading "Data Types" in BOL, I've kind of decided that it's just easier to remember not to take anything to the max, if possible. I'll always plan for 8000 and if I get into trouble somewhere, I've got a little bit I can play with.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)