January 12, 2013 at 9:54 am
After I export a SQL 2000 database on a Windows 2003 server and then import it into a SQL 2008R2 database on Windows 2008R2 server I run the following command on the imported SQL 2008R2 database.
DBCC CHECKDB(N'Membership_GL') WITH NO_INFOMSGS, ALL_ERRORMSGS
I get the following error:
Msg 2508, Level 16, State 3, Line 1
The In-row data RSVD page count for object "Flexible_Budget", index ID 0, partition ID 5517826457600, alloc unit ID 5517826457600 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'Flexible_Budget' (object ID 84195350).
Msg 2508, Level 16, State 3, Line 1
The In-row data RSVD page count for object "Statement_YTD_Template", index ID 0, partition ID 11809304870912, alloc unit ID 11809304870912 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'Statement_YTD_Template' (object ID 180195692).
CHECKDB found 0 allocation errors and 2 consistency errors in database 'Membership_GL'.
However, when I run the same "DBCC CHECKDB(N'Membership_GL') WITH NO_INFOMSGS, ALL_ERRORMSGS" command on the SQL Server 2000 database it show no errors. It just shows "The command(s) completed successfully."
The current compatibility level is 80 on the SQL Server 2008R2 database.
Is this something that I should be concerned about?
Thanks
Howard
January 12, 2013 at 9:55 am
Just do what the messages tell you to. In SQL 2000 incorrect page usage stats was acceptable, in 2005 and above it's considered an error.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 12, 2013 at 9:59 am
Mr. Shaw:
Thank you for the quick response.
Is there any reason for concern that this error shows up in 2 of the SQL Server 2000 databases?
Howard
January 12, 2013 at 10:03 am
As I said, in SQL 2000 incorrect page usage stats was acceptable, in 2005 and above it's considered an error.
Since you're upgrading from SQL 2000, you have gone from a scenario where page usage inaccuracies were fine (and even common in some cases) to a scenario where they're considered an error and are reported by CheckDB. Just run the command that the errors say.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 12, 2013 at 10:14 am
Mr. Shaw:
Thank you for your help in this matter.
Howard
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply