Any ideas? Thanks in advance!
What is the error you get that causes it to go suspect?
Try ALTER DATABASE <dbname> SET ONLINE to see the error.
|||Part of attaching a database from an older version of SQL on a newer instance involves making any required alterations to the database structure needed by the new version.
If the database was suspect on SQL 2000 before it was detached, that may well prevent those alterations from happening.
Why are you trying to attach this database to a newer version of SQL instead of resolving the suspect status before moving it?
|||The mdf and ldf files were recovered from a failing RAID array before the whole thing died. So there is not actually a way to attempt a repair on the original system.|||Kevin,
Will attaching these data files to a SQL Server 2000 make difference , could be a different hardware
Thanks
Vishal|||I agree, I would try and get the database back to a SQL2K instance, fix your problems there and then move to 2005.|||
Vishal Gandhi wrote:
Kevin,
Will attaching these data files to a SQL Server 2000 make difference , could be a different hardwareThanks
Vishal
Yes, because the SQL 2000 instance will not need to perform the upgrade step prior to bringing the database online.
|||Hi,If you used sp_resetstatus to make the db status to emergency mode, then you should restore the db using the latest backup available.
No comments:
Post a Comment