Re: How do Ad hoc updates to system catalogs at SQL 2005

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Krisnamourt,

I suspect then that your data corruption happened on SQL Server 2000. I
suggest that you fix it there, before trying to upgrade to SQL Server 2005.
You should only try to upgrade databases that are already in a consistent
state.

Once a database is inconsistent, it is certainly suspicious to rely upon the
accuracy of the data. It may still be mostly OK, or it may be seriously
damaged. Once you are sure that you are starting with a consistent
database, then you can restore that database to SQL Server 2005 and do the
upgrade.

If I am failing to understand, I apologize, but there are no tricks in 2005
to fix this problem.

Tibor's advice is still good.

RLF

"Krisnamourt via SQLMonster.com" <u21487@uwe> wrote in message
news:78c17ee547646@xxxxxx
Yes. the problem is exactly this.

DBCC CHECKDB was found integrity problem with this table.

I don't try with REPAIR_ALLOW_DATA_LOSS . I will...but I need this
procedure
form to do this operation, I mean, backup from SQL 2000 and restore at
SQL2005 to make upgrade "side by side".

The other way could be change from sql2000.

I thought that exist any form to do this at SQL 2005. Of any form, I
appreciate your help.

Russell Fields wrote:
Krisnamourt,

In 2005 you do not update the system catalogs directly. And even if you
did, I don't think that deleting a row in sysindexes would actually delete
the table.

Perhaps your database has integrity problems. Have you run DBCC
CHECKDB(dbname)? I would suggest doing so.

RLF

Please,
somy friend have this answer so clear, I mean, any article or guide to
[quoted text clipped - 25 lines]

Kris.

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-setup/200709/1



.

Quantcast