Recataloging a log backup disk file

Backup Log DataBaseName to
DISK='\\ServerName\ShareName\Path\FileName.TRN' with
RetainDays=1, Description='Daily Backup Routine'
When I restore a database and logs to an alternate
server, I can restore the full database backup and the
first iteration of the log backups without any problems.
The problem is with all subsequent log backups that were
performed and apended to the file created by the above
statement. I know and can get to the subsequent appended
logs via TSQL, but not an easy task if there are 15
appended log backups on the device. Is there a way I can
recatalog all the log backups so I can use Enterprise
Manager's point an click interface to restore? Will the
STOPAT parameter restore the first log backup, and all
subsequent backups, up to the STOPAT? The command used
to create the log backup is stated above.
Thanx soo much for your help,
D2David,
> Is there a way I can
> recatalog all the log backups so I can use Enterprise
> Manager's point an click interface to restore?
Not easily. I guess you can write a TSQL script that uses RESTORE HEADERONLY and based on that
inserts data into the backup history tables in msdb. Note that *this is not supported*! EM has an
option to generate backuphistory as you select a backup device in the restore dialog, but that isn't
dine on a file basis, but on a backup basis, so using EM to generate backuphistory, you would have
to go through that dialog 15 times.
> Will the
> STOPAT parameter restore the first log backup, and all
> subsequent backups, up to the STOPAT?
No. All RESTORE commands only addresses one backup at a time.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Danh" <anonymous@.discussions.microsoft.com> wrote in message
news:370101c4a05d$53fc68b0$a501280a@.phx.gbl...
> Backup Log DataBaseName to
> DISK='\\ServerName\ShareName\Path\FileName.TRN' with
> RetainDays=1, Description='Daily Backup Routine'
> When I restore a database and logs to an alternate
> server, I can restore the full database backup and the
> first iteration of the log backups without any problems.
> The problem is with all subsequent log backups that were
> performed and apended to the file created by the above
> statement. I know and can get to the subsequent appended
> logs via TSQL, but not an easy task if there are 15
> appended log backups on the device. Is there a way I can
> recatalog all the log backups so I can use Enterprise
> Manager's point an click interface to restore? Will the
> STOPAT parameter restore the first log backup, and all
> subsequent backups, up to the STOPAT? The command used
> to create the log backup is stated above.
> Thanx soo much for your help,
> D2
>|||Thanks for the help... I ended up doing this...
RESTORE VERIFYONLY FROM DISK='FilePath' WITH
FILE=#,LOADHISTORY
Replaced the # with 1 2 3 4 5 6 7 ...
I just wish it can be done with one command.
>--Original Message--
>David,
>> Is there a way I can
>> recatalog all the log backups so I can use Enterprise
>> Manager's point an click interface to restore?
>Not easily. I guess you can write a TSQL script that
uses RESTORE HEADERONLY and based on that
>inserts data into the backup history tables in msdb.
Note that *this is not supported*! EM has an
>option to generate backuphistory as you select a backup
device in the restore dialog, but that isn't
>dine on a file basis, but on a backup basis, so using EM
to generate backuphistory, you would have
>to go through that dialog 15 times.
>> Will the
>> STOPAT parameter restore the first log backup, and all
>> subsequent backups, up to the STOPAT?
>No. All RESTORE commands only addresses one backup at a
time.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
>"David Danh" <anonymous@.discussions.microsoft.com> wrote
in message
>news:370101c4a05d$53fc68b0$a501280a@.phx.gbl...
>> Backup Log DataBaseName to
>> DISK='\\ServerName\ShareName\Path\FileName.TRN' with
>> RetainDays=1, Description='Daily Backup Routine'
>> When I restore a database and logs to an alternate
>> server, I can restore the full database backup and the
>> first iteration of the log backups without any
problems.
>> The problem is with all subsequent log backups that
were
>> performed and apended to the file created by the above
>> statement. I know and can get to the subsequent
appended
>> logs via TSQL, but not an easy task if there are 15
>> appended log backups on the device. Is there a way I
can
>> recatalog all the log backups so I can use Enterprise
>> Manager's point an click interface to restore? Will
the
>> STOPAT parameter restore the first log backup, and all
>> subsequent backups, up to the STOPAT? The command used
>> to create the log backup is stated above.
>> Thanx soo much for your help,
>> D2
>
>.
>

Rebuild SQL server 7 db

Our NT 4.0 server machine's motherboard burned out. After placed the hard
disk drives in a new box, we got a video issue and disk I/O error. Therefore
I installed SQL server 7 on a new Win2K server box. The hard disk drives on
the NT server are fine and placed in the new box. I can't use detach or
attach sp from the new box. How can I restore the db to the new box?
Thanks,
Eli
>> I can't use detach or attach sp from the new box.
You mean, you are getting some errors while trying to attach the databases?
If so, what are they?
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:uVLY7pbkFHA.2444@.tk2msftngp13.phx.gbl...
Our NT 4.0 server machine's motherboard burned out. After placed the hard
disk drives in a new box, we got a video issue and disk I/O error. Therefore
I installed SQL server 7 on a new Win2K server box. The hard disk drives on
the NT server are fine and placed in the new box. I can't use detach or
attach sp from the new box. How can I restore the db to the new box?
Thanks,
Eli
|||Hi,
If you have all the physical files (MDF, NDF and LDF) belongs to SYSTEM and
User databases then you can do below:-
1. Install SQL Server 7 in the same folder as old installation
2. Apply the same service pack as old
3. Stop SQL Server service
4. COpy the new physical files to a new folder
5. Copy the physical files (MDF, NDF and LDF) from the old server to the
exact folders as old
6. Start the SQL Server service
7. Open enterprise manager and see if all the databases are ok.
Incase if this step fails then you need to:-
Restore the databases from last good backup.
Thanks
Hari
SQL Server MVP
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:uVLY7pbkFHA.2444@.tk2msftngp13.phx.gbl...
> Our NT 4.0 server machine's motherboard burned out. After placed the hard
> disk drives in a new box, we got a video issue and disk I/O error.
> Therefore
> I installed SQL server 7 on a new Win2K server box. The hard disk drives
> on
> the NT server are fine and placed in the new box. I can't use detach or
> attach sp from the new box. How can I restore the db to the new box?
> Thanks,
> Eli
>
|||Hi Narayana & Hai,
Thank you so much for your replies. Because the db was not normally
detached, therefore I didn't know how to attach it to a new SQL serverl.
I'll try Hai's instructions to see how it works. Thanks again, really
apreciate it.
Eli
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ursSf8gkFHA.3828@.TK2MSFTNGP12.phx.gbl...
> Hi,
> If you have all the physical files (MDF, NDF and LDF) belongs to SYSTEM
and[vbcol=seagreen]
> User databases then you can do below:-
> 1. Install SQL Server 7 in the same folder as old installation
> 2. Apply the same service pack as old
> 3. Stop SQL Server service
> 4. COpy the new physical files to a new folder
> 5. Copy the physical files (MDF, NDF and LDF) from the old server to the
> exact folders as old
> 6. Start the SQL Server service
> 7. Open enterprise manager and see if all the databases are ok.
> Incase if this step fails then you need to:-
> Restore the databases from last good backup.
> Thanks
> Hari
> SQL Server MVP
>
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:uVLY7pbkFHA.2444@.tk2msftngp13.phx.gbl...
hard
>

Rebuild SQL server 7 db

Our NT 4.0 server machine's motherboard burned out. After placed the hard
disk drives in a new box, we got a video issue and disk I/O error. Therefore
I installed SQL server 7 on a new Win2K server box. The hard disk drives on
the NT server are fine and placed in the new box. I can't use detach or
attach sp from the new box. How can I restore the db to the new box?
Thanks,
Eli>> I can't use detach or attach sp from the new box.
You mean, you are getting some errors while trying to attach the databases?
If so, what are they?
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:uVLY7pbkFHA.2444@.tk2msftngp13.phx.gbl...
Our NT 4.0 server machine's motherboard burned out. After placed the hard
disk drives in a new box, we got a video issue and disk I/O error. Therefore
I installed SQL server 7 on a new Win2K server box. The hard disk drives on
the NT server are fine and placed in the new box. I can't use detach or
attach sp from the new box. How can I restore the db to the new box?
Thanks,
Eli|||Hi,
If you have all the physical files (MDF, NDF and LDF) belongs to SYSTEM and
User databases then you can do below:-
1. Install SQL Server 7 in the same folder as old installation
2. Apply the same service pack as old
3. Stop SQL Server service
4. COpy the new physical files to a new folder
5. Copy the physical files (MDF, NDF and LDF) from the old server to the
exact folders as old
6. Start the SQL Server service
7. Open enterprise manager and see if all the databases are ok.
Incase if this step fails then you need to:-
Restore the databases from last good backup.
Thanks
Hari
SQL Server MVP
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:uVLY7pbkFHA.2444@.tk2msftngp13.phx.gbl...
> Our NT 4.0 server machine's motherboard burned out. After placed the hard
> disk drives in a new box, we got a video issue and disk I/O error.
> Therefore
> I installed SQL server 7 on a new Win2K server box. The hard disk drives
> on
> the NT server are fine and placed in the new box. I can't use detach or
> attach sp from the new box. How can I restore the db to the new box?
> Thanks,
> Eli
>|||Hi Narayana & Hai,
Thank you so much for your replies. Because the db was not normally
detached, therefore I didn't know how to attach it to a new SQL serverl.
I'll try Hai's instructions to see how it works. Thanks again, really
apreciate it.
Eli
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ursSf8gkFHA.3828@.TK2MSFTNGP12.phx.gbl...
> Hi,
> If you have all the physical files (MDF, NDF and LDF) belongs to SYSTEM
and
> User databases then you can do below:-
> 1. Install SQL Server 7 in the same folder as old installation
> 2. Apply the same service pack as old
> 3. Stop SQL Server service
> 4. COpy the new physical files to a new folder
> 5. Copy the physical files (MDF, NDF and LDF) from the old server to the
> exact folders as old
> 6. Start the SQL Server service
> 7. Open enterprise manager and see if all the databases are ok.
> Incase if this step fails then you need to:-
> Restore the databases from last good backup.
> Thanks
> Hari
> SQL Server MVP
>
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:uVLY7pbkFHA.2444@.tk2msftngp13.phx.gbl...
> > Our NT 4.0 server machine's motherboard burned out. After placed the
hard
> > disk drives in a new box, we got a video issue and disk I/O error.
> > Therefore
> > I installed SQL server 7 on a new Win2K server box. The hard disk drives
> > on
> > the NT server are fine and placed in the new box. I can't use detach or
> > attach sp from the new box. How can I restore the db to the new box?
> > Thanks,
> > Eli
> >
> >
>

Rebuild SQL server 7 db

Our NT 4.0 server machine's motherboard burned out. After placed the hard
disk drives in a new box, we got a video issue and disk I/O error. Therefore
I installed SQL server 7 on a new Win2K server box. The hard disk drives on
the NT server are fine and placed in the new box. I can't use detach or
attach sp from the new box. How can I restore the db to the new box?
Thanks,
Eli>> I can't use detach or attach sp from the new box.
You mean, you are getting some errors while trying to attach the databases?
If so, what are they?
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:uVLY7pbkFHA.2444@.tk2msftngp13.phx.gbl...
Our NT 4.0 server machine's motherboard burned out. After placed the hard
disk drives in a new box, we got a video issue and disk I/O error. Therefore
I installed SQL server 7 on a new Win2K server box. The hard disk drives on
the NT server are fine and placed in the new box. I can't use detach or
attach sp from the new box. How can I restore the db to the new box?
Thanks,
Eli|||Hi,
If you have all the physical files (MDF, NDF and LDF) belongs to SYSTEM and
User databases then you can do below:-
1. Install SQL Server 7 in the same folder as old installation
2. Apply the same service pack as old
3. Stop SQL Server service
4. COpy the new physical files to a new folder
5. Copy the physical files (MDF, NDF and LDF) from the old server to the
exact folders as old
6. Start the SQL Server service
7. Open enterprise manager and see if all the databases are ok.
Incase if this step fails then you need to:-
Restore the databases from last good backup.
Thanks
Hari
SQL Server MVP
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:uVLY7pbkFHA.2444@.tk2msftngp13.phx.gbl...
> Our NT 4.0 server machine's motherboard burned out. After placed the hard
> disk drives in a new box, we got a video issue and disk I/O error.
> Therefore
> I installed SQL server 7 on a new Win2K server box. The hard disk drives
> on
> the NT server are fine and placed in the new box. I can't use detach or
> attach sp from the new box. How can I restore the db to the new box?
> Thanks,
> Eli
>|||Hi Narayana & Hai,
Thank you so much for your replies. Because the db was not normally
detached, therefore I didn't know how to attach it to a new SQL serverl.
I'll try Hai's instructions to see how it works. Thanks again, really
apreciate it.
Eli
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ursSf8gkFHA.3828@.TK2MSFTNGP12.phx.gbl...
> Hi,
> If you have all the physical files (MDF, NDF and LDF) belongs to SYSTEM
and
> User databases then you can do below:-
> 1. Install SQL Server 7 in the same folder as old installation
> 2. Apply the same service pack as old
> 3. Stop SQL Server service
> 4. COpy the new physical files to a new folder
> 5. Copy the physical files (MDF, NDF and LDF) from the old server to the
> exact folders as old
> 6. Start the SQL Server service
> 7. Open enterprise manager and see if all the databases are ok.
> Incase if this step fails then you need to:-
> Restore the databases from last good backup.
> Thanks
> Hari
> SQL Server MVP
>
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:uVLY7pbkFHA.2444@.tk2msftngp13.phx.gbl...
hard[vbcol=seagreen]
>sql

Rebuild of SQL Server

With the initial system DISK configuration now running out of space, it will
be necessary to reconfigure the disk structure - with a reload of Win2k and
SQL 2000.
Question: Prior to the server rebuild, if SQL is stopped and system/user d
atabase device files are copied to tape, after the rebuild of the server (sa
me name) and a reload of SQL 2000 to same drive, would it possible to stop S
QL and copy the same databa
se device files from tape to avoid a SQL restore of the databases. This woul
d save some time and effort in recreating the databases from scratch, includ
ing the master database.
Thanks in Advance for any advice.Hi,
Yes, You can do that and it will be the faster and easy methodology. But
ensure that you have the same service pack in new server as well.
Thanks
Hari
MCDBA
Thanks
Hari
MCDBA
"Greg H" <anonymous@.discussions.microsoft.com> wrote in message
news:F5F90AF5-EA63-4192-BEB5-E4238C2A624F@.microsoft.com...
> With the initial system DISK configuration now running out of space, it
will be necessary to reconfigure the disk structure - with a reload of Win2k
and SQL 2000.
> Question: Prior to the server rebuild, if SQL is stopped and system/user
database device files are copied to tape, after the rebuild of the server
(same name) and a reload of SQL 2000 to same drive, would it possible to
stop SQL and copy the same database device files from tape to avoid a SQL
restore of the databases. This would save some time and effort in recreating
the databases from scratch, including the master database.
> Thanks in Advance for any advice.|||Provided all the path namews for location of master, model, tempdb etc =
and the user databses are the same, same service pack levels etc then I =
be;leive this should be OK. I would still test it though.=20
Being paranoid I would take at least 2 tape copies. And if possible =
restore to new disks BEFORE ditching the old ones.
But do you really ned to reinstall win2k to make the disk changes.?
Mike John
"Greg H" <anonymous@.discussions.microsoft.com> wrote in message =
news:F5F90AF5-EA63-4192-BEB5-E4238C2A624F@.microsoft.com...
> With the initial system DISK configuration now running out of space, =
it will be necessary to reconfigure the disk structure - with a reload =
of Win2k and SQL 2000. =20
> Question: Prior to the server rebuild, if SQL is stopped and =
system/user database device files are copied to tape, after the rebuild =
of the server (same name) and a reload of SQL 2000 to same drive, would =
it possible to stop SQL and copy the same database device files from =
tape to avoid a SQL restore of the databases. This would save some time =
and effort in recreating the databases from scratch, including the =
master database.
>=20
> Thanks in Advance for any advice.

Rebuild database in a SQL server

Hello,
Had a system failure and the disk volume, where all
databases were resided on, was gone.
SQL application is on a different disk volume, and there
is BAK copy for master, msdb and a user database.
Who can share his/her experience or lead me to tech info
links to rebuild the database?
Thanks in advance.
EricYou might want to pay the $250.00 or so for tech support to walk you thru
this:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
But here are some links that may help along with the BooksOnLine help file:
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
Andrew J. Kelly
SQL Server MVP
"Eric Chen" <eric.chen@.broadvision.com> wrote in message
news:2b4301c33f56$c01fe940$a401280a@.phx.gbl...
> Hello,
> Had a system failure and the disk volume, where all
> databases were resided on, was gone.
> SQL application is on a different disk volume, and there
> is BAK copy for master, msdb and a user database.
> Who can share his/her experience or lead me to tech info
> links to rebuild the database?
> Thanks in advance.
> Eric
>