November 18, 2009 at 6:56 pm
When I try to restore msdb database of SQL server 2008 using a backup copy of SQL 2000 msdb database I can getting following error.
Msg 3154, Level 16, State 4, Line 5
The backup set holds a backup of a database other than the existing 'msdb' database.
Msg 3013, Level 16, State 1, Line 5
RESTORE DATABASE is terminating abnormally.
Is it because of the version incompatibility of sql server or any other reason.
November 18, 2009 at 8:04 pm
I expect that this error is because you are trying to restore MSDB from an earlier version of SQL Server.
If you did manage to restore it, I would expect that you would start to experience significant issues with the operation of any part of SQL Server that uses MSDB since there are structural and functional changes made between versions of SQL Server.
November 18, 2009 at 9:22 pm
I have to agree with happycat59. There is not ANY circumstance where I would restore an msdb from an previous version, that is just asking for major issues.
CEWII
November 19, 2009 at 8:57 am
agree with the above and to add you can try this
restore it as files to the sql 2008 server but don't attach it. detach the current MSDB and attach the files you just restored.
My guess is you never backed it up and something happened and now you need the jobs from there. I don't think this method will work in production but you should be able to transfer the jobs out.
another method is to create a dummy sql 2000 server. detach the msdb and restore the one in question. attach it and transfer the jobs using SSIS. you might have to create dummy databases on the server you create just for placeholders
November 19, 2009 at 10:48 am
ajith.ranjan (11/18/2009)
When I try to restore msdb database of SQL server 2008 using a backup copy of SQL 2000 msdb database I can getting following error.Msg 3154, Level 16, State 4, Line 5
The backup set holds a backup of a database other than the existing 'msdb' database.
Msg 3013, Level 16, State 1, Line 5
RESTORE DATABASE is terminating abnormally.
Is it because of the version incompatibility of sql server or any other reason.
It's definitely because of the version incompatibility. See this in BOL: http://msdn.microsoft.com/en-us/library/ms190436(SQL.90).aspx
Greg
November 20, 2009 at 2:44 am
If your sql2000 instance is still available, just script out all jobs, alerts, user created objects, ....
and then run that script on your sql2008 instance.
Keep in mind NOT to implement any microsoft msdb objects !! (because that will get you into a very confusing situation, nolonger knowing which version that table/view/proc/... belongs to)
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply