Showing posts with label occurred. Show all posts
Showing posts with label occurred. Show all posts

Saturday, February 25, 2012

msdb restore?

A terrible event has occurred. Our SQL Server 2000 database was attacked an
d
the master, msdb, etc was deleted. We used a utility to undelete those file
s
and have saved them. We had to reinstall Windows and SQL Server, but am
unable to replace the msdb. We have no backup so that isn't an option. Is
there a way to restore our DTS packages from the original msdb? Thanks.Did you try attaching it with a different name?
http://www.aspfaq.com/
(Reverse address to reply.)
"Phill" <Phill@.discussions.microsoft.com> wrote in message
news:104A0726-0C71-4A29-B3A8-DF21C9158F38@.microsoft.com...
> A terrible event has occurred. Our SQL Server 2000 database was attacked
and
> the master, msdb, etc was deleted. We used a utility to undelete those
files
> and have saved them. We had to reinstall Windows and SQL Server, but am
> unable to replace the msdb. We have no backup so that isn't an option.
Is
> there a way to restore our DTS packages from the original msdb? Thanks.|||I tried but I get the following error:
I/O error 38(Reached the end of the file.) detected during read at offset
0000000000000000 in file 'C:\Mymsdbdata.mdf'.
Connection Broken
"Aaron [SQL Server MVP]" wrote:

> Did you try attaching it with a different name?
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Phill" <Phill@.discussions.microsoft.com> wrote in message
> news:104A0726-0C71-4A29-B3A8-DF21C9158F38@.microsoft.com...
> and
> files
> Is
>
>|||> I tried but I get the following error:
What *exactly* did you try? I see that you renamed the MDF file, I meant to
attach as a different database name.
If the file is corrupt, and you may be S.O.L. (this is what backups are
for).
http://www.aspfaq.com/
(Reverse address to reply.)
"Phill" <Phill@.discussions.microsoft.com> wrote in message
news:F9540632-EF19-41D8-A3FD-572722B13190@.microsoft.com...[vbcol=seagreen]
> I/O error 38(Reached the end of the file.) detected during read at offset
> 0000000000000000 in file 'C:\Mymsdbdata.mdf'.
> Connection Broken
> "Aaron [SQL Server MVP]" wrote:
>
attacked[vbcol=seagreen]
those[vbcol=seagreen]
am[vbcol=seagreen]
option.[vbcol=seagreen]
Thanks.[vbcol=seagreen]|||I copied the mdf and ldf files to Mymsdbdata.mdf and Mymsdblog.ldf. The I
ran the following in Query Analyser:
exec sp_attach_db @.dbname =
N'Mymsdb',@.filename1=N'C:\Mymsdbdata.mdf',@.filename2=N'C:\Mymsdblog.ldf'
"Aaron [SQL Server MVP]" wrote:

> What *exactly* did you try? I see that you renamed the MDF file, I meant
to
> attach as a different database name.
> If the file is corrupt, and you may be S.O.L. (this is what backups are
> for).
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Phill" <Phill@.discussions.microsoft.com> wrote in message
> news:F9540632-EF19-41D8-A3FD-572722B13190@.microsoft.com...
> attacked
> those
> am
> option.
> Thanks.
>
>|||The data file is 0k, but the log file has data in it. I'm hoping that since
msdb was never backed up that it can be rebuilt using the log file. Can thi
s
be done?
"Phill" wrote:
[vbcol=seagreen]
> I copied the mdf and ldf files to Mymsdbdata.mdf and Mymsdblog.ldf. The I
> ran the following in Query Analyser:
> exec sp_attach_db @.dbname =
> N'Mymsdb',@.filename1=N'C:\Mymsdbdata.mdf',@.filename2=N'C:\Mymsdblog.ldf'
> "Aaron [SQL Server MVP]" wrote:
>|||I think you may have to open a case with PSS, or cut your losses. In the
future: backup is a very important word.
http://www.aspfaq.com/
(Reverse address to reply.)
"Phill" <Phill@.discussions.microsoft.com> wrote in message
news:6B1824AD-016E-41CE-A851-889622057227@.microsoft.com...[vbcol=seagreen]
> I copied the mdf and ldf files to Mymsdbdata.mdf and Mymsdblog.ldf. The I
> ran the following in Query Analyser:
> exec sp_attach_db @.dbname =
> N'Mymsdb',@.filename1=N'C:\Mymsdbdata.mdf',@.filename2=N'C:\Mymsdblog.ldf'
> "Aaron [SQL Server MVP]" wrote:
>
meant to[vbcol=seagreen]
offset[vbcol=seagreen]
but[vbcol=seagreen]|||Thanks Aaron. I knida knew that answer but didn't want to hear it.
"Aaron [SQL Server MVP]" wrote:

> I think you may have to open a case with PSS, or cut your losses. In the
> future: backup is a very important word.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Phill" <Phill@.discussions.microsoft.com> wrote in message
> news:6B1824AD-016E-41CE-A851-889622057227@.microsoft.com...
> meant to
> offset
> but
>
>

msdb restore?

A terrible event has occurred. Our SQL Server 2000 database was attacked and
the master, msdb, etc was deleted. We used a utility to undelete those files
and have saved them. We had to reinstall Windows and SQL Server, but am
unable to replace the msdb. We have no backup so that isn't an option. Is
there a way to restore our DTS packages from the original msdb? Thanks.
Did you try attaching it with a different name?
http://www.aspfaq.com/
(Reverse address to reply.)
"Phill" <Phill@.discussions.microsoft.com> wrote in message
news:104A0726-0C71-4A29-B3A8-DF21C9158F38@.microsoft.com...
> A terrible event has occurred. Our SQL Server 2000 database was attacked
and
> the master, msdb, etc was deleted. We used a utility to undelete those
files
> and have saved them. We had to reinstall Windows and SQL Server, but am
> unable to replace the msdb. We have no backup so that isn't an option.
Is
> there a way to restore our DTS packages from the original msdb? Thanks.
|||I tried but I get the following error:
I/O error 38(Reached the end of the file.) detected during read at offset
0000000000000000 in file 'C:\Mymsdbdata.mdf'.
Connection Broken
"Aaron [SQL Server MVP]" wrote:

> Did you try attaching it with a different name?
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Phill" <Phill@.discussions.microsoft.com> wrote in message
> news:104A0726-0C71-4A29-B3A8-DF21C9158F38@.microsoft.com...
> and
> files
> Is
>
>
|||> I tried but I get the following error:
What *exactly* did you try? I see that you renamed the MDF file, I meant to
attach as a different database name.
If the file is corrupt, and you may be S.O.L. (this is what backups are
for).
http://www.aspfaq.com/
(Reverse address to reply.)
"Phill" <Phill@.discussions.microsoft.com> wrote in message
news:F9540632-EF19-41D8-A3FD-572722B13190@.microsoft.com...[vbcol=seagreen]
> I/O error 38(Reached the end of the file.) detected during read at offset
> 0000000000000000 in file 'C:\Mymsdbdata.mdf'.
> Connection Broken
> "Aaron [SQL Server MVP]" wrote:
attacked[vbcol=seagreen]
those[vbcol=seagreen]
am[vbcol=seagreen]
option.[vbcol=seagreen]
Thanks.[vbcol=seagreen]
|||I copied the mdf and ldf files to Mymsdbdata.mdf and Mymsdblog.ldf. The I
ran the following in Query Analyser:
exec sp_attach_db @.dbname =
N'Mymsdb',@.filename1=N'C:\Mymsdbdata.mdf',@.filenam e2=N'C:\Mymsdblog.ldf'
"Aaron [SQL Server MVP]" wrote:

> What *exactly* did you try? I see that you renamed the MDF file, I meant to
> attach as a different database name.
> If the file is corrupt, and you may be S.O.L. (this is what backups are
> for).
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Phill" <Phill@.discussions.microsoft.com> wrote in message
> news:F9540632-EF19-41D8-A3FD-572722B13190@.microsoft.com...
> attacked
> those
> am
> option.
> Thanks.
>
>
|||The data file is 0k, but the log file has data in it. I'm hoping that since
msdb was never backed up that it can be rebuilt using the log file. Can this
be done?
"Phill" wrote:
[vbcol=seagreen]
> I copied the mdf and ldf files to Mymsdbdata.mdf and Mymsdblog.ldf. The I
> ran the following in Query Analyser:
> exec sp_attach_db @.dbname =
> N'Mymsdb',@.filename1=N'C:\Mymsdbdata.mdf',@.filenam e2=N'C:\Mymsdblog.ldf'
> "Aaron [SQL Server MVP]" wrote:
|||I think you may have to open a case with PSS, or cut your losses. In the
future: backup is a very important word.
http://www.aspfaq.com/
(Reverse address to reply.)
"Phill" <Phill@.discussions.microsoft.com> wrote in message
news:6B1824AD-016E-41CE-A851-889622057227@.microsoft.com...[vbcol=seagreen]
> I copied the mdf and ldf files to Mymsdbdata.mdf and Mymsdblog.ldf. The I
> ran the following in Query Analyser:
> exec sp_attach_db @.dbname =
> N'Mymsdb',@.filename1=N'C:\Mymsdbdata.mdf',@.filenam e2=N'C:\Mymsdblog.ldf'
> "Aaron [SQL Server MVP]" wrote:
meant to[vbcol=seagreen]
offset[vbcol=seagreen]
but[vbcol=seagreen]
|||Thanks Aaron. I knida knew that answer but didn't want to hear it.
"Aaron [SQL Server MVP]" wrote:

> I think you may have to open a case with PSS, or cut your losses. In the
> future: backup is a very important word.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Phill" <Phill@.discussions.microsoft.com> wrote in message
> news:6B1824AD-016E-41CE-A851-889622057227@.microsoft.com...
> meant to
> offset
> but
>
>

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?
Thanks
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
>
|||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...
>
|||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...[vbcol=seagreen]
> 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:
|||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...
>

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
> >> >
> >>
>

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_4047d59
b9e28_ cannot be restored because it
was created by a different version of the server (134218407) than this serve
r
(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_4047d59
b9e28_ 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 versi
on
> you should be OK. This generally isn't an issue when moving between servi
ce
> 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 outp
ut
> 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...
>|||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...[vbcol=seagreen]
> 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:
>|||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...
>