Monday, February 20, 2012

MSDB database restore

I am trying to restore the msdb to another server. When I do, I get the
following message:
V-79-57344-33938 -
An error occurred on a query to database msdb.
V-79-57344-33938 - The backup of the system database on device
msdb_00__60f69b04_bfad_4b17_a284_4047d59b9e28_ cannot be restored because it
was created by a different version of the server (134218407) than this server
(134218262).
I understand what the message is saying but how do I find out what SPs and
hotfixes I need to install in order to get the target server to the correct
version? Is there a table or a document that will tell me what needs to be
installed on the target server?
ThanksYou can restore to a new version so as long as your up to the latest version
you should be OK. This generally isn't an issue when moving between service
pack and hot fixes so my guess is that you are trying to restore to a
pre-released version of SQL Server. Looking at the SELECT @.@.version output
should help determine what you are running.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Paul Oren" <PaulOren@.discussions.microsoft.com> wrote in message
news:0C01112B-319F-4B14-8A49-F1EBAB72BF6A@.microsoft.com...
>I am trying to restore the msdb to another server. When I do, I get the
> following message:
> V-79-57344-33938 -
> An error occurred on a query to database msdb.
> V-79-57344-33938 - The backup of the system database on device
> msdb_00__60f69b04_bfad_4b17_a284_4047d59b9e28_ cannot be restored because
> it
> was created by a different version of the server (134218407) than this
> server
> (134218262).
> I understand what the message is saying but how do I find out what SPs and
> hotfixes I need to install in order to get the target server to the
> correct
> version? Is there a table or a document that will tell me what needs to
> be
> installed on the target server?
> Thanks
>|||The backup I am restoring from is on tape so I can not get it restored in
order to run the the select statement. All my databases were loaded from MS
CDs so a pre-released version of SQL server should not be an issue.
"Roger Wolter[MSFT]" wrote:
> You can restore to a new version so as long as your up to the latest version
> you should be OK. This generally isn't an issue when moving between service
> pack and hot fixes so my guess is that you are trying to restore to a
> pre-released version of SQL Server. Looking at the SELECT @.@.version output
> should help determine what you are running.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Paul Oren" <PaulOren@.discussions.microsoft.com> wrote in message
> news:0C01112B-319F-4B14-8A49-F1EBAB72BF6A@.microsoft.com...
> >I am trying to restore the msdb to another server. When I do, I get the
> > following message:
> >
> > V-79-57344-33938 -
> > An error occurred on a query to database msdb.
> > V-79-57344-33938 - The backup of the system database on device
> > msdb_00__60f69b04_bfad_4b17_a284_4047d59b9e28_ cannot be restored because
> > it
> > was created by a different version of the server (134218407) than this
> > server
> > (134218262).
> >
> > I understand what the message is saying but how do I find out what SPs and
> > hotfixes I need to install in order to get the target server to the
> > correct
> > version? Is there a table or a document that will tell me what needs to
> > be
> > installed on the target server?
> >
> > Thanks
> >
>|||So apply SQL 2005 SP2 and you will assuredly be more recent that the tape
backup.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Paul Oren" <PaulOren@.discussions.microsoft.com> wrote in message
news:339C5DF0-6C3A-4FDA-B0AF-F65D59CB7349@.microsoft.com...
> The backup I am restoring from is on tape so I can not get it restored in
> order to run the the select statement. All my databases were loaded from
> MS
> CDs so a pre-released version of SQL server should not be an issue.
> "Roger Wolter[MSFT]" wrote:
>> You can restore to a new version so as long as your up to the latest
>> version
>> you should be OK. This generally isn't an issue when moving between
>> service
>> pack and hot fixes so my guess is that you are trying to restore to a
>> pre-released version of SQL Server. Looking at the SELECT @.@.version
>> output
>> should help determine what you are running.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Paul Oren" <PaulOren@.discussions.microsoft.com> wrote in message
>> news:0C01112B-319F-4B14-8A49-F1EBAB72BF6A@.microsoft.com...
>> >I am trying to restore the msdb to another server. When I do, I get the
>> > following message:
>> >
>> > V-79-57344-33938 -
>> > An error occurred on a query to database msdb.
>> > V-79-57344-33938 - The backup of the system database on device
>> > msdb_00__60f69b04_bfad_4b17_a284_4047d59b9e28_ cannot be restored
>> > because
>> > it
>> > was created by a different version of the server (134218407) than this
>> > server
>> > (134218262).
>> >
>> > I understand what the message is saying but how do I find out what SPs
>> > and
>> > hotfixes I need to install in order to get the target server to the
>> > correct
>> > version? Is there a table or a document that will tell me what needs
>> > to
>> > be
>> > installed on the target server?
>> >
>> > Thanks
>> >|||We are running SQL 2000 not SQL 2005.
"Roger Wolter[MSFT]" wrote:
> So apply SQL 2005 SP2 and you will assuredly be more recent that the tape
> backup.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Paul Oren" <PaulOren@.discussions.microsoft.com> wrote in message
> news:339C5DF0-6C3A-4FDA-B0AF-F65D59CB7349@.microsoft.com...
> > The backup I am restoring from is on tape so I can not get it restored in
> > order to run the the select statement. All my databases were loaded from
> > MS
> > CDs so a pre-released version of SQL server should not be an issue.
> >
> > "Roger Wolter[MSFT]" wrote:
> >
> >> You can restore to a new version so as long as your up to the latest
> >> version
> >> you should be OK. This generally isn't an issue when moving between
> >> service
> >> pack and hot fixes so my guess is that you are trying to restore to a
> >> pre-released version of SQL Server. Looking at the SELECT @.@.version
> >> output
> >> should help determine what you are running.
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> Use of included script samples are subject to the terms specified at
> >> http://www.microsoft.com/info/cpyright.htm
> >>
> >> "Paul Oren" <PaulOren@.discussions.microsoft.com> wrote in message
> >> news:0C01112B-319F-4B14-8A49-F1EBAB72BF6A@.microsoft.com...
> >> >I am trying to restore the msdb to another server. When I do, I get the
> >> > following message:
> >> >
> >> > V-79-57344-33938 -
> >> > An error occurred on a query to database msdb.
> >> > V-79-57344-33938 - The backup of the system database on device
> >> > msdb_00__60f69b04_bfad_4b17_a284_4047d59b9e28_ cannot be restored
> >> > because
> >> > it
> >> > was created by a different version of the server (134218407) than this
> >> > server
> >> > (134218262).
> >> >
> >> > I understand what the message is saying but how do I find out what SPs
> >> > and
> >> > hotfixes I need to install in order to get the target server to the
> >> > correct
> >> > version? Is there a table or a document that will tell me what needs
> >> > to
> >> > be
> >> > installed on the target server?
> >> >
> >> > Thanks
> >> >
> >>
>

No comments:

Post a Comment