September 19, 2006 at 2:30 pm
I'm working on an index rebuild routine and I'm using the new sys.dm_db_index_physical_stats function to get index info. Any ideas on the following? The DB that I think is causing the problem passes DBCC CHECKDB.
When I run this...
SELECT
*
FROM
sys.dm_db_index_physical_stats (NULL, NULL, NULL, NULL, 'detailed')
I get this error...
Location: qxcntxt.cpp:954
Expression: !"No exceptions should be raised by this code"
SPID: 145
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.
September 22, 2006 at 8:00 am
This was removed by the editor as SPAM
September 26, 2006 at 1:36 pm
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.
March 27, 2007 at 1:12 pm
just got this today one one server
i'm running the system view with the detailed option for two other databases on this server and others and it works. i added another step to the job to gather frag data for a third database and got this.
June 4, 2007 at 4:08 am
Is this problem solved in sp2?, I have the same symptom in my SQL2005 sp1.
Regards, Ronnie Johansson
June 4, 2007 at 7:41 am
Yes, I just ran it on our test server that has SP2 and it works fine. We are planning to move to SP2 for production but just haven't got there yet.
June 4, 2007 at 9:18 am
anyone get the KB error when upgrading to SP1? I think there is a link between this error and the KB upgrade error where you ignore the error because the build # on SQL matches the SP
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply