I'm setting up a routine to do some reindexing. To get the info I need I'm trying to use the new function. The DB I think is causing the problem does pass DBCC CHECKDB. I'm not sure why I'm getting this but can not find anyone else that is getting this same error.
When I run this....
SELECT *
FROM sys.dm_db_index_physical_stats (NULL, NULL, NULL, NULL, 'detailed')
I get this....
Location: qxcntxt.cpp:954
Expression: !"No exceptions should be raised by this code"
SPID: 236
Process ID: 1060
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
If I run only for the DB I think is causing the problem I get this...
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Well, since this created a dump I guess I'll be contacting product support services. Just thought I'd check online first.|||I think when system code claims: Expression: !"No exceptions should be raised by this code" that would be the best thing...
Can you post here and tell us what the issue was?
|||Unfortunately, this is an internal server error due to unknown cause, and unlikely to get resolved with standard mini dump only.|||This is was found to be a bug in SP1 of SQL 2005. The work around is to use limited instead of detailed. I don't get all the data I was wanting to collect but this will work ok until SP2 is released with the fix. We had three DBs on our 2005 server that would generate this error.
|||Thanks for letting us know. It is always interesting when someone else is having a similar problem if a resolution (or lack thereof :) is noted!
No comments:
Post a Comment