Hi there -- I'm a developer who mostly uses SQL Server from that
perspective, not a DBA, and I had a client ask me a question recently that I
couldn't answer.
My client has a database that is updated constantly. A few weeks ago, he
accidentially deleted about two weeks worth of data from the database.
Since then the db's users have continued to update new data. So basically
the database is missing about two weeks worth of data from a couple of
months ago.
Is there a way to restore just those two weeks worth of data from the
transaction logs? From everything that I know and everything I've found,
you restore a database to a point in time, instead of picking out a date
range from a backup. But as I said, I'm not a DBA. So any advice would be
appreciated. Thanks!
Thanks for your help! I will pass this info along.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23qmgAZKRHHA.4252@.TK2MSFTNGP05.phx.gbl...
> If your customer has transaction log backups covering this period, you
> might be able to do this.
> Either restore (db and then log backups) up to just before that deletion,
> to a new database. Then transfer the desired data over to the production
> database (take relationships, constraints, triggers etc into
> considerations).
> Or, use some log reader tool and see if it can "mine" out counter
> statements for the delete process from your log backup. I've listed some
> such tools at http://www.karaszi.com/SQLServer/links.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mike Ripplinger" <miker@.entrerock.com> wrote in message
> news:egaC1EKRHHA.3316@.TK2MSFTNGP02.phx.gbl...
>
Showing posts with label client. Show all posts
Showing posts with label client. Show all posts
Wednesday, March 28, 2012
Restore transactions based on date range?
Hi there -- I'm a developer who mostly uses SQL Server from that
perspective, not a DBA, and I had a client ask me a question recently that I
couldn't answer.
My client has a database that is updated constantly. A few weeks ago, he
accidentially deleted about two weeks worth of data from the database.
Since then the db's users have continued to update new data. So basically
the database is missing about two weeks worth of data from a couple of
months ago.
Is there a way to restore just those two weeks worth of data from the
transaction logs? From everything that I know and everything I've found,
you restore a database to a point in time, instead of picking out a date
range from a backup. But as I said, I'm not a DBA. So any advice would be
appreciated. Thanks!If your customer has transaction log backups covering this period, you might
be able to do this.
Either restore (db and then log backups) up to just before that deletion, to
a new database. Then
transfer the desired data over to the production database (take relationship
s, constraints, triggers
etc into considerations).
Or, use some log reader tool and see if it can "mine" out counter statements
for the delete process
from your log backup. I've listed some such tools at http://www.karaszi.com/SQLSer
ver/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Ripplinger" <miker@.entrerock.com> wrote in message
news:egaC1EKRHHA.3316@.TK2MSFTNGP02.phx.gbl...
> Hi there -- I'm a developer who mostly uses SQL Server from that perspecti
ve, not a DBA, and I had
> a client ask me a question recently that I couldn't answer.
> My client has a database that is updated constantly. A few weeks ago, he
accidentially deleted
> about two weeks worth of data from the database. Since then the db's users
have continued to
> update new data. So basically the database is missing about two weeks wor
th of data from a couple
> of months ago.
> Is there a way to restore just those two weeks worth of data from the tran
saction logs? From
> everything that I know and everything I've found, you restore a database t
o a point in time,
> instead of picking out a date range from a backup. But as I said, I'm not
a DBA. So any advice
> would be appreciated. Thanks!
>|||Thanks for your help! I will pass this info along.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23qmgAZKRHHA.4252@.TK2MSFTNGP05.phx.gbl...
> If your customer has transaction log backups covering this period, you
> might be able to do this.
> Either restore (db and then log backups) up to just before that deletion,
> to a new database. Then transfer the desired data over to the production
> database (take relationships, constraints, triggers etc into
> considerations).
> Or, use some log reader tool and see if it can "mine" out counter
> statements for the delete process from your log backup. I've listed some
> such tools at http://www.karaszi.com/SQLServer/links.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mike Ripplinger" <miker@.entrerock.com> wrote in message
> news:egaC1EKRHHA.3316@.TK2MSFTNGP02.phx.gbl...
>sql
perspective, not a DBA, and I had a client ask me a question recently that I
couldn't answer.
My client has a database that is updated constantly. A few weeks ago, he
accidentially deleted about two weeks worth of data from the database.
Since then the db's users have continued to update new data. So basically
the database is missing about two weeks worth of data from a couple of
months ago.
Is there a way to restore just those two weeks worth of data from the
transaction logs? From everything that I know and everything I've found,
you restore a database to a point in time, instead of picking out a date
range from a backup. But as I said, I'm not a DBA. So any advice would be
appreciated. Thanks!If your customer has transaction log backups covering this period, you might
be able to do this.
Either restore (db and then log backups) up to just before that deletion, to
a new database. Then
transfer the desired data over to the production database (take relationship
s, constraints, triggers
etc into considerations).
Or, use some log reader tool and see if it can "mine" out counter statements
for the delete process
from your log backup. I've listed some such tools at http://www.karaszi.com/SQLSer
ver/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Ripplinger" <miker@.entrerock.com> wrote in message
news:egaC1EKRHHA.3316@.TK2MSFTNGP02.phx.gbl...
> Hi there -- I'm a developer who mostly uses SQL Server from that perspecti
ve, not a DBA, and I had
> a client ask me a question recently that I couldn't answer.
> My client has a database that is updated constantly. A few weeks ago, he
accidentially deleted
> about two weeks worth of data from the database. Since then the db's users
have continued to
> update new data. So basically the database is missing about two weeks wor
th of data from a couple
> of months ago.
> Is there a way to restore just those two weeks worth of data from the tran
saction logs? From
> everything that I know and everything I've found, you restore a database t
o a point in time,
> instead of picking out a date range from a backup. But as I said, I'm not
a DBA. So any advice
> would be appreciated. Thanks!
>|||Thanks for your help! I will pass this info along.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23qmgAZKRHHA.4252@.TK2MSFTNGP05.phx.gbl...
> If your customer has transaction log backups covering this period, you
> might be able to do this.
> Either restore (db and then log backups) up to just before that deletion,
> to a new database. Then transfer the desired data over to the production
> database (take relationships, constraints, triggers etc into
> considerations).
> Or, use some log reader tool and see if it can "mine" out counter
> statements for the delete process from your log backup. I've listed some
> such tools at http://www.karaszi.com/SQLServer/links.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mike Ripplinger" <miker@.entrerock.com> wrote in message
> news:egaC1EKRHHA.3316@.TK2MSFTNGP02.phx.gbl...
>sql
Restore transactions based on date range?
Hi there -- I'm a developer who mostly uses SQL Server from that
perspective, not a DBA, and I had a client ask me a question recently that I
couldn't answer.
My client has a database that is updated constantly. A few weeks ago, he
accidentially deleted about two weeks worth of data from the database.
Since then the db's users have continued to update new data. So basically
the database is missing about two weeks worth of data from a couple of
months ago.
Is there a way to restore just those two weeks worth of data from the
transaction logs? From everything that I know and everything I've found,
you restore a database to a point in time, instead of picking out a date
range from a backup. But as I said, I'm not a DBA. So any advice would be
appreciated. Thanks!If your customer has transaction log backups covering this period, you might be able to do this.
Either restore (db and then log backups) up to just before that deletion, to a new database. Then
transfer the desired data over to the production database (take relationships, constraints, triggers
etc into considerations).
Or, use some log reader tool and see if it can "mine" out counter statements for the delete process
from your log backup. I've listed some such tools at http://www.karaszi.com/SQLServer/links.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Ripplinger" <miker@.entrerock.com> wrote in message
news:egaC1EKRHHA.3316@.TK2MSFTNGP02.phx.gbl...
> Hi there -- I'm a developer who mostly uses SQL Server from that perspective, not a DBA, and I had
> a client ask me a question recently that I couldn't answer.
> My client has a database that is updated constantly. A few weeks ago, he accidentially deleted
> about two weeks worth of data from the database. Since then the db's users have continued to
> update new data. So basically the database is missing about two weeks worth of data from a couple
> of months ago.
> Is there a way to restore just those two weeks worth of data from the transaction logs? From
> everything that I know and everything I've found, you restore a database to a point in time,
> instead of picking out a date range from a backup. But as I said, I'm not a DBA. So any advice
> would be appreciated. Thanks!
>|||Thanks for your help! I will pass this info along.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23qmgAZKRHHA.4252@.TK2MSFTNGP05.phx.gbl...
> If your customer has transaction log backups covering this period, you
> might be able to do this.
> Either restore (db and then log backups) up to just before that deletion,
> to a new database. Then transfer the desired data over to the production
> database (take relationships, constraints, triggers etc into
> considerations).
> Or, use some log reader tool and see if it can "mine" out counter
> statements for the delete process from your log backup. I've listed some
> such tools at http://www.karaszi.com/SQLServer/links.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mike Ripplinger" <miker@.entrerock.com> wrote in message
> news:egaC1EKRHHA.3316@.TK2MSFTNGP02.phx.gbl...
>> Hi there -- I'm a developer who mostly uses SQL Server from that
>> perspective, not a DBA, and I had a client ask me a question recently
>> that I couldn't answer.
>> My client has a database that is updated constantly. A few weeks ago, he
>> accidentially deleted about two weeks worth of data from the database.
>> Since then the db's users have continued to update new data. So
>> basically the database is missing about two weeks worth of data from a
>> couple of months ago.
>> Is there a way to restore just those two weeks worth of data from the
>> transaction logs? From everything that I know and everything I've found,
>> you restore a database to a point in time, instead of picking out a date
>> range from a backup. But as I said, I'm not a DBA. So any advice would
>> be appreciated. Thanks!
>
perspective, not a DBA, and I had a client ask me a question recently that I
couldn't answer.
My client has a database that is updated constantly. A few weeks ago, he
accidentially deleted about two weeks worth of data from the database.
Since then the db's users have continued to update new data. So basically
the database is missing about two weeks worth of data from a couple of
months ago.
Is there a way to restore just those two weeks worth of data from the
transaction logs? From everything that I know and everything I've found,
you restore a database to a point in time, instead of picking out a date
range from a backup. But as I said, I'm not a DBA. So any advice would be
appreciated. Thanks!If your customer has transaction log backups covering this period, you might be able to do this.
Either restore (db and then log backups) up to just before that deletion, to a new database. Then
transfer the desired data over to the production database (take relationships, constraints, triggers
etc into considerations).
Or, use some log reader tool and see if it can "mine" out counter statements for the delete process
from your log backup. I've listed some such tools at http://www.karaszi.com/SQLServer/links.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Ripplinger" <miker@.entrerock.com> wrote in message
news:egaC1EKRHHA.3316@.TK2MSFTNGP02.phx.gbl...
> Hi there -- I'm a developer who mostly uses SQL Server from that perspective, not a DBA, and I had
> a client ask me a question recently that I couldn't answer.
> My client has a database that is updated constantly. A few weeks ago, he accidentially deleted
> about two weeks worth of data from the database. Since then the db's users have continued to
> update new data. So basically the database is missing about two weeks worth of data from a couple
> of months ago.
> Is there a way to restore just those two weeks worth of data from the transaction logs? From
> everything that I know and everything I've found, you restore a database to a point in time,
> instead of picking out a date range from a backup. But as I said, I'm not a DBA. So any advice
> would be appreciated. Thanks!
>|||Thanks for your help! I will pass this info along.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23qmgAZKRHHA.4252@.TK2MSFTNGP05.phx.gbl...
> If your customer has transaction log backups covering this period, you
> might be able to do this.
> Either restore (db and then log backups) up to just before that deletion,
> to a new database. Then transfer the desired data over to the production
> database (take relationships, constraints, triggers etc into
> considerations).
> Or, use some log reader tool and see if it can "mine" out counter
> statements for the delete process from your log backup. I've listed some
> such tools at http://www.karaszi.com/SQLServer/links.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mike Ripplinger" <miker@.entrerock.com> wrote in message
> news:egaC1EKRHHA.3316@.TK2MSFTNGP02.phx.gbl...
>> Hi there -- I'm a developer who mostly uses SQL Server from that
>> perspective, not a DBA, and I had a client ask me a question recently
>> that I couldn't answer.
>> My client has a database that is updated constantly. A few weeks ago, he
>> accidentially deleted about two weeks worth of data from the database.
>> Since then the db's users have continued to update new data. So
>> basically the database is missing about two weeks worth of data from a
>> couple of months ago.
>> Is there a way to restore just those two weeks worth of data from the
>> transaction logs? From everything that I know and everything I've found,
>> you restore a database to a point in time, instead of picking out a date
>> range from a backup. But as I said, I'm not a DBA. So any advice would
>> be appreciated. Thanks!
>
Monday, March 26, 2012
Restore to different version of 2003 OS
Hello,
I have a client with a database and want to use a second server as warm spare.
Primary server is 2003 Std and the spare is 2003Ent.
I've heard that the OS must be the same to restore.
I can understand the SQL needs the same version 2000 and service pack level
on each server but what about the OS?
Thanks in advance
Kevin"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
>
The OS can be different.
David|||To restore a system database, the SQL build numbers must match exactly. To
restore a non-system database, the major levels must match (I.E 7.0, 8.0,
9.0 etc). The operating system does not matter as long as it is supported
for that release of SQL.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
> Thanks in advance
> Kevin|||While I agree with what the others have posted, you are going to test this
all first, right?
"Kevin1aB" wrote:
> Hello,
> I have a client with a database and want to use a second server as warm spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack level
> on each server but what about the OS?
> Thanks in advance
> Kevin|||Thanks to all who posted. I will test it in the next week or so.
Regards,
Kevin B
"ChrisR" wrote:
> While I agree with what the others have posted, you are going to test this
> all first, right?
> "Kevin1aB" wrote:
> > Hello,
> > I have a client with a database and want to use a second server as warm spare.
> > Primary server is 2003 Std and the spare is 2003Ent.
> > I've heard that the OS must be the same to restore.
> > I can understand the SQL needs the same version 2000 and service pack level
> > on each server but what about the OS?
> >
> > Thanks in advance
> >
> > Kevin
I have a client with a database and want to use a second server as warm spare.
Primary server is 2003 Std and the spare is 2003Ent.
I've heard that the OS must be the same to restore.
I can understand the SQL needs the same version 2000 and service pack level
on each server but what about the OS?
Thanks in advance
Kevin"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
>
The OS can be different.
David|||To restore a system database, the SQL build numbers must match exactly. To
restore a non-system database, the major levels must match (I.E 7.0, 8.0,
9.0 etc). The operating system does not matter as long as it is supported
for that release of SQL.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
> Thanks in advance
> Kevin|||While I agree with what the others have posted, you are going to test this
all first, right?
"Kevin1aB" wrote:
> Hello,
> I have a client with a database and want to use a second server as warm spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack level
> on each server but what about the OS?
> Thanks in advance
> Kevin|||Thanks to all who posted. I will test it in the next week or so.
Regards,
Kevin B
"ChrisR" wrote:
> While I agree with what the others have posted, you are going to test this
> all first, right?
> "Kevin1aB" wrote:
> > Hello,
> > I have a client with a database and want to use a second server as warm spare.
> > Primary server is 2003 Std and the spare is 2003Ent.
> > I've heard that the OS must be the same to restore.
> > I can understand the SQL needs the same version 2000 and service pack level
> > on each server but what about the OS?
> >
> > Thanks in advance
> >
> > Kevin
Restore to different version of 2003 OS
Hello,
I have a client with a database and want to use a second server as warm spare.
Primary server is 2003 Std and the spare is 2003Ent.
I've heard that the OS must be the same to restore.
I can understand the SQL needs the same version 2000 and service pack level
on each server but what about the OS?
Thanks in advance
Kevin
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
>
The OS can be different.
David
|||To restore a system database, the SQL build numbers must match exactly. To
restore a non-system database, the major levels must match (I.E 7.0, 8.0,
9.0 etc). The operating system does not matter as long as it is supported
for that release of SQL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
> Thanks in advance
> Kevin
|||While I agree with what the others have posted, you are going to test this
all first, right?
"Kevin1aB" wrote:
> Hello,
> I have a client with a database and want to use a second server as warm spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack level
> on each server but what about the OS?
> Thanks in advance
> Kevin
|||Thanks to all who posted. I will test it in the next week or so.
Regards,
Kevin B
"ChrisR" wrote:
[vbcol=seagreen]
> While I agree with what the others have posted, you are going to test this
> all first, right?
> "Kevin1aB" wrote:
I have a client with a database and want to use a second server as warm spare.
Primary server is 2003 Std and the spare is 2003Ent.
I've heard that the OS must be the same to restore.
I can understand the SQL needs the same version 2000 and service pack level
on each server but what about the OS?
Thanks in advance
Kevin
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
>
The OS can be different.
David
|||To restore a system database, the SQL build numbers must match exactly. To
restore a non-system database, the major levels must match (I.E 7.0, 8.0,
9.0 etc). The operating system does not matter as long as it is supported
for that release of SQL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
> Thanks in advance
> Kevin
|||While I agree with what the others have posted, you are going to test this
all first, right?
"Kevin1aB" wrote:
> Hello,
> I have a client with a database and want to use a second server as warm spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack level
> on each server but what about the OS?
> Thanks in advance
> Kevin
|||Thanks to all who posted. I will test it in the next week or so.
Regards,
Kevin B
"ChrisR" wrote:
[vbcol=seagreen]
> While I agree with what the others have posted, you are going to test this
> all first, right?
> "Kevin1aB" wrote:
Restore to different version of 2003 OS
Hello,
I have a client with a database and want to use a second server as warm spar
e.
Primary server is 2003 Std and the spare is 2003Ent.
I've heard that the OS must be the same to restore.
I can understand the SQL needs the same version 2000 and service pack level
on each server but what about the OS?
Thanks in advance
Kevin"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
>
The OS can be different.
David|||To restore a system database, the SQL build numbers must match exactly. To
restore a non-system database, the major levels must match (I.E 7.0, 8.0,
9.0 etc). The operating system does not matter as long as it is supported
for that release of SQL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
> Thanks in advance
> Kevin|||While I agree with what the others have posted, you are going to test this
all first, right?
"Kevin1aB" wrote:
> Hello,
> I have a client with a database and want to use a second server as warm sp
are.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack leve
l
> on each server but what about the OS?
> Thanks in advance
> Kevin|||Thanks to all who posted. I will test it in the next week or so.
Regards,
Kevin B
"ChrisR" wrote:
[vbcol=seagreen]
> While I agree with what the others have posted, you are going to test this
> all first, right?
> "Kevin1aB" wrote:
>
I have a client with a database and want to use a second server as warm spar
e.
Primary server is 2003 Std and the spare is 2003Ent.
I've heard that the OS must be the same to restore.
I can understand the SQL needs the same version 2000 and service pack level
on each server but what about the OS?
Thanks in advance
Kevin"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
>
The OS can be different.
David|||To restore a system database, the SQL build numbers must match exactly. To
restore a non-system database, the major levels must match (I.E 7.0, 8.0,
9.0 etc). The operating system does not matter as long as it is supported
for that release of SQL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
> Thanks in advance
> Kevin|||While I agree with what the others have posted, you are going to test this
all first, right?
"Kevin1aB" wrote:
> Hello,
> I have a client with a database and want to use a second server as warm sp
are.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack leve
l
> on each server but what about the OS?
> Thanks in advance
> Kevin|||Thanks to all who posted. I will test it in the next week or so.
Regards,
Kevin B
"ChrisR" wrote:
[vbcol=seagreen]
> While I agree with what the others have posted, you are going to test this
> all first, right?
> "Kevin1aB" wrote:
>
Monday, March 12, 2012
Restore problem... "The media family on device '%ls' is incorrectly formed"
A client keeps sending me .BAK files. A couple have worked, but I
have gotten this error on many:
Error 3241 Severity 16 State 1
The media family on device '%ls' is incorrectly formed. SQL Server
cannot process this media family.
If I view the contents of the .BAK (in Enterprise Manager), it says it
is INCOMPLETE.
This indicates that maybe the backup was bad. However, since they have
sent me so many bad ones, my question is why are these backups turning
out bad?
Some details:
-The client is using SQL Server 2000 SP4, so am I
-I am running Win2K Server, they are running Win 2003 server.
-I looked at KB 297104 which deals with this error, but that is for
pre-SP4.
-When I run a restore verifyonly, I get the same error
Since I am off-site and can't go to the client site, any ideas on what
they may be doing wrong or what we can do for me to get a legitimate
copy of this database on my server? I am going crazy with these files
that won't load and don't know what to tell my client.have them run a verify before sending them to you. This should guarantee a
valid backup.
--
RelevantNoise.com - dedicated to mining blogs for business intelligence.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mike C" <michaeljc70@.hotmail.com> wrote in message
news:1187736521.741462.231380@.l22g2000prc.googlegroups.com...
>A client keeps sending me .BAK files. A couple have worked, but I
> have gotten this error on many:
> Error 3241 Severity 16 State 1
> The media family on device '%ls' is incorrectly formed. SQL Server
> cannot process this media family.
> If I view the contents of the .BAK (in Enterprise Manager), it says it
> is INCOMPLETE.
> This indicates that maybe the backup was bad. However, since they have
> sent me so many bad ones, my question is why are these backups turning
> out bad?
> Some details:
> -The client is using SQL Server 2000 SP4, so am I
> -I am running Win2K Server, they are running Win 2003 server.
> -I looked at KB 297104 which deals with this error, but that is for
> pre-SP4.
> -When I run a restore verifyonly, I get the same error
> Since I am off-site and can't go to the client site, any ideas on what
> they may be doing wrong or what we can do for me to get a legitimate
> copy of this database on my server? I am going crazy with these files
> that won't load and don't know what to tell my client.
>|||Hello,
First of all tell your client to do a restore with verify only or header only
to test, on their side, the correctness of the backup. If it's possible, tell
the client to do a full restore of the backup.
Second, if the first worked out well, send back the media to the client and
tell them to try the above process.
It is possible that between different copies of the backup file it becomes
corrupt. If the transfer of the backup file it is done over wan this is
something sure. A second possibility it is this file is part of a multivolume
backup. Sql Server has the option to backup a database to more than one file
to speed up the backup process.
Hope this helps you solve the problem.
I recommend you reading this too
http://www.dbforums.com/showthread.php?t=682406.
Cheers.
Mike C wrote:
>A client keeps sending me .BAK files. A couple have worked, but I
>have gotten this error on many:
>Error 3241 Severity 16 State 1
>The media family on device '%ls' is incorrectly formed. SQL Server
>cannot process this media family.
>If I view the contents of the .BAK (in Enterprise Manager), it says it
>is INCOMPLETE.
>This indicates that maybe the backup was bad. However, since they have
>sent me so many bad ones, my question is why are these backups turning
>out bad?
>Some details:
>-The client is using SQL Server 2000 SP4, so am I
>-I am running Win2K Server, they are running Win 2003 server.
>-I looked at KB 297104 which deals with this error, but that is for
>pre-SP4.
>-When I run a restore verifyonly, I get the same error
>Since I am off-site and can't go to the client site, any ideas on what
>they may be doing wrong or what we can do for me to get a legitimate
>copy of this database on my server? I am going crazy with these files
>that won't load and don't know what to tell my client.|||On Aug 22, 5:08 am, "flooriin" <u36842@.uwe> wrote:
> Hello,
> First of all tell your client to do arestorewith verify only or header only
> to test, on their side, the correctness of the backup. If it's possible, tell
> the client to do a fullrestoreof the backup.
> Second, if the first worked out well, send back themediato the client and
> tell them to try the above process.
> It is possible that between different copies of the backup file it becomes
> corrupt. If the transfer of the backup file it is done over wan this is
> something sure. A second possibility it is this file is part of a multivolume
> backup. Sql Server has the option to backup a database to more than one file
> to speed up the backup process.
> Hope this helps you solve theproblem.
> I recommend you reading this toohttp://www.dbforums.com/showthread.php?t=682406.
> Cheers.
> Mike C wrote:
> >A client keeps sending me .BAK files. A couple have worked, but I
> >have gotten this error on many:
> >Error 3241 Severity 16 State 1
> >Themediafamily on device '%ls' is incorrectly formed. SQL Server
> >cannot process thismediafamily.
> >If I view the contents of the .BAK (in Enterprise Manager), it says it
> >is INCOMPLETE.
> >This indicates that maybe the backup was bad. However, since they have
> >sent me so many bad ones, my question is why are these backups turning
> >out bad?
> >Some details:
> >-The client is using SQL Server 2000 SP4, so am I
> >-I am running Win2K Server, they are running Win 2003 server.
> >-I looked at KB 297104 which deals with this error, but that is for
> >pre-SP4.
> >-When I run arestoreverifyonly, I get the same error
> >Since I am off-site and can't go to the client site, any ideas on what
> >they may be doing wrong or what we can do for me to get a legitimate
> >copy of this database on my server? I am going crazy with these files
> >that won't load and don't know what to tell my client.
The client said they did a verify when they did the backup. I will
have them check to see if RESTORE VERIFYONLY works. Assuming the file
is good, I can only think of 2 unlikely issues:
-The file is becoming corrupt when they zip it up. Since it is bigger
than a DVD, that is the only way to get it to me.
-Running W2K Server vs. W2003 Server is making some dofference.|||On Aug 22, 5:08 am, "flooriin" <u36842@.uwe> wrote:
> Hello,
> First of all tell your client to do a restore with verify only or header only
> to test, on their side, the correctness of the backup. If it's possible, tell
> the client to do a full restore of the backup.
> Second, if the first worked out well, send back the media to the client and
> tell them to try the above process.
> It is possible that between different copies of the backup file it becomes
> corrupt. If the transfer of the backup file it is done over wan this is
> something sure. A second possibility it is this file is part of a multivolume
> backup. Sql Server has the option to backup a database to more than one file
> to speed up the backup process.
> Hope this helps you solve the problem.
> I recommend you reading this toohttp://www.dbforums.com/showthread.php?t=682406.
> Cheers.
> Mike C wrote:
> >A client keeps sending me .BAK files. A couple have worked, but I
> >have gotten this error on many:
> >Error 3241 Severity 16 State 1
> >The media family on device '%ls' is incorrectly formed. SQL Server
> >cannot process this media family.
> >If I view the contents of the .BAK (in Enterprise Manager), it says it
> >is INCOMPLETE.
> >This indicates that maybe the backup was bad. However, since they have
> >sent me so many bad ones, my question is why are these backups turning
> >out bad?
> >Some details:
> >-The client is using SQL Server 2000 SP4, so am I
> >-I am running Win2K Server, they are running Win 2003 server.
> >-I looked at KB 297104 which deals with this error, but that is for
> >pre-SP4.
> >-When I run a restore verifyonly, I get the same error
> >Since I am off-site and can't go to the client site, any ideas on what
> >they may be doing wrong or what we can do for me to get a legitimate
> >copy of this database on my server? I am going crazy with these files
> >that won't load and don't know what to tell my client.
The restore verifyonly or backuponly works at the client site. I
verified versions. They are using Sql Server 2000 SP3 (plus a
cumulative patch) while I am running SP4. I can try and go back to
SP3, but that seems unlikely culprit (more likely if their version
were higher than mine). Any other ideas?|||On Aug 22, 5:08 am, "flooriin" <u36842@.uwe> wrote:
> Hello,
> First of all tell your client to do a restore with verify only or header only
> to test, on their side, the correctness of the backup. If it's possible, tell
> the client to do a full restore of the backup.
> Second, if the first worked out well, send back the media to the client and
> tell them to try the above process.
> It is possible that between different copies of the backup file it becomes
> corrupt. If the transfer of the backup file it is done over wan this is
> something sure. A second possibility it is this file is part of a multivolume
> backup. Sql Server has the option to backup a database to more than one file
> to speed up the backup process.
> Hope this helps you solve the problem.
> I recommend you reading this toohttp://www.dbforums.com/showthread.php?t=682406.
> Cheers.
> Mike C wrote:
> >A client keeps sending me .BAK files. A couple have worked, but I
> >have gotten this error on many:
> >Error 3241 Severity 16 State 1
> >The media family on device '%ls' is incorrectly formed. SQL Server
> >cannot process this media family.
> >If I view the contents of the .BAK (in Enterprise Manager), it says it
> >is INCOMPLETE.
> >This indicates that maybe the backup was bad. However, since they have
> >sent me so many bad ones, my question is why are these backups turning
> >out bad?
> >Some details:
> >-The client is using SQL Server 2000 SP4, so am I
> >-I am running Win2K Server, they are running Win 2003 server.
> >-I looked at KB 297104 which deals with this error, but that is for
> >pre-SP4.
> >-When I run a restore verifyonly, I get the same error
> >Since I am off-site and can't go to the client site, any ideas on what
> >they may be doing wrong or what we can do for me to get a legitimate
> >copy of this database on my server? I am going crazy with these files
> >that won't load and don't know what to tell my client.
Do you think me being on w2K and them on W2003 server makes a
difference?|||I do not believe the problem arise because of different Windows versions. I
think it's more about database and the process to backup and deliver the
database. You have said that are cases when the backup was restored
successfully. What is different from your current situation? I am more
concern about different Sql Server version. I know about a bug in SP3 when a
differential database backup could miss to save some extents ... but you are
talking about full backup.
Read this too
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=24&messageid=167366&p=2
Maybe it will help you. Read the last post and try out the utility told
there.
Cheers.
Mike C wrote:
>> Hello,
>[quoted text clipped - 40 lines]
>> >copy of this database on my server? I am going crazy with these files
>> >that won't load and don't know what to tell my client.
>Do you think me being on w2K and them on W2003 server makes a
>difference?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200708/1|||On Aug 24, 6:25 am, "flooriin via SQLMonster.com" <u36842@.uwe> wrote:
> I do not believe the problem arise because of different Windows versions. I
> think it's more about database and the process to backup and deliver the
> database. You have said that are cases when the backup was restored
> successfully. What is different from your current situation? I am more
> concern about different Sql Server version. I know about a bug in SP3 when a
> differential database backup could miss to save some extents ... but you are
> talking about full backup.
> Read this toohttp://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=24&mes...
> Maybe it will help you. Read the last post and try out the utility told
> there.
> Cheers.
> Mike C wrote:
> >> Hello,
> >[quoted text clipped - 40 lines]
> >> >copy of this database on my server? I am going crazy with these files
> >> >that won't load and don't know what to tell my client.
> >Do you think me being on w2K and them on W2003 server makes a
> >difference?
> --
> Message posted via SQLMonster.comhttp://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200708/1
I installed SQL Server 2000 MSDE on an XP box and I was able to
restore the backup. That means the file is fine. I am just going to
work with that since I don't need any of the enterprise features.
This is a short project and it isn't worth spending 100 hrs trying to
figure out what the problem is.
have gotten this error on many:
Error 3241 Severity 16 State 1
The media family on device '%ls' is incorrectly formed. SQL Server
cannot process this media family.
If I view the contents of the .BAK (in Enterprise Manager), it says it
is INCOMPLETE.
This indicates that maybe the backup was bad. However, since they have
sent me so many bad ones, my question is why are these backups turning
out bad?
Some details:
-The client is using SQL Server 2000 SP4, so am I
-I am running Win2K Server, they are running Win 2003 server.
-I looked at KB 297104 which deals with this error, but that is for
pre-SP4.
-When I run a restore verifyonly, I get the same error
Since I am off-site and can't go to the client site, any ideas on what
they may be doing wrong or what we can do for me to get a legitimate
copy of this database on my server? I am going crazy with these files
that won't load and don't know what to tell my client.have them run a verify before sending them to you. This should guarantee a
valid backup.
--
RelevantNoise.com - dedicated to mining blogs for business intelligence.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mike C" <michaeljc70@.hotmail.com> wrote in message
news:1187736521.741462.231380@.l22g2000prc.googlegroups.com...
>A client keeps sending me .BAK files. A couple have worked, but I
> have gotten this error on many:
> Error 3241 Severity 16 State 1
> The media family on device '%ls' is incorrectly formed. SQL Server
> cannot process this media family.
> If I view the contents of the .BAK (in Enterprise Manager), it says it
> is INCOMPLETE.
> This indicates that maybe the backup was bad. However, since they have
> sent me so many bad ones, my question is why are these backups turning
> out bad?
> Some details:
> -The client is using SQL Server 2000 SP4, so am I
> -I am running Win2K Server, they are running Win 2003 server.
> -I looked at KB 297104 which deals with this error, but that is for
> pre-SP4.
> -When I run a restore verifyonly, I get the same error
> Since I am off-site and can't go to the client site, any ideas on what
> they may be doing wrong or what we can do for me to get a legitimate
> copy of this database on my server? I am going crazy with these files
> that won't load and don't know what to tell my client.
>|||Hello,
First of all tell your client to do a restore with verify only or header only
to test, on their side, the correctness of the backup. If it's possible, tell
the client to do a full restore of the backup.
Second, if the first worked out well, send back the media to the client and
tell them to try the above process.
It is possible that between different copies of the backup file it becomes
corrupt. If the transfer of the backup file it is done over wan this is
something sure. A second possibility it is this file is part of a multivolume
backup. Sql Server has the option to backup a database to more than one file
to speed up the backup process.
Hope this helps you solve the problem.
I recommend you reading this too
http://www.dbforums.com/showthread.php?t=682406.
Cheers.
Mike C wrote:
>A client keeps sending me .BAK files. A couple have worked, but I
>have gotten this error on many:
>Error 3241 Severity 16 State 1
>The media family on device '%ls' is incorrectly formed. SQL Server
>cannot process this media family.
>If I view the contents of the .BAK (in Enterprise Manager), it says it
>is INCOMPLETE.
>This indicates that maybe the backup was bad. However, since they have
>sent me so many bad ones, my question is why are these backups turning
>out bad?
>Some details:
>-The client is using SQL Server 2000 SP4, so am I
>-I am running Win2K Server, they are running Win 2003 server.
>-I looked at KB 297104 which deals with this error, but that is for
>pre-SP4.
>-When I run a restore verifyonly, I get the same error
>Since I am off-site and can't go to the client site, any ideas on what
>they may be doing wrong or what we can do for me to get a legitimate
>copy of this database on my server? I am going crazy with these files
>that won't load and don't know what to tell my client.|||On Aug 22, 5:08 am, "flooriin" <u36842@.uwe> wrote:
> Hello,
> First of all tell your client to do arestorewith verify only or header only
> to test, on their side, the correctness of the backup. If it's possible, tell
> the client to do a fullrestoreof the backup.
> Second, if the first worked out well, send back themediato the client and
> tell them to try the above process.
> It is possible that between different copies of the backup file it becomes
> corrupt. If the transfer of the backup file it is done over wan this is
> something sure. A second possibility it is this file is part of a multivolume
> backup. Sql Server has the option to backup a database to more than one file
> to speed up the backup process.
> Hope this helps you solve theproblem.
> I recommend you reading this toohttp://www.dbforums.com/showthread.php?t=682406.
> Cheers.
> Mike C wrote:
> >A client keeps sending me .BAK files. A couple have worked, but I
> >have gotten this error on many:
> >Error 3241 Severity 16 State 1
> >Themediafamily on device '%ls' is incorrectly formed. SQL Server
> >cannot process thismediafamily.
> >If I view the contents of the .BAK (in Enterprise Manager), it says it
> >is INCOMPLETE.
> >This indicates that maybe the backup was bad. However, since they have
> >sent me so many bad ones, my question is why are these backups turning
> >out bad?
> >Some details:
> >-The client is using SQL Server 2000 SP4, so am I
> >-I am running Win2K Server, they are running Win 2003 server.
> >-I looked at KB 297104 which deals with this error, but that is for
> >pre-SP4.
> >-When I run arestoreverifyonly, I get the same error
> >Since I am off-site and can't go to the client site, any ideas on what
> >they may be doing wrong or what we can do for me to get a legitimate
> >copy of this database on my server? I am going crazy with these files
> >that won't load and don't know what to tell my client.
The client said they did a verify when they did the backup. I will
have them check to see if RESTORE VERIFYONLY works. Assuming the file
is good, I can only think of 2 unlikely issues:
-The file is becoming corrupt when they zip it up. Since it is bigger
than a DVD, that is the only way to get it to me.
-Running W2K Server vs. W2003 Server is making some dofference.|||On Aug 22, 5:08 am, "flooriin" <u36842@.uwe> wrote:
> Hello,
> First of all tell your client to do a restore with verify only or header only
> to test, on their side, the correctness of the backup. If it's possible, tell
> the client to do a full restore of the backup.
> Second, if the first worked out well, send back the media to the client and
> tell them to try the above process.
> It is possible that between different copies of the backup file it becomes
> corrupt. If the transfer of the backup file it is done over wan this is
> something sure. A second possibility it is this file is part of a multivolume
> backup. Sql Server has the option to backup a database to more than one file
> to speed up the backup process.
> Hope this helps you solve the problem.
> I recommend you reading this toohttp://www.dbforums.com/showthread.php?t=682406.
> Cheers.
> Mike C wrote:
> >A client keeps sending me .BAK files. A couple have worked, but I
> >have gotten this error on many:
> >Error 3241 Severity 16 State 1
> >The media family on device '%ls' is incorrectly formed. SQL Server
> >cannot process this media family.
> >If I view the contents of the .BAK (in Enterprise Manager), it says it
> >is INCOMPLETE.
> >This indicates that maybe the backup was bad. However, since they have
> >sent me so many bad ones, my question is why are these backups turning
> >out bad?
> >Some details:
> >-The client is using SQL Server 2000 SP4, so am I
> >-I am running Win2K Server, they are running Win 2003 server.
> >-I looked at KB 297104 which deals with this error, but that is for
> >pre-SP4.
> >-When I run a restore verifyonly, I get the same error
> >Since I am off-site and can't go to the client site, any ideas on what
> >they may be doing wrong or what we can do for me to get a legitimate
> >copy of this database on my server? I am going crazy with these files
> >that won't load and don't know what to tell my client.
The restore verifyonly or backuponly works at the client site. I
verified versions. They are using Sql Server 2000 SP3 (plus a
cumulative patch) while I am running SP4. I can try and go back to
SP3, but that seems unlikely culprit (more likely if their version
were higher than mine). Any other ideas?|||On Aug 22, 5:08 am, "flooriin" <u36842@.uwe> wrote:
> Hello,
> First of all tell your client to do a restore with verify only or header only
> to test, on their side, the correctness of the backup. If it's possible, tell
> the client to do a full restore of the backup.
> Second, if the first worked out well, send back the media to the client and
> tell them to try the above process.
> It is possible that between different copies of the backup file it becomes
> corrupt. If the transfer of the backup file it is done over wan this is
> something sure. A second possibility it is this file is part of a multivolume
> backup. Sql Server has the option to backup a database to more than one file
> to speed up the backup process.
> Hope this helps you solve the problem.
> I recommend you reading this toohttp://www.dbforums.com/showthread.php?t=682406.
> Cheers.
> Mike C wrote:
> >A client keeps sending me .BAK files. A couple have worked, but I
> >have gotten this error on many:
> >Error 3241 Severity 16 State 1
> >The media family on device '%ls' is incorrectly formed. SQL Server
> >cannot process this media family.
> >If I view the contents of the .BAK (in Enterprise Manager), it says it
> >is INCOMPLETE.
> >This indicates that maybe the backup was bad. However, since they have
> >sent me so many bad ones, my question is why are these backups turning
> >out bad?
> >Some details:
> >-The client is using SQL Server 2000 SP4, so am I
> >-I am running Win2K Server, they are running Win 2003 server.
> >-I looked at KB 297104 which deals with this error, but that is for
> >pre-SP4.
> >-When I run a restore verifyonly, I get the same error
> >Since I am off-site and can't go to the client site, any ideas on what
> >they may be doing wrong or what we can do for me to get a legitimate
> >copy of this database on my server? I am going crazy with these files
> >that won't load and don't know what to tell my client.
Do you think me being on w2K and them on W2003 server makes a
difference?|||I do not believe the problem arise because of different Windows versions. I
think it's more about database and the process to backup and deliver the
database. You have said that are cases when the backup was restored
successfully. What is different from your current situation? I am more
concern about different Sql Server version. I know about a bug in SP3 when a
differential database backup could miss to save some extents ... but you are
talking about full backup.
Read this too
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=24&messageid=167366&p=2
Maybe it will help you. Read the last post and try out the utility told
there.
Cheers.
Mike C wrote:
>> Hello,
>[quoted text clipped - 40 lines]
>> >copy of this database on my server? I am going crazy with these files
>> >that won't load and don't know what to tell my client.
>Do you think me being on w2K and them on W2003 server makes a
>difference?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200708/1|||On Aug 24, 6:25 am, "flooriin via SQLMonster.com" <u36842@.uwe> wrote:
> I do not believe the problem arise because of different Windows versions. I
> think it's more about database and the process to backup and deliver the
> database. You have said that are cases when the backup was restored
> successfully. What is different from your current situation? I am more
> concern about different Sql Server version. I know about a bug in SP3 when a
> differential database backup could miss to save some extents ... but you are
> talking about full backup.
> Read this toohttp://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=24&mes...
> Maybe it will help you. Read the last post and try out the utility told
> there.
> Cheers.
> Mike C wrote:
> >> Hello,
> >[quoted text clipped - 40 lines]
> >> >copy of this database on my server? I am going crazy with these files
> >> >that won't load and don't know what to tell my client.
> >Do you think me being on w2K and them on W2003 server makes a
> >difference?
> --
> Message posted via SQLMonster.comhttp://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200708/1
I installed SQL Server 2000 MSDE on an XP box and I was able to
restore the backup. That means the file is fine. I am just going to
work with that since I don't need any of the enterprise features.
This is a short project and it isn't worth spending 100 hrs trying to
figure out what the problem is.
Subscribe to:
Posts (Atom)