CaptainGiblets
asked on
Getting a database to restore - error 3241
i have an important database that was hosted from a server in a datacenter, we were having problems with the machine so sql on it was backup up and it was reformatted. When we got it back online it appears something is wrong with the sql backup and it now wont restore. The only backup we have that works is over 6 days old, is there anyway to get it to work?
I read somewhere that it may be to do with the transaction logs, and you can get it to work by restoring it to the MSDE 2000 rather than sql 2000 server. However i cant seem to manage to connect to the MSDE.
Any help fixing this would be appreciated.
I read somewhere that it may be to do with the transaction logs, and you can get it to work by restoring it to the MSDE 2000 rather than sql 2000 server. However i cant seem to manage to connect to the MSDE.
Any help fixing this would be appreciated.
ASKER
it was backed up using sql server 2000 sp 4, and we restored it using sql server 2000 sp4 still no luck.
May be that backup is not taken correctly, try to run RESTORE VERIFYONLY to see whether it is consistent
ASKER
i cant seem to find the option to restore verifyonly, where abouts is it.
http://www.mssqltips.com/tip.asp?tip=1093 should explain
ASKER
iv etried restoring it using query analyzer and i get the message
Collation ID 49o is invalid.
Collation ID 49o is invalid.
mmm looks like backup is corrupt.....
ASKER
if i can access the old files using a file restorer, is there any way to get the data by finding the old sql database in the installation directory.
mmm that a question for experts in windows i think
ASKER
i know how to get the files back etc, its just opening them in sql once ive got them im not sure how 2 do.
just restore like mentioned earlier
ASKER
its an mdf file, not a bak file its the whole database stored in the binn folder that i managed 2 get hold of
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
sorry but how do i do this
4. Now your database will be marked suspect 5. Update the sysdatabases to update to Emergency mode. This will not use LOG files in start up
Sp_configure "allow updates", 1
go
Reconfigure with override
GO
Update sysdatabases set status = 32768 where name = "BadDbName"
go
Sp_configure "allow updates", 0
go
Reconfigure with override
GO
4. Now your database will be marked suspect 5. Update the sysdatabases to update to Emergency mode. This will not use LOG files in start up
Sp_configure "allow updates", 1
go
Reconfigure with override
GO
Update sysdatabases set status = 32768 where name = "BadDbName"
go
Sp_configure "allow updates", 0
go
Reconfigure with override
GO
ASKER
i think i will need a hand doing all part 4 onward, sorry but im not really an expert in any of this stuff.
paste it into sql query anazlyer
ASKER
ive followed all them steps, and it said it did it ok, but when i go into the database its called lom2_charddb (DBO Use Only) and all the tables etc are there, but they are all empty. however the database is still 120mb
ASKER
never mind, just rebooted and it came straight back up, thanks a lot for your help.
pheww glad all sorted
http://support.microsoft.com/kb/297104