May 5, 2008 at 2:56 pm
Attribute (object_id=) of row (object_id=,column_id=1) in sys.columns does not have a matching row (object_id=) in sys.objects
May 5, 2008 at 3:00 pm
Well, not too much info to go on, or the normal forum etiquette of please/thank-you but I'll help you anyway.
This is a metadata corruption returned by CHECKDB or CHECKCATALOG. The most likely cause is that someone altered the system tables manually on SQL 2000 and then you upgraded the database to 2005 and CHECKDB found the problem (it include CHECKCATALOG in 2005).
If you just upgraded the database, go back to 2000, fix the problem and then upgrade again.
If you're on 2005, you can't fix this easily.
Which is it?
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
May 5, 2008 at 3:07 pm
I lost my connection trying to post the problem. Thanks..
Thanks another time!
May 5, 2008 at 3:11 pm
I'm using 2005...
Thanks
May 5, 2008 at 3:16 pm
I know you're using 2005 - that's where the error came from. Can you read my post and answer the question about upgrading/altering system tables?
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
May 5, 2008 at 3:22 pm
This is a metadata corruption returned by CHECKDB or CHECKCATALOG. The most likely cause is that someone altered the system tables manually on SQL 2000 and then you upgraded the database to 2005 and CHECKDB found the problem (it include CHECKCATALOG in 2005).
--------
Yes, It looks like my conditions. I do not Know if someone altered the system table but it's possible.
--------------------------------------------------------
If you just upgraded the database, go back to 2000, fix the problem and then upgrade again.
---------
I can't return to 2000
-----------------------------------------------------------------------
If you're on 2005, you can't fix this easily.
I know. Do you have any solution?
------------------------------------
Thanks Paul
May 6, 2008 at 1:49 pm
This is not supported in any way but you can use the Dedicated Admin Connection to get access to the system tables. I won't explain any more how to do it but that should give you enough info to get started. Be careful and take a backup before doing anything.
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
May 7, 2008 at 9:03 am
Thanks! You are right.
I'm thinking in something like this. Any other ideas please? Did you tested before?
Is this error important for SQL server? What do you think?
1. Run
ALTER DATABASE NGPROD
SET SINGLE_USER
WITH ROLLBACK IMMEDIATE
2. Run
sp_configure 'allow updates', 1;
RECONFIGURE WITH OVERRIDE
GO
3. Add -m to SQL service.
4. Restart SQL Server service
5. Connect a New Query Interface Window using a DAC.
6. DELETE FROM syscolumns….
7. Remove –m parameter
8- Restart to SQL
Other way, recreate entire database copying all table one by one to other database, After that recreate other objects (restrictions, sp, functions etc)
Thank for your useful opinion
May 7, 2008 at 1:26 pm
You're on the right path - as I said before I'm not going to give detailed info on how to do this as its unsupported and I haven't tested it thoroughly.
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply