Home Dashboard Directory Help
Search

DBCC PAGE incorrect output with filtered indexes by Luciano Moreira


Status: 

Closed


10
0
Sign in
to vote
Type: Bug
ID: 776144
Opened: 1/9/2013 9:48:55 AM
Access Restriction: Public
1
Workaround(s)
view
3
User(s) can reproduce this bug

Description

When I use DBCC PAGE to check a page of an index with format 3, it shows as expected (on grid, with level, ChildPageId, key, row size, …). But when I create a non-clustered index with a filter, the same DBCC PAGE doesn’t format the output anymore.

This was verified using Microsoft SQL Server 2012 - 11.0.2218.0 (X64). With SQL Server 2008 and 2008 R2 I couldn't reproduce the problem.

I know DBCC PAGE is undocumented, but want to make sure Microsoft knows about it.
Details
Sign in to post a comment.
Posted by Microsoft on 7/15/2013 at 7:20 AM
Given DBCC Page is not intended for public usage and we can only keep the tool updated as engineering resources allow. We are now aware of this issue and will see if this can be fixed in a future release.
Posted by Microsoft on 3/29/2013 at 10:51 AM
Hi,
Thank you for your feedback and bringing this behaviour to our attention. At the moment, there are no plans to enhance this command as it is undocumented. However we will keep this in mind in the future.
Posted by Kendra Little on 2/22/2013 at 10:31 PM
I just hit this issue. Took me a while to narrow it down to the filtered index, but it's the exact same thing.

When the issue occurs, there's a stack dump written to the SQL Server log (Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION)
Sign in to post a workaround.
Posted by Kendra Little on 2/22/2013 at 11:09 PM
This is obviously only a suitable workaround for a demo, but you can disable or drop the filtered index. You will then be able to see DBCC PAGE output with dump style 3 for all other indexes on the table.

(In other words, the issue isn't permanent and you can just disable the single NC.)