July 1, 2008 at 3:26 am
Hi All,
I have migrated some of the databases from SQL 2000 to SQL 2005. They all are running fine, but some tables having the issue with consistency error. So what I did I create the same table structure for the tables having the consistency error, transfer the data from old table to newly created table and delete the old table. It was working fine for every database and after that DBCC CheckDB was running fine for that database. But for one DB I am not able to do that as this table having one column with Image DataType. Table size is more than 32 GB and when I am transferring it is showing me the problem with Log File Full, when I added one more Log file to it, it again get failed with the error insufficient physical memory. Could anyone of you suggest any alternative or how can fix this issue in the same approach.
Thanks in Advance.
Regards,
Shekhar
July 2, 2008 at 6:28 am
Shekhar, this really should have gone under data corruption as you'll likely get quicker responses as to what may have led to the corruption. Do you have a good backup of the database in question? If SQL2000 is still running, can you check the consistency of that database there and if it's good, re-migrate? As far as the log filling up is concerned, are you backing up the log with any regularity? If you do that, you really shouldn't need to add any additional log files. Maybe schedule a backup of the log every 15-30 minutes while your process is running. With respect to insufficient memory, how much do you have and how much is allocated to SQL server?
-- You can't be late until you show up.
July 2, 2008 at 7:02 am
Can you post the results of DBCC CHECKDB (database name) WITH ALL_ERRORMSGS
Maninder
www.dbanation.com
July 2, 2008 at 7:47 am
Run DBCC UPDATEUSAGE.
BOL has following remarks:
In earlier versions of SQL Server, the values for the per-table and per-index row count and page counts can become incorrect. Under certain circumstances, one or more of these values might even become negative. DBCC CHECKDB does not detect this issue. This is not a corruption of any data stored in the database, and the situation is typically addressed by running the DBCC UPDATEUSAGE command.
In SQL Server 2005, DBCC CHECKDB has been enhanced to detect when any one of these counts becomes negative. When detected, the DBCC CHECKDB output contains a warning and a recommendation to run DBCC UPDATEUSAGE to address the issue. Although it may appear as if upgrading the database to SQL Server 2005 has caused this issue, it was, in fact, present before the upgrade procedure.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply