April 28, 2007 at 6:57 pm
April 29, 2007 at 9:07 am
Very intersting questions. I'd try to experiment and with dbcc page or even add data to a new table in 2k chunks and see how many pages are used.
My suspicion is the pages are 8k and that only the compatability level affects keywords, not the physical structure.
I would never change the master, tempdb, or msdb comp levels.
April 29, 2007 at 10:19 am
Steve,
thanks for your reply, i tried using DBCC PAGE & didn't see the PAGE size in the result or i might be looking at the wrong place. i agree to you about comptlevel but i am not sure about how SQL Server 2000 Database Engine reacts when it sees SQL server 6.5 USER database. thank you
May 1, 2007 at 7:30 am
Look at "Connecting Early Version Clients to SQL Server 2000" in BOL.
As for storage the system enforces 8K on even 6.5 compatibility mode databases and you cannot restore them to a 6.5 server.
As for storage it is 8192 per page. However, there are some control bits on a page so the free space will never be more than 8188. The field you want to look for is m_freeData in the DBCC PAGE output. Also make sure you turn on trace flag 3604 to see the output
Ex.
DBCC TRACEON (3604)
GO
DBCC PAGE (Risk_Assessment,1,1,3)
GO
Hope this helps.
May 1, 2007 at 8:42 am
I was not sure about what this "m_freeData" after doing DBCC PAGE, but you explained well.
Thanks for your feedback,
Thanks
Jay
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply