How does SQL Server store a Page ???

Question

Post reply

How does SQL Server store a Page ???

Amit Jethva

SSCarpal Tunnel

Points: 4707
More actions
February 4, 2004 at 5:12 am

#83384

A quick maths.
Size of a SQL page = 8K = 8 * 1024 = 8192 Bytes
Page Header Size = 96 bytes (as per BOL look for Pages and Extents).
so total Free bytes available to SQL Server Page = 8192 - 96 = 8096 bytes.
Again as per BOL, Maximum row size = 8060, which includes row overheads etc..
just to test
create table t ( t1 varchar(8000) , t2 varchar(8000) )
insert t select replicate('0', 8000) ,replicate('0', 48) --- Fails
insert t select replicate('0', 8000) ,replicate('0', 47) --- works
so the maximum size of 8060 is inclusive of all row overheads (in this case 13 bytes)
Now we still have 8096 - 8060 = 36 bytes remaining.
My question is "Where are the rest 36 bytes of information used ?"
please do put forward your thoughts on this.
-- Amit

-- Amit

"There is no 'patch' for stupidity."

Download the Updated SQL Server 2005 Books Online.

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

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

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

This will be interesting for you

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]

Amit Jethva SSCarpal Tunnel Points: 4707 More actions · Answer 2

I did read the article. Nice one.

But it explains why i can use only 8039 bytes of actual data out of maximum 8060 bytes per row allowed.

Still what happens to other 36 bytes in the same page ?

Some search on internet took me to this article. http://www.sqlmag.com/Articles/Index.cfm?ArticleID=4885

This article explains the data streucture in SQL 7.0

Please read that before proceeding further........

As per that

There is an element on the page called row offset array, which some documentation calls a row offset table. The array has a 2-byte slot for each row in the table. The slot contains the byte offset on the page in which you can locate each row. The array starts with slot 0 at the end of the page, and slot numbers increase as the array grows inward from the bottom of the page. Each row has a row number on the page, and that number is the index in the array for the start of the row. For example, if you need to retrieve row 2 from a data page, SQL Server looks in the third 2-byte slot from the end of the page and finds a byte offset. That offset is the page position of the data row.

I wonder if

a. the same applies for SQL 2000

b. if the concept of row byte offset is true, what will happen when the page contains only 1 row (8060 in size) and

c. if the concept of row byte offset is true, what will happen when the page contains 1000 rows each of 8 in size (if thats the minimum create table test ( col1 bit not null), the row size would be 1 for col1 , 4 for row header + 3 for nul bitmap , i used formula given by msdn http://msdn.microsoft.com/library/default.asp?url=/library/en-us/createdb/cm_8_des_02_92k3.asp&nbsp

this is turning really intresting topic for me.

--- amit

-- Amit

"There is no 'patch' for stupidity."

Download the Updated SQL Server 2005 Books Online.

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

This is the same sequence from Inside SQL Server 2000

Row Offset Array

The row offset array is a block of 2-byte entries, each of which indicates the offset on the page on which the corresponding data row begins. Every row has a 2-byte entry in this array. Although these bytes aren't stored in the row with the data, they do affect the number of rows that will fit on a page.

The row offset array indicates the logical order of rows on a page. For example, if a table has a clustered index, SQL Server will store the rows in the order of the clustered index key. This doesn't mean that the rows will be physically stored on the page in the order of the clustered index key. Rather, slot 0 in the offset array will refer to the first row in the order, slot 1 will refer to the second row, and so forth. As we'll see shortly when we examine an actual page, the offset of these rows can be anywhere on the page.

There's no internal global row number for every row in a table. SQL Server uses the combination of file number, page number, and slot number on the page to uniquely identify each row in a table.

Never experimented with that, but why not try it out, create both test scenarios and examine what happens after inserting by looking at the data page?

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

Amit Jethva SSCarpal Tunnel Points: 4707 More actions · Answer 4

I did a bit of testing like this. Got some results which i could not understand.

-- create a smallest table possible in SQL

create table test1 ( col1 char(1) not null)

insert test1 select 'A'

dbcc showcontig ( 693577509 ) -- object id of test1

-----------------------------------------------------------------------

DBCC SHOWCONTIG scanning 'test1' table...

Table: 'test1' (693577509); index ID: 0, database ID: 13

TABLE level scan performed.

- Pages Scanned................................: 1

- Extents Scanned..............................: 1

- Extent Switches..............................: 0

- Avg. Pages per Extent........................: 1.0

- Scan Density [Best Count:Actual Count].......: 100.00% [1:1]

- Extent Scan Fragmentation ...................: 0.00%

- Avg. Bytes Free per Page.....................: 8085.0

- Avg. Page Density (full).....................: 0.11%

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

-----------------------------------------------------------------------

-- one more row insert

insert test1 select 'A'

dbcc showcontig ( 693577509 ) -- object id of test1

-----------------------------------------------------------------------

DBCC SHOWCONTIG scanning 'test1' table...

Table: 'test1' (693577509); index ID: 0, database ID: 13

TABLE level scan performed.

- Pages Scanned................................: 1

- Extents Scanned..............................: 1

- Extent Switches..............................: 0

- Avg. Pages per Extent........................: 1.0

- Scan Density [Best Count:Actual Count].......: 100.00% [1:1]

- Extent Scan Fragmentation ...................: 0.00%

- Avg. Bytes Free per Page.....................: 8074.0

- Avg. Page Density (full).....................: 0.25%

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

-----------------------------------------------------------------------

-- one more row insert

insert test1 select 'A'

dbcc showcontig ( 693577509 ) -- object id of test1

-----------------------------------------------------------------------

DBCC SHOWCONTIG scanning 'test1' table...

Table: 'test1' (693577509); index ID: 0, database ID: 13

TABLE level scan performed.

- Pages Scanned................................: 1

- Extents Scanned..............................: 1

- Extent Switches..............................: 0

- Avg. Pages per Extent........................: 1.0

- Scan Density [Best Count:Actual Count].......: 100.00% [1:1]

- Extent Scan Fragmentation ...................: 0.00%

- Avg. Bytes Free per Page.....................: 8063.0

- Avg. Page Density (full).....................: 0.38%

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

-----------------------------------------------------------------------

so now i have found out every row inserted in this smallest table takes out 11 bytes out of the page allocated to it.

As per MSDN my row size = 8

( Total row size (Row_Size) = Fixed_Data_Size + Variable_Data_Size + Null_Bitmap +4 = 1 + 0 + 3 + 4 = 8 where Null_Bitmap = 2 + (( Num_Cols + 7) / 8 ) = 2 + 1 = 3 )

Now I am thinking where are additional 3 bytes per row being used ?????

-- Amit

"There is no 'patch' for stupidity."

Download the Updated SQL Server 2005 Books Online.

swjohnson Hall of Fame Points: 3254 More actions · Answer 5

The best explanation of this I read was in a book by Ken England "Microsoft SQL Server 2000 Performance Optimization and Tuning Handbook". He explained it in great details over about 10 pages with pictures and explanations. I don't have the book here at work but it is well worth the $$$$.

If you use the DBCC Page { dbid | dbName, file ID, page number} ( I believe this is an undocumented DBCC command)

So it would look something like DBCC Page ('dbBanking',1,30) and you will have to turn on DBCC TRACEON (3604) to get any useful info.

SJ

Accepting all invites

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

Yes, that's what I meant earlier. Here's a sample usage of dbcc page.

use pubs

go

dbcc traceon(3604)

go

dbcc page(5,1,88,1)

This is the result

DBCC-Ausführung abgeschlossen. Falls DBCC Fehlermeldungen ausgegeben hat, wenden Sie sich an den Systemadministrator.

PAGE: (1:88)

------------

BUFFER:

-------

BUF @0x00E17F00

---------------

bpage = 0x19FB8000 bhash = 0x00000000 bpageno = (1:88)

bdbid = 5 breferences = 1 bstat = 0x209

bspin = 0 bnext = 0x00000000

PAGE HEADER:

------------

Page @0x19FB8000

----------------

m_pageId = (1:88) m_headerVersion = 1 m_type = 1

m_typeFlagBits = 0x0 m_level = 0 m_flagBits = 0x0

m_objId = 1977058079 m_indexId = 0 m_prevPage = (0:0)

m_nextPage = (0:0) pminlen = 24 m_slotCnt = 23

m_freeCnt = 6010 m_freeData = 2136 m_reservedCnt = 0

m_lsn = (3:242:2) m_xactReserved = 0 m_xdesId = (0:0)

m_ghostRecCnt = 0 m_tornBits = -2147483591

Allocation Status

-----------------

GAM (1:2) = ALLOCATED SGAM (1:3) = ALLOCATED

PFS (1:1) = 0x20 MIXED_EXT 0_PCT_FULL DIFF (1:6) = CHANGED

ML (1:7) = NOT MIN_LOGGED

DATA:

-----

Slot 0, Offset 0x631

--------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB8631: 00180030 20383034 2d363934 33323237 0...408 496-7223

19FB8641: 34394143 01353230 00000009 00330005 CA94025.......3.

19FB8651: 003f0038 0058004e 2d323731 312d3233 8.?.N.X.172-32-1

19FB8661: 57363731 65746968 6e686f4a 316e6f73 176WhiteJohnson1

19FB8671: 32333930 67694220 52206567 654d2e64 0932 Bigge Rd.Me

19FB8681: 206f6c6e 6b726150 nlo Park

Slot 1, Offset 0xb8

-------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB80B8: 00180030 20353134 2d363839 30323037 0...415 986-7020

19FB80C8: 34394143 01383136 00000009 00330005 CA94618.......3.

19FB80D8: 00400038 00580051 2d333132 382d3634 8.@.Q.X.213-46-8

19FB80E8: 47353139 6e656572 6a72614d 6569726f 915GreenMarjorie

19FB80F8: 20393033 64723336 2e745320 31342320 309 63rd St. #41

19FB8108: 6b614f31 646e616c 1Oakland

Slot 2, Offset 0x110

--------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB8110: 00180030 20353134 2d383435 33323737 0...415 548-7723

19FB8120: 34394143 01353037 00000009 00330005 CA94705.......3.

19FB8130: 003f0039 0055004d 2d383332 372d3539 9.?.M.U.238-95-7

19FB8140: 43363637 6f737261 6568436e 356c7972 766CarsonCheryl5

19FB8150: 44203938 69777261 6e4c206e 7265422e 89 Darwin Ln.Ber

19FB8160: 656c656b 79 keley

Slot 3, Offset 0x522

--------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB8522: 00180030 20383034 2d363832 38323432 0...408 286-2428

19FB8532: 35394143 01383231 00000009 00330005 CA95128.......3.

19FB8542: 0041003a 005d0055 2d373632 322d3134 :.A.U.].267-41-2

19FB8552: 4f343933 61654c27 694d7972 65616863 394O'LearyMichae

19FB8562: 2032326c 76656c43 6e616c65 76412064 l22 Cleveland Av

19FB8572: 3123202e 6e615334 736f4a20 65 . #14San Jose

Slot 4, Offset 0x374

--------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB8374: 00180030 20353134 2d343338 39313932 0...415 834-2919

19FB8384: 34394143 01393036 00000009 00330005 CA94609.......3.

19FB8394: 003f003b 0056004f 2d343732 392d3038 ;.?.O.V.274-80-9

19FB83A4: 53313933 69617274 44746867 356e6165 391StraightDean5

19FB83B4: 20303234 6c6c6f43 20656765 4f2e7641 420 College Av.O

19FB83C4: 616c6b61 646e akland

Slot 5, Offset 0x7ff

--------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB87FF: 00180030 20333139 2d333438 32363430 0...913 843-0462

19FB880F: 3636534b 00343430 00000009 00330005 KS66044.......3.

19FB881F: 003f0038 00590051 2d313433 312d3232 8.?.Q.Y.341-22-1

19FB882F: 53323837 6874696d 6e61654d 31726564 782SmithMeander1

19FB883F: 694d2030 73697373 70706973 72442069 0 Mississippi Dr

19FB884F: 77614c2e 636e6572 65 .Lawrence

Slot 6, Offset 0x60

-------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB8060: 00180030 20353134 2d383536 32333939 0...415 658-9932

19FB8070: 34394143 01353037 00000009 00330005 CA94705.......3.

19FB8080: 00400039 00580050 2d393034 372d3635 9.@.P.X.409-56-7

19FB8090: 42383030 656e6e65 72624174 6d616861 008BennetAbraham

19FB80A0: 33323236 74614220 6e616d65 2e745320 6223 Bateman St.

19FB80B0: 6b726542 79656c65 Berkeley

Slot 7, Offset 0x478

--------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB8478: 00180030 20353134 2d363338 38323137 0...415 836-7128

19FB8488: 34394143 01313033 00000009 00330005 CA94301.......3.

19FB8498: 003a0037 00520049 2d373234 322d3731 7.:.I.R.427-17-2

19FB84A8: 44393133 416c6c75 34336e6e 42203031 319DullAnn3410 B

19FB84B8: 646e6f6c 74532065 6c61502e 6c41206f londe St.Palo Al

19FB84C8: 6f74 to

Slot 8, Offset 0x57f

--------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB857F: 00180030 20373037 2d383339 35343436 0...707 938-6445

19FB858F: 35394143 01383234 00000009 00330005 CA95428.......3.

19FB859F: 0041003d 0051004b 2d323734 322d3732 =.A.K.Q.472-27-2

19FB85AF: 47393433 676e6972 6273656c 72754279 349GringlesbyBur

19FB85BF: 204f5074 20786f42 43323937 6c65766f tPO Box 792Covel

19FB85CF: 6f o

Slot 9, Offset 0x73e

--------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB873E: 00180030 20353134 2d353835 30323634 0...415 585-4620

19FB874E: 34394143 01303331 00000009 00330005 CA94130.......3.

19FB875E: 0043003b 005f0052 2d363834 312d3932 ;.C.R._.486-29-1

19FB876E: 4c363837 736b636f 4379656c 6c726168 786LocksleyCharl

19FB877E: 31656e65 72422038 7764616f 41207961 ene18 Broadway A

19FB878E: 61532e76 7246206e 69636e61 6f6373 v.San Francisco

Slot 10, Offset 0x5d0

---------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB85D0: 00180030 20353136 2d373932 33323732 0...615 297-2723

19FB85E0: 37334e54 00353132 00000009 00330005 TN37215.......3.

19FB85F0: 00440039 00610058 2d373235 332d3237 9.D.X.a.527-72-3

19FB8600: 47363432 6e656572 726f4d65 676e696e 246GreeneMorning

19FB8610: 72617473 47203232 62796172 48207261 star22 Graybar H

19FB8620: 6573756f 2e645220 6873614e 6c6c6976 ouse Rd.Nashvill

19FB8630: 65 e

Slot 11, Offset 0x79d

---------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB879D: 00180030 20333035 2d353437 32303436 0...503 745-6402

19FB87AD: 3739524f 01303333 00000009 00330005 OR97330.......3.

19FB87BD: 00490041 00620059 2d383436 312d3239 A.I.Y.b.648-92-1

19FB87CD: 42323738 63746f6c 2d746568 6c6c6148 872Blotchet-Hall

19FB87DD: 67655273 6c616e69 20353564 6c6c6948 sReginald55 Hill

19FB87ED: 6c616473 6c422065 726f432e 6c6c6176 sdale Bl.Corvall

19FB87FD: 7369 is

Slot 12, Offset 0x4ca

---------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB84CA: 00180030 20353134 2d353339 38323234 0...415 935-4228

19FB84DA: 34394143 01353935 00000009 00330005 CA94595.......3.

19FB84EA: 0040003b 0058004c 2d323736 332d3137 ;.@.L.X.672-71-3

19FB84FA: 59393432 6d6f6b6f 416f746f 6f6b696b 249YokomotoAkiko

19FB850A: 69532033 7265766c 2e744320 6e6c6157 3 Silver Ct.Waln

19FB851A: 43207475 6b656572 ut Creek

Slot 13, Offset 0x689

---------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB8689: 00180030 20353136 2d363939 35373238 0...615 996-8275

19FB8699: 3834494d 01353031 00000009 00330005 MI48105.......3.

19FB86A9: 0044003f 005e0055 2d323137 312d3534 ?.D.U.^.712-45-1

19FB86B9: 64373638 43206c65 69747361 496f6c6c 867del CastilloI

19FB86C9: 73656e6e 36383232 61724320 6c50206d nnes2286 Cram Pl

19FB86D9: 3823202e 6e6e4136 62724120 726f . #86Ann Arbor

Slot 14, Offset 0x219

---------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB8219: 00180030 20393132 2d373435 32383939 0...219 547-9982

19FB8229: 36344e49 01333034 00000009 00330005 IN46403.......3.

19FB8239: 0041003b 0052004e 2d323237 352d3135 ;.A.N.R.722-51-5

19FB8249: 44343534 61724665 4d65636e 65686369 454DeFranceMiche

19FB8259: 4220336c 69646c61 5020676e 61472e6c l3 Balding Pl.Ga

19FB8269: 7972 ry

Slot 15, Offset 0x31c

---------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB831C: 00180030 20353134 2d333438 31393932 0...415 843-2991

19FB832C: 34394143 00393036 00000009 00330005 CA94609.......3.

19FB833C: 003f003b 00580051 2d343237 392d3830 ;.?.Q.X.724-08-9

19FB834C: 53313339 6e697274 44726567 356b7269 931StringerDirk5

19FB835C: 20303234 656c6554 70617267 76412068 420 Telegraph Av

19FB836C: 6b614f2e 646e616c .Oakland

Slot 16, Offset 0x41f

---------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB841F: 00180030 20353134 2d343533 38323137 0...415 354-7128

19FB842F: 34394143 01323136 00000009 00330005 CA94612.......3.

19FB843F: 0044003d 00590052 2d343237 392d3038 =.D.R.Y.724-80-9

19FB844F: 4d313933 65466361 65687461 65745372 391MacFeatherSte

19FB845F: 736e7261 55203434 6e616c70 74482064 arns44 Upland Ht

19FB846F: 614f2e73 6e616c6b 64 s.Oakland

Slot 17, Offset 0x3ca

---------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB83CA: 00180030 20353134 2d343335 39313239 0...415 534-9219

19FB83DA: 34394143 01393036 00000009 00330005 CA94609.......3.

19FB83EA: 003e0039 0055004e 2d363537 372d3033 9.>.N.U.756-30-7

19FB83FA: 4b313933 65737261 76694c6e 37356169 391KarsenLivia57

19FB840A: 4d203032 6c754163 53207965 614f2e74 20 McAuley St.Oa

19FB841A: 6e616c6b 64 kland

Slot 18, Offset 0x26b

---------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB826B: 00180030 20313033 2d363439 33353838 0...301 946-8853

19FB827B: 3032444d 01333538 00000009 00330005 MD20853.......3.

19FB828B: 0041003b 005c0053 2d373038 362d3139 ;.A.S.\.807-91-6

19FB829B: 50343536 65746e61 5379656c 69766c79 654PanteleySylvi

19FB82AB: 35393161 72412036 676e696c 206e6f74 a1956 Arlington

19FB82BB: 522e6c50 766b636f 656c6c69 Pl.Rockville

Slot 19, Offset 0x6e7

---------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB86E7: 00180030 20353134 2d363338 38323137 0...415 836-7128

19FB86F7: 34394143 01313033 00000009 00330005 CA94301.......3.

19FB8707: 003f0039 0057004e 2d363438 372d3239 9.?.N.W.846-92-7

19FB8717: 48363831 65746e75 65685372 336c7972 186HunterSheryl3

19FB8727: 20303134 6e6f6c42 53206564 61502e74 410 Blonde St.Pa

19FB8737: 41206f6c 6f746c lo Alto

Slot 20, Offset 0x2c7

---------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB82C7: 00180030 20373037 2d383434 32383934 0...707 448-4982

19FB82D7: 35394143 00383836 00000009 00330005 CA95688.......3.

19FB82E7: 0042003b 0055004c 2d333938 312d3237 ;.B.L.U.893-72-1

19FB82F7: 4d383531 64614263 486e6564 68746165 158McBaddenHeath

19FB8307: 30337265 75502031 6d616e74 61636156 er301 PutnamVaca

19FB8317: 6c6c6976 65 ville

Slot 21, Offset 0x1c0

---------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB81C0: 00180030 20313038 2d363238 32353730 0...801 826-0752

19FB81D0: 34385455 01323531 00000009 00330005 UT84152.......3.

19FB81E0: 003d0039 0059004b 2d393938 322d3634 9.=.K.Y.899-46-2

19FB81F0: 52353330 65676e69 6e6e4172 20373665 035RingerAnne67

19FB8200: 65766553 2068746e 532e7641 20746c61 Seventh Av.Salt

19FB8210: 656b614c 74694320 79 Lake City

Slot 22, Offset 0x165

---------------------

Record Type = PRIMARY_RECORD

Record Attributes = NULL_BITMAP VARIABLE_COLUMNS

19FB8165: 00180030 20313038 2d363238 32353730 0...801 826-0752

19FB8175: 34385455 01323531 00000009 00330005 UT84152.......3.

19FB8185: 003f0039 005b004d 2d383939 332d3237 9.?.M.[.998-72-3

19FB8195: 52373635 65676e69 626c4172 36747265 567RingerAlbert6

19FB81A5: 65532037 746e6576 76412068 6c61532e 7 Seventh Av.Sal

19FB81B5: 614c2074 4320656b 797469 t Lake City

OFFSET TABLE:

-------------

Row - Offset

22 (0x16) - 357 (0x165)

21 (0x15) - 448 (0x1c0)

20 (0x14) - 711 (0x2c7)

19 (0x13) - 1767 (0x6e7)

18 (0x12) - 619 (0x26b)

17 (0x11) - 970 (0x3ca)

16 (0x10) - 1055 (0x41f)

15 (0xf) - 796 (0x31c)

14 (0xe) - 537 (0x219)

13 (0xd) - 1673 (0x689)

12 (0xc) - 1226 (0x4ca)

11 (0xb) - 1949 (0x79d)

10 (0xa) - 1488 (0x5d0)

9 (0x9) - 1854 (0x73e)

8 (0x8) - 1407 (0x57f)

7 (0x7) - 1144 (0x478)

6 (0x6) - 96 (0x60)

5 (0x5) - 2047 (0x7ff)

4 (0x4) - 884 (0x374)

3 (0x3) - 1314 (0x522)

2 (0x2) - 272 (0x110)

1 (0x1) - 184 (0xb8)

0 (0x0) - 1585 (0x631)

DBCC-Ausführung abgeschlossen. Falls DBCC Fehlermeldungen ausgegeben hat, wenden Sie sich an den Systemadministrator.

Have fun fumbling those bits and bytes together.

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