In the previous post, I shared demonstration on how to corrupt your table in SQL Server.

Generally, SQL DBAs are executing DBCC CHECKDB for checking and finding damaged table or data. But if your database size is very enormous and the result of DBCC CHECKDB is also huge, it is tough to find out suspected tables.

Then, what is the solution?
The solution is to check the suspect pages and find the table name using object id.

Check the below demonstration where I used one sample corrupted table, and more you can test the yesterday’s post for tbl_bad.

Check the suspect_pages:

SELECT * FROM [msdb].[dbo].[suspect_pages]

Result:

database_id file_id     page_id              
----------- ----------- -------------------- 
10          1           312

Execute below DBCC PAGE:
Database id =10
File no=1
Page id=312
Print option=0

DBCC TRACEON (3604);
DBCC PAGE (10, 1, 312, 0);
DBCC TRACEOFF (3604);
GO

Result:

PAGE HEADER:

Page @0x000000F815DC4000

m_pageId = (1:312)                  m_headerVersion = 1                 m_type = 1
m_typeFlagBits = 0x0                m_level = 0                         m_flagBits = 0x8200
m_objId (AllocUnitId.idObj) = 138   m_indexId (AllocUnitId.idInd) = 256 
Metadata: AllocUnitId = 72057594046971904                                
Metadata: PartitionId = 72057594041335808                                Metadata: IndexId = 1
Metadata: ObjectId = 565577053      m_prevPage = (0:0)                  m_nextPage = (0:0)
pminlen = 8                         m_slotCnt = 5                       m_freeCnt = 7976
m_freeData = 206                    m_reservedCnt = 0                   m_lsn = (34:228:3)
m_xactReserved = 0                  m_xdesId = (0:0)                    m_ghostRecCnt = 0
m_tornBits = -411585792             DB Frag ID = 1                      

Allocation Status

GAM (1:2) = ALLOCATED               SGAM (1:3) = NOT ALLOCATED          PFS (1:1) = 0x40 ALLOCATED   0_PCT_FULL
DIFF (1:6) = CHANGED                ML (1:7) = NOT MIN_LOGGED

Find Metadata: ObjectId and get the object name:

SELECT OBJECT_NAME (565577053);

In the previous series of the articles, I shared internal structure of the Data File and Data Page of the SQL Server.

In this article, I am going to share small practical demonstration on how to find Data Page information of a particular table of the SQL Server.

First, Create a table with sample data:

CREATE TABLE dbo.tbl_TestDataPage 
(
	DataPageID INT PRIMARY KEY
	,Name VARCHAR(30)	
)
GO

INSERT dbo.tbl_TestDataPage 
VALUES 
(1,'Anvesh'),(2,'Neevan')
,(3,'Martin'),(4,'Jeeny')
,(5,'Maria'),(6,'Roy')
GO

Execute DBCC IND to check allocated pages of a Table:
You should put your Database_Name. -1 means display all type of pages.

DBCC IND('Database_Name', 'tbl_TestDataPage', -1)

The Result:
PageFID is a file number and PagePID is a page number. You can use these numbers for further tracing.

Execute DBCC PAGE to find more information about the allocated page:

Syntax:

DBCC PAGE ( {'database_name' or DB_ID}, file_number, page_number [, printopt={0|1|2|3} ])

Print option:
0 - print the page header
1 - page header plus per-row hex dumps and slot array 
2 - page header plus whole page hex dump
3 - detailed per-row interpretation

DBCC TRACEON(3604) -- This trace flag enable result in table format. 
GO
DBCC PAGE('database_name',1,274,3)
GO

The Result: