What is the best document for restoring databases from one SQL 2000 server to a new SQL 2000 server?
What do you mean by document?
Refer to Books Online (within the SQL Server program group). It will =
tell you how to use the Transact-SQL commands BACKUP and RESTORE. =20
You might also find these KB articles helpful:
INF: Disaster Recovery Articles for Microsoft SQL Server
http://www.support.microsoft.com/?id=3D307775
INF: Moving SQL Server databases to a new location with Detach/Attach
http://www.support.microsoft.com/?id=3D224071
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://www.support.microsoft.com/?id=3D314546
INF: Using the WITH MOVE Option with the RESTORE Statement
http://support.microsoft.com/?id=3D221465
PRB: User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=3D168001
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=3D246133
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is =
Incomplete
http://www.support.microsoft.com/?id=3D274188
How to Resolve Permission Issues When a Database Is Moved Between SQL =
Servers
http://www.support.microsoft.com/?id=3D240872
SAMPLE: Mapsids.exe Helps Map SIDs Between User and Master Databases =
When Database Is Moved
http://www.support.microsoft.com/?id=3D298897
--=20
Keith
"new2sql" <anonymous@.discussions.microsoft.com> wrote in message =
news:E22BCD34-B235-420E-848E-9C2A63576020@.microsoft.com...
> What is the best document for restoring databases from one SQL 2000 =
server to a new SQL 2000 server?
Showing posts with label document. Show all posts
Showing posts with label document. Show all posts
Sunday, February 19, 2012
Thursday, February 16, 2012
Backup/Restore
What is the best document for restoring databases from one SQL 2000 server to a new SQL 2000 server?What do you mean by document?
Refer to Books Online (within the SQL Server program group). It will =tell you how to use the Transact-SQL commands BACKUP and RESTORE.
You might also find these KB articles helpful:
INF: Disaster Recovery Articles for Microsoft SQL Server
http://www.support.microsoft.com/?id=3D307775
INF: Moving SQL Server databases to a new location with Detach/Attach
http://www.support.microsoft.com/?id=3D224071
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://www.support.microsoft.com/?id=3D314546
INF: Using the WITH MOVE Option with the RESTORE Statement
http://support.microsoft.com/?id=3D221465
PRB: User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=3D168001
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=3D246133
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is =Incomplete
http://www.support.microsoft.com/?id=3D274188
How to Resolve Permission Issues When a Database Is Moved Between SQL =Servers
http://www.support.microsoft.com/?id=3D240872
SAMPLE: Mapsids.exe Helps Map SIDs Between User and Master Databases =When Database Is Moved
http://www.support.microsoft.com/?id=3D298897
-- Keith
"new2sql" <anonymous@.discussions.microsoft.com> wrote in message =news:E22BCD34-B235-420E-848E-9C2A63576020@.microsoft.com...
> What is the best document for restoring databases from one SQL 2000 =server to a new SQL 2000 server?
Refer to Books Online (within the SQL Server program group). It will =tell you how to use the Transact-SQL commands BACKUP and RESTORE.
You might also find these KB articles helpful:
INF: Disaster Recovery Articles for Microsoft SQL Server
http://www.support.microsoft.com/?id=3D307775
INF: Moving SQL Server databases to a new location with Detach/Attach
http://www.support.microsoft.com/?id=3D224071
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://www.support.microsoft.com/?id=3D314546
INF: Using the WITH MOVE Option with the RESTORE Statement
http://support.microsoft.com/?id=3D221465
PRB: User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=3D168001
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=3D246133
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is =Incomplete
http://www.support.microsoft.com/?id=3D274188
How to Resolve Permission Issues When a Database Is Moved Between SQL =Servers
http://www.support.microsoft.com/?id=3D240872
SAMPLE: Mapsids.exe Helps Map SIDs Between User and Master Databases =When Database Is Moved
http://www.support.microsoft.com/?id=3D298897
-- Keith
"new2sql" <anonymous@.discussions.microsoft.com> wrote in message =news:E22BCD34-B235-420E-848E-9C2A63576020@.microsoft.com...
> What is the best document for restoring databases from one SQL 2000 =server to a new SQL 2000 server?
Backup/Restore
What is the best document for restoring databases from one SQL 2000 server t
o a new SQL 2000 server?What do you mean by document?
Refer to Books Online (within the SQL Server program group). It will =
tell you how to use the Transact-SQL commands BACKUP and RESTORE. =20
You might also find these KB articles helpful:
INF: Disaster Recovery Articles for Microsoft SQL Server
http://www.support.microsoft.com/?id=3D307775
INF: Moving SQL Server databases to a new location with Detach/Attach
http://www.support.microsoft.com/?id=3D224071
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://www.support.microsoft.com/?id=3D314546
INF: Using the WITH MOVE Option with the RESTORE Statement
http://support.microsoft.com/?id=3D221465
PRB: User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=3D168001
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=3D246133
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is =
Incomplete
http://www.support.microsoft.com/?id=3D274188
How to Resolve Permission Issues When a Database Is Moved Between SQL =
Servers
http://www.support.microsoft.com/?id=3D240872
SAMPLE: Mapsids.exe Helps Map SIDs Between User and Master Databases =
When Database Is Moved
http://www.support.microsoft.com/?id=3D298897
--=20
Keith
"new2sql" <anonymous@.discussions.microsoft.com> wrote in message =
news:E22BCD34-B235-420E-848E-9C2A63576020@.microsoft.com...
> What is the best document for restoring databases from one SQL 2000 =
server to a new SQL 2000 server?
o a new SQL 2000 server?What do you mean by document?
Refer to Books Online (within the SQL Server program group). It will =
tell you how to use the Transact-SQL commands BACKUP and RESTORE. =20
You might also find these KB articles helpful:
INF: Disaster Recovery Articles for Microsoft SQL Server
http://www.support.microsoft.com/?id=3D307775
INF: Moving SQL Server databases to a new location with Detach/Attach
http://www.support.microsoft.com/?id=3D224071
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://www.support.microsoft.com/?id=3D314546
INF: Using the WITH MOVE Option with the RESTORE Statement
http://support.microsoft.com/?id=3D221465
PRB: User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=3D168001
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=3D246133
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is =
Incomplete
http://www.support.microsoft.com/?id=3D274188
How to Resolve Permission Issues When a Database Is Moved Between SQL =
Servers
http://www.support.microsoft.com/?id=3D240872
SAMPLE: Mapsids.exe Helps Map SIDs Between User and Master Databases =
When Database Is Moved
http://www.support.microsoft.com/?id=3D298897
--=20
Keith
"new2sql" <anonymous@.discussions.microsoft.com> wrote in message =
news:E22BCD34-B235-420E-848E-9C2A63576020@.microsoft.com...
> What is the best document for restoring databases from one SQL 2000 =
server to a new SQL 2000 server?
Monday, February 13, 2012
Backup troubles
Hi,
I need some help with a logic for a important document I need to create. Its
regarding my Backup procedures that require me to test my database backups
every 3 months. The problem occurs that I do not have another server to test
out the database. So my solution was the following:
* Backup DB
* Restore DB redirected towards another DB
Now the problem is that QA doesnt think that is enough. I noticed that SQL
2005 (starting since SQL 2000) has this option which alot of 3rd party
Backup application use (my case backup exec 10d) "consistency check".
I am wondering if I set a consistency check at Backup and then at restore
with consistency check, could I absolutely prove that both databases are
EXACTLY the same.
Example using MD5 for comparing 2 files.
"Consistency check is the MD5 for the DB"
Thank you so much,
George S.
Hi
The restoration of the database will only prove that you can backup and
restore that backup i.e. the backup was not corrupted. It does not mean to
say that the restored database is the one that you backed up i.e. the backup
was not subsequently overwritten with a different backup. Therefore the issue
is one for protecting the backup and making sure it is not tampered with. A
checksum of the backup file may help, but then it doesn't mean that someone
has not tampered with where that is stored either!! If checking consistency
is the same as a DBCC CHECKDB it is not a comparison of the two databases.
HTH
John
"George Spiro" wrote:
> Hi,
> I need some help with a logic for a important document I need to create. Its
> regarding my Backup procedures that require me to test my database backups
> every 3 months. The problem occurs that I do not have another server to test
> out the database. So my solution was the following:
> * Backup DB
> * Restore DB redirected towards another DB
> Now the problem is that QA doesnt think that is enough. I noticed that SQL
> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> Backup application use (my case backup exec 10d) "consistency check".
> I am wondering if I set a consistency check at Backup and then at restore
> with consistency check, could I absolutely prove that both databases are
> EXACTLY the same.
> Example using MD5 for comparing 2 files.
> "Consistency check is the MD5 for the DB"
> Thank you so much,
> George S.
>
>
|||So what exactly is the Check consistency option on SQL 2000 / 2005?
G.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...[vbcol=seagreen]
> Hi
> The restoration of the database will only prove that you can backup and
> restore that backup i.e. the backup was not corrupted. It does not mean to
> say that the restored database is the one that you backed up i.e. the
> backup
> was not subsequently overwritten with a different backup. Therefore the
> issue
> is one for protecting the backup and making sure it is not tampered with.
> A
> checksum of the backup file may help, but then it doesn't mean that
> someone
> has not tampered with where that is stored either!! If checking
> consistency
> is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> HTH
> John
> "George Spiro" wrote:
|||Hi George
I don't use backup exec so I can not be sure, but the sales literature does
talk about performing DBCC commands, I don't think that it is anything that
will help you, although you may want to check with Symantic directly.
John
"George Spiro" wrote:
> So what exactly is the Check consistency option on SQL 2000 / 2005?
> G.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
>
>
I need some help with a logic for a important document I need to create. Its
regarding my Backup procedures that require me to test my database backups
every 3 months. The problem occurs that I do not have another server to test
out the database. So my solution was the following:
* Backup DB
* Restore DB redirected towards another DB
Now the problem is that QA doesnt think that is enough. I noticed that SQL
2005 (starting since SQL 2000) has this option which alot of 3rd party
Backup application use (my case backup exec 10d) "consistency check".
I am wondering if I set a consistency check at Backup and then at restore
with consistency check, could I absolutely prove that both databases are
EXACTLY the same.
Example using MD5 for comparing 2 files.
"Consistency check is the MD5 for the DB"
Thank you so much,
George S.
Hi
The restoration of the database will only prove that you can backup and
restore that backup i.e. the backup was not corrupted. It does not mean to
say that the restored database is the one that you backed up i.e. the backup
was not subsequently overwritten with a different backup. Therefore the issue
is one for protecting the backup and making sure it is not tampered with. A
checksum of the backup file may help, but then it doesn't mean that someone
has not tampered with where that is stored either!! If checking consistency
is the same as a DBCC CHECKDB it is not a comparison of the two databases.
HTH
John
"George Spiro" wrote:
> Hi,
> I need some help with a logic for a important document I need to create. Its
> regarding my Backup procedures that require me to test my database backups
> every 3 months. The problem occurs that I do not have another server to test
> out the database. So my solution was the following:
> * Backup DB
> * Restore DB redirected towards another DB
> Now the problem is that QA doesnt think that is enough. I noticed that SQL
> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> Backup application use (my case backup exec 10d) "consistency check".
> I am wondering if I set a consistency check at Backup and then at restore
> with consistency check, could I absolutely prove that both databases are
> EXACTLY the same.
> Example using MD5 for comparing 2 files.
> "Consistency check is the MD5 for the DB"
> Thank you so much,
> George S.
>
>
|||So what exactly is the Check consistency option on SQL 2000 / 2005?
G.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...[vbcol=seagreen]
> Hi
> The restoration of the database will only prove that you can backup and
> restore that backup i.e. the backup was not corrupted. It does not mean to
> say that the restored database is the one that you backed up i.e. the
> backup
> was not subsequently overwritten with a different backup. Therefore the
> issue
> is one for protecting the backup and making sure it is not tampered with.
> A
> checksum of the backup file may help, but then it doesn't mean that
> someone
> has not tampered with where that is stored either!! If checking
> consistency
> is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> HTH
> John
> "George Spiro" wrote:
|||Hi George
I don't use backup exec so I can not be sure, but the sales literature does
talk about performing DBCC commands, I don't think that it is anything that
will help you, although you may want to check with Symantic directly.
John
"George Spiro" wrote:
> So what exactly is the Check consistency option on SQL 2000 / 2005?
> G.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
>
>
Backup troubles
Hi,
I need some help with a logic for a important document I need to create. Its
regarding my Backup procedures that require me to test my database backups
every 3 months. The problem occurs that I do not have another server to test
out the database. So my solution was the following:
* Backup DB
* Restore DB redirected towards another DB
Now the problem is that QA doesnt think that is enough. I noticed that SQL
2005 (starting since SQL 2000) has this option which alot of 3rd party
Backup application use (my case backup exec 10d) "consistency check".
I am wondering if I set a consistency check at Backup and then at restore
with consistency check, could I absolutely prove that both databases are
EXACTLY the same.
Example using MD5 for comparing 2 files.
"Consistency check is the MD5 for the DB"
Thank you so much,
George S.Hi
The restoration of the database will only prove that you can backup and
restore that backup i.e. the backup was not corrupted. It does not mean to
say that the restored database is the one that you backed up i.e. the backup
was not subsequently overwritten with a different backup. Therefore the issue
is one for protecting the backup and making sure it is not tampered with. A
checksum of the backup file may help, but then it doesn't mean that someone
has not tampered with where that is stored either!! If checking consistency
is the same as a DBCC CHECKDB it is not a comparison of the two databases.
HTH
John
"George Spiro" wrote:
> Hi,
> I need some help with a logic for a important document I need to create. Its
> regarding my Backup procedures that require me to test my database backups
> every 3 months. The problem occurs that I do not have another server to test
> out the database. So my solution was the following:
> * Backup DB
> * Restore DB redirected towards another DB
> Now the problem is that QA doesnt think that is enough. I noticed that SQL
> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> Backup application use (my case backup exec 10d) "consistency check".
> I am wondering if I set a consistency check at Backup and then at restore
> with consistency check, could I absolutely prove that both databases are
> EXACTLY the same.
> Example using MD5 for comparing 2 files.
> "Consistency check is the MD5 for the DB"
> Thank you so much,
> George S.
>
>|||So what exactly is the Check consistency option on SQL 2000 / 2005?
G.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
> Hi
> The restoration of the database will only prove that you can backup and
> restore that backup i.e. the backup was not corrupted. It does not mean to
> say that the restored database is the one that you backed up i.e. the
> backup
> was not subsequently overwritten with a different backup. Therefore the
> issue
> is one for protecting the backup and making sure it is not tampered with.
> A
> checksum of the backup file may help, but then it doesn't mean that
> someone
> has not tampered with where that is stored either!! If checking
> consistency
> is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> HTH
> John
> "George Spiro" wrote:
>> Hi,
>> I need some help with a logic for a important document I need to create.
>> Its
>> regarding my Backup procedures that require me to test my database
>> backups
>> every 3 months. The problem occurs that I do not have another server to
>> test
>> out the database. So my solution was the following:
>> * Backup DB
>> * Restore DB redirected towards another DB
>> Now the problem is that QA doesnt think that is enough. I noticed that
>> SQL
>> 2005 (starting since SQL 2000) has this option which alot of 3rd party
>> Backup application use (my case backup exec 10d) "consistency check".
>> I am wondering if I set a consistency check at Backup and then at restore
>> with consistency check, could I absolutely prove that both databases are
>> EXACTLY the same.
>> Example using MD5 for comparing 2 files.
>> "Consistency check is the MD5 for the DB"
>> Thank you so much,
>> George S.
>>|||Hi George
I don't use backup exec so I can not be sure, but the sales literature does
talk about performing DBCC commands, I don't think that it is anything that
will help you, although you may want to check with Symantic directly.
John
"George Spiro" wrote:
> So what exactly is the Check consistency option on SQL 2000 / 2005?
> G.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
> > Hi
> >
> > The restoration of the database will only prove that you can backup and
> > restore that backup i.e. the backup was not corrupted. It does not mean to
> > say that the restored database is the one that you backed up i.e. the
> > backup
> > was not subsequently overwritten with a different backup. Therefore the
> > issue
> > is one for protecting the backup and making sure it is not tampered with.
> > A
> > checksum of the backup file may help, but then it doesn't mean that
> > someone
> > has not tampered with where that is stored either!! If checking
> > consistency
> > is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> >
> > HTH
> >
> > John
> >
> > "George Spiro" wrote:
> >
> >> Hi,
> >>
> >> I need some help with a logic for a important document I need to create.
> >> Its
> >> regarding my Backup procedures that require me to test my database
> >> backups
> >> every 3 months. The problem occurs that I do not have another server to
> >> test
> >> out the database. So my solution was the following:
> >>
> >> * Backup DB
> >> * Restore DB redirected towards another DB
> >>
> >> Now the problem is that QA doesnt think that is enough. I noticed that
> >> SQL
> >> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> >> Backup application use (my case backup exec 10d) "consistency check".
> >>
> >> I am wondering if I set a consistency check at Backup and then at restore
> >> with consistency check, could I absolutely prove that both databases are
> >> EXACTLY the same.
> >>
> >> Example using MD5 for comparing 2 files.
> >> "Consistency check is the MD5 for the DB"
> >>
> >> Thank you so much,
> >>
> >> George S.
> >>
> >>
> >>
>
>
I need some help with a logic for a important document I need to create. Its
regarding my Backup procedures that require me to test my database backups
every 3 months. The problem occurs that I do not have another server to test
out the database. So my solution was the following:
* Backup DB
* Restore DB redirected towards another DB
Now the problem is that QA doesnt think that is enough. I noticed that SQL
2005 (starting since SQL 2000) has this option which alot of 3rd party
Backup application use (my case backup exec 10d) "consistency check".
I am wondering if I set a consistency check at Backup and then at restore
with consistency check, could I absolutely prove that both databases are
EXACTLY the same.
Example using MD5 for comparing 2 files.
"Consistency check is the MD5 for the DB"
Thank you so much,
George S.Hi
The restoration of the database will only prove that you can backup and
restore that backup i.e. the backup was not corrupted. It does not mean to
say that the restored database is the one that you backed up i.e. the backup
was not subsequently overwritten with a different backup. Therefore the issue
is one for protecting the backup and making sure it is not tampered with. A
checksum of the backup file may help, but then it doesn't mean that someone
has not tampered with where that is stored either!! If checking consistency
is the same as a DBCC CHECKDB it is not a comparison of the two databases.
HTH
John
"George Spiro" wrote:
> Hi,
> I need some help with a logic for a important document I need to create. Its
> regarding my Backup procedures that require me to test my database backups
> every 3 months. The problem occurs that I do not have another server to test
> out the database. So my solution was the following:
> * Backup DB
> * Restore DB redirected towards another DB
> Now the problem is that QA doesnt think that is enough. I noticed that SQL
> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> Backup application use (my case backup exec 10d) "consistency check".
> I am wondering if I set a consistency check at Backup and then at restore
> with consistency check, could I absolutely prove that both databases are
> EXACTLY the same.
> Example using MD5 for comparing 2 files.
> "Consistency check is the MD5 for the DB"
> Thank you so much,
> George S.
>
>|||So what exactly is the Check consistency option on SQL 2000 / 2005?
G.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
> Hi
> The restoration of the database will only prove that you can backup and
> restore that backup i.e. the backup was not corrupted. It does not mean to
> say that the restored database is the one that you backed up i.e. the
> backup
> was not subsequently overwritten with a different backup. Therefore the
> issue
> is one for protecting the backup and making sure it is not tampered with.
> A
> checksum of the backup file may help, but then it doesn't mean that
> someone
> has not tampered with where that is stored either!! If checking
> consistency
> is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> HTH
> John
> "George Spiro" wrote:
>> Hi,
>> I need some help with a logic for a important document I need to create.
>> Its
>> regarding my Backup procedures that require me to test my database
>> backups
>> every 3 months. The problem occurs that I do not have another server to
>> test
>> out the database. So my solution was the following:
>> * Backup DB
>> * Restore DB redirected towards another DB
>> Now the problem is that QA doesnt think that is enough. I noticed that
>> SQL
>> 2005 (starting since SQL 2000) has this option which alot of 3rd party
>> Backup application use (my case backup exec 10d) "consistency check".
>> I am wondering if I set a consistency check at Backup and then at restore
>> with consistency check, could I absolutely prove that both databases are
>> EXACTLY the same.
>> Example using MD5 for comparing 2 files.
>> "Consistency check is the MD5 for the DB"
>> Thank you so much,
>> George S.
>>|||Hi George
I don't use backup exec so I can not be sure, but the sales literature does
talk about performing DBCC commands, I don't think that it is anything that
will help you, although you may want to check with Symantic directly.
John
"George Spiro" wrote:
> So what exactly is the Check consistency option on SQL 2000 / 2005?
> G.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
> > Hi
> >
> > The restoration of the database will only prove that you can backup and
> > restore that backup i.e. the backup was not corrupted. It does not mean to
> > say that the restored database is the one that you backed up i.e. the
> > backup
> > was not subsequently overwritten with a different backup. Therefore the
> > issue
> > is one for protecting the backup and making sure it is not tampered with.
> > A
> > checksum of the backup file may help, but then it doesn't mean that
> > someone
> > has not tampered with where that is stored either!! If checking
> > consistency
> > is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> >
> > HTH
> >
> > John
> >
> > "George Spiro" wrote:
> >
> >> Hi,
> >>
> >> I need some help with a logic for a important document I need to create.
> >> Its
> >> regarding my Backup procedures that require me to test my database
> >> backups
> >> every 3 months. The problem occurs that I do not have another server to
> >> test
> >> out the database. So my solution was the following:
> >>
> >> * Backup DB
> >> * Restore DB redirected towards another DB
> >>
> >> Now the problem is that QA doesnt think that is enough. I noticed that
> >> SQL
> >> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> >> Backup application use (my case backup exec 10d) "consistency check".
> >>
> >> I am wondering if I set a consistency check at Backup and then at restore
> >> with consistency check, could I absolutely prove that both databases are
> >> EXACTLY the same.
> >>
> >> Example using MD5 for comparing 2 files.
> >> "Consistency check is the MD5 for the DB"
> >>
> >> Thank you so much,
> >>
> >> George S.
> >>
> >>
> >>
>
>
Backup troubles
Hi,
I need some help with a logic for a important document I need to create. Its
regarding my Backup procedures that require me to test my database backups
every 3 months. The problem occurs that I do not have another server to test
out the database. So my solution was the following:
* Backup DB
* Restore DB redirected towards another DB
Now the problem is that QA doesnt think that is enough. I noticed that SQL
2005 (starting since SQL 2000) has this option which alot of 3rd party
Backup application use (my case backup exec 10d) "consistency check".
I am wondering if I set a consistency check at Backup and then at restore
with consistency check, could I absolutely prove that both databases are
EXACTLY the same.
Example using MD5 for comparing 2 files.
"Consistency check is the MD5 for the DB"
Thank you so much,
George S.
Hi
The restoration of the database will only prove that you can backup and
restore that backup i.e. the backup was not corrupted. It does not mean to
say that the restored database is the one that you backed up i.e. the backup
was not subsequently overwritten with a different backup. Therefore the issue
is one for protecting the backup and making sure it is not tampered with. A
checksum of the backup file may help, but then it doesn't mean that someone
has not tampered with where that is stored either!! If checking consistency
is the same as a DBCC CHECKDB it is not a comparison of the two databases.
HTH
John
"George Spiro" wrote:
> Hi,
> I need some help with a logic for a important document I need to create. Its
> regarding my Backup procedures that require me to test my database backups
> every 3 months. The problem occurs that I do not have another server to test
> out the database. So my solution was the following:
> * Backup DB
> * Restore DB redirected towards another DB
> Now the problem is that QA doesnt think that is enough. I noticed that SQL
> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> Backup application use (my case backup exec 10d) "consistency check".
> I am wondering if I set a consistency check at Backup and then at restore
> with consistency check, could I absolutely prove that both databases are
> EXACTLY the same.
> Example using MD5 for comparing 2 files.
> "Consistency check is the MD5 for the DB"
> Thank you so much,
> George S.
>
>
|||So what exactly is the Check consistency option on SQL 2000 / 2005?
G.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...[vbcol=seagreen]
> Hi
> The restoration of the database will only prove that you can backup and
> restore that backup i.e. the backup was not corrupted. It does not mean to
> say that the restored database is the one that you backed up i.e. the
> backup
> was not subsequently overwritten with a different backup. Therefore the
> issue
> is one for protecting the backup and making sure it is not tampered with.
> A
> checksum of the backup file may help, but then it doesn't mean that
> someone
> has not tampered with where that is stored either!! If checking
> consistency
> is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> HTH
> John
> "George Spiro" wrote:
|||Hi George
I don't use backup exec so I can not be sure, but the sales literature does
talk about performing DBCC commands, I don't think that it is anything that
will help you, although you may want to check with Symantic directly.
John
"George Spiro" wrote:
> So what exactly is the Check consistency option on SQL 2000 / 2005?
> G.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
>
>
I need some help with a logic for a important document I need to create. Its
regarding my Backup procedures that require me to test my database backups
every 3 months. The problem occurs that I do not have another server to test
out the database. So my solution was the following:
* Backup DB
* Restore DB redirected towards another DB
Now the problem is that QA doesnt think that is enough. I noticed that SQL
2005 (starting since SQL 2000) has this option which alot of 3rd party
Backup application use (my case backup exec 10d) "consistency check".
I am wondering if I set a consistency check at Backup and then at restore
with consistency check, could I absolutely prove that both databases are
EXACTLY the same.
Example using MD5 for comparing 2 files.
"Consistency check is the MD5 for the DB"
Thank you so much,
George S.
Hi
The restoration of the database will only prove that you can backup and
restore that backup i.e. the backup was not corrupted. It does not mean to
say that the restored database is the one that you backed up i.e. the backup
was not subsequently overwritten with a different backup. Therefore the issue
is one for protecting the backup and making sure it is not tampered with. A
checksum of the backup file may help, but then it doesn't mean that someone
has not tampered with where that is stored either!! If checking consistency
is the same as a DBCC CHECKDB it is not a comparison of the two databases.
HTH
John
"George Spiro" wrote:
> Hi,
> I need some help with a logic for a important document I need to create. Its
> regarding my Backup procedures that require me to test my database backups
> every 3 months. The problem occurs that I do not have another server to test
> out the database. So my solution was the following:
> * Backup DB
> * Restore DB redirected towards another DB
> Now the problem is that QA doesnt think that is enough. I noticed that SQL
> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> Backup application use (my case backup exec 10d) "consistency check".
> I am wondering if I set a consistency check at Backup and then at restore
> with consistency check, could I absolutely prove that both databases are
> EXACTLY the same.
> Example using MD5 for comparing 2 files.
> "Consistency check is the MD5 for the DB"
> Thank you so much,
> George S.
>
>
|||So what exactly is the Check consistency option on SQL 2000 / 2005?
G.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...[vbcol=seagreen]
> Hi
> The restoration of the database will only prove that you can backup and
> restore that backup i.e. the backup was not corrupted. It does not mean to
> say that the restored database is the one that you backed up i.e. the
> backup
> was not subsequently overwritten with a different backup. Therefore the
> issue
> is one for protecting the backup and making sure it is not tampered with.
> A
> checksum of the backup file may help, but then it doesn't mean that
> someone
> has not tampered with where that is stored either!! If checking
> consistency
> is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> HTH
> John
> "George Spiro" wrote:
|||Hi George
I don't use backup exec so I can not be sure, but the sales literature does
talk about performing DBCC commands, I don't think that it is anything that
will help you, although you may want to check with Symantic directly.
John
"George Spiro" wrote:
> So what exactly is the Check consistency option on SQL 2000 / 2005?
> G.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
>
>
Backup troubles
Hi,
I need some help with a logic for a important document I need to create. Its
regarding my Backup procedures that require me to test my database backups
every 3 months. The problem occurs that I do not have another server to test
out the database. So my solution was the following:
* Backup DB
* Restore DB redirected towards another DB
Now the problem is that QA doesnt think that is enough. I noticed that SQL
2005 (starting since SQL 2000) has this option which alot of 3rd party
Backup application use (my case backup exec 10d) "consistency check".
I am wondering if I set a consistency check at Backup and then at restore
with consistency check, could I absolutely prove that both databases are
EXACTLY the same.
Example using MD5 for comparing 2 files.
"Consistency check is the MD5 for the DB"
Thank you so much,
George S.Hi
The restoration of the database will only prove that you can backup and
restore that backup i.e. the backup was not corrupted. It does not mean to
say that the restored database is the one that you backed up i.e. the backup
was not subsequently overwritten with a different backup. Therefore the issu
e
is one for protecting the backup and making sure it is not tampered with. A
checksum of the backup file may help, but then it doesn't mean that someone
has not tampered with where that is stored either!! If checking consistency
is the same as a DBCC CHECKDB it is not a comparison of the two databases.
HTH
John
"George Spiro" wrote:
> Hi,
> I need some help with a logic for a important document I need to create. I
ts
> regarding my Backup procedures that require me to test my database backups
> every 3 months. The problem occurs that I do not have another server to te
st
> out the database. So my solution was the following:
> * Backup DB
> * Restore DB redirected towards another DB
> Now the problem is that QA doesnt think that is enough. I noticed that SQL
> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> Backup application use (my case backup exec 10d) "consistency check".
> I am wondering if I set a consistency check at Backup and then at restore
> with consistency check, could I absolutely prove that both databases are
> EXACTLY the same.
> Example using MD5 for comparing 2 files.
> "Consistency check is the MD5 for the DB"
> Thank you so much,
> George S.
>
>|||So what exactly is the Check consistency option on SQL 2000 / 2005?
G.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...[vbcol=seagreen]
> Hi
> The restoration of the database will only prove that you can backup and
> restore that backup i.e. the backup was not corrupted. It does not mean to
> say that the restored database is the one that you backed up i.e. the
> backup
> was not subsequently overwritten with a different backup. Therefore the
> issue
> is one for protecting the backup and making sure it is not tampered with.
> A
> checksum of the backup file may help, but then it doesn't mean that
> someone
> has not tampered with where that is stored either!! If checking
> consistency
> is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> HTH
> John
> "George Spiro" wrote:
>|||Hi George
I don't use backup exec so I can not be sure, but the sales literature does
talk about performing DBCC commands, I don't think that it is anything that
will help you, although you may want to check with Symantic directly.
John
"George Spiro" wrote:
> So what exactly is the Check consistency option on SQL 2000 / 2005?
> G.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
>
>
I need some help with a logic for a important document I need to create. Its
regarding my Backup procedures that require me to test my database backups
every 3 months. The problem occurs that I do not have another server to test
out the database. So my solution was the following:
* Backup DB
* Restore DB redirected towards another DB
Now the problem is that QA doesnt think that is enough. I noticed that SQL
2005 (starting since SQL 2000) has this option which alot of 3rd party
Backup application use (my case backup exec 10d) "consistency check".
I am wondering if I set a consistency check at Backup and then at restore
with consistency check, could I absolutely prove that both databases are
EXACTLY the same.
Example using MD5 for comparing 2 files.
"Consistency check is the MD5 for the DB"
Thank you so much,
George S.Hi
The restoration of the database will only prove that you can backup and
restore that backup i.e. the backup was not corrupted. It does not mean to
say that the restored database is the one that you backed up i.e. the backup
was not subsequently overwritten with a different backup. Therefore the issu
e
is one for protecting the backup and making sure it is not tampered with. A
checksum of the backup file may help, but then it doesn't mean that someone
has not tampered with where that is stored either!! If checking consistency
is the same as a DBCC CHECKDB it is not a comparison of the two databases.
HTH
John
"George Spiro" wrote:
> Hi,
> I need some help with a logic for a important document I need to create. I
ts
> regarding my Backup procedures that require me to test my database backups
> every 3 months. The problem occurs that I do not have another server to te
st
> out the database. So my solution was the following:
> * Backup DB
> * Restore DB redirected towards another DB
> Now the problem is that QA doesnt think that is enough. I noticed that SQL
> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> Backup application use (my case backup exec 10d) "consistency check".
> I am wondering if I set a consistency check at Backup and then at restore
> with consistency check, could I absolutely prove that both databases are
> EXACTLY the same.
> Example using MD5 for comparing 2 files.
> "Consistency check is the MD5 for the DB"
> Thank you so much,
> George S.
>
>|||So what exactly is the Check consistency option on SQL 2000 / 2005?
G.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...[vbcol=seagreen]
> Hi
> The restoration of the database will only prove that you can backup and
> restore that backup i.e. the backup was not corrupted. It does not mean to
> say that the restored database is the one that you backed up i.e. the
> backup
> was not subsequently overwritten with a different backup. Therefore the
> issue
> is one for protecting the backup and making sure it is not tampered with.
> A
> checksum of the backup file may help, but then it doesn't mean that
> someone
> has not tampered with where that is stored either!! If checking
> consistency
> is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> HTH
> John
> "George Spiro" wrote:
>|||Hi George
I don't use backup exec so I can not be sure, but the sales literature does
talk about performing DBCC commands, I don't think that it is anything that
will help you, although you may want to check with Symantic directly.
John
"George Spiro" wrote:
> So what exactly is the Check consistency option on SQL 2000 / 2005?
> G.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
>
>
Subscribe to:
Posts (Atom)