Restore database...schedule

SQL Server Enterprise Edition
Microsoft Windows NT - 5.2 (3790)
Product version 8.00.760 (SP3)
1. I am moving two databases to different location (Both ldf and mdf files
because of size) on the same server. Can I automate the process and schedule
to run it at midnight. When I try to create a restore task using enterprise
manager it does not give me a option to schedule the task.
2. While performing same task(restore), few services on another server (Non
sql server) needs to be stopped, once restore is complete needs to be started
again. How to automate (start and stop services).
--
ontario, canadaProbably better to detach the database(s), move the files, thn re-attach
Check out sp_detach_db and sp_attach_db in Books Online. You can write a
few simple T-SQL statements and schedule these as a SQL job for the Agent to
run
Step 1 - sp_detach...etc.
Step 2 - xp_cmdshell 'copy the files...'
Step 3 - sp_attach_db
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"db" <db@.discussions.microsoft.com> wrote in message
news:63CA1294-582D-47BF-9508-65E44EDF74C6@.microsoft.com...
> SQL Server Enterprise Edition
> Microsoft Windows NT - 5.2 (3790)
> Product version 8.00.760 (SP3)
> 1. I am moving two databases to different location (Both ldf and mdf files
> because of size) on the same server. Can I automate the process and
> schedule
> to run it at midnight. When I try to create a restore task using
> enterprise
> manager it does not give me a option to schedule the task.
> 2. While performing same task(restore), few services on another server
> (Non
> sql server) needs to be stopped, once restore is complete needs to be
> started
> again. How to automate (start and stop services).
> --
> ontario, canada|||Can I schedule database restore. I have schedules non sql services to stop
at desired time.
--
ontario, canada
"Kevin3NF" wrote:
> Probably better to detach the database(s), move the files, thn re-attach
> Check out sp_detach_db and sp_attach_db in Books Online. You can write a
> few simple T-SQL statements and schedule these as a SQL job for the Agent to
> run
> Step 1 - sp_detach...etc.
> Step 2 - xp_cmdshell 'copy the files...'
> Step 3 - sp_attach_db
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "db" <db@.discussions.microsoft.com> wrote in message
> news:63CA1294-582D-47BF-9508-65E44EDF74C6@.microsoft.com...
> >
> > SQL Server Enterprise Edition
> > Microsoft Windows NT - 5.2 (3790)
> > Product version 8.00.760 (SP3)
> >
> > 1. I am moving two databases to different location (Both ldf and mdf files
> > because of size) on the same server. Can I automate the process and
> > schedule
> > to run it at midnight. When I try to create a restore task using
> > enterprise
> > manager it does not give me a option to schedule the task.
> >
> > 2. While performing same task(restore), few services on another server
> > (Non
> > sql server) needs to be stopped, once restore is complete needs to be
> > started
> > again. How to automate (start and stop services).
> > --
> > ontario, canada
>
>|||You can. Create a job with a RESTORE Database statement in it...
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"db" <db@.discussions.microsoft.com> wrote in message
news:4B5A046B-5A3F-4FB7-8FED-D4319B59DF81@.microsoft.com...
> Can I schedule database restore. I have schedules non sql services to
> stop
> at desired time.
> --
> ontario, canada
>
> "Kevin3NF" wrote:
>> Probably better to detach the database(s), move the files, thn re-attach
>> Check out sp_detach_db and sp_attach_db in Books Online. You can write a
>> few simple T-SQL statements and schedule these as a SQL job for the Agent
>> to
>> run
>> Step 1 - sp_detach...etc.
>> Step 2 - xp_cmdshell 'copy the files...'
>> Step 3 - sp_attach_db
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "db" <db@.discussions.microsoft.com> wrote in message
>> news:63CA1294-582D-47BF-9508-65E44EDF74C6@.microsoft.com...
>> >
>> > SQL Server Enterprise Edition
>> > Microsoft Windows NT - 5.2 (3790)
>> > Product version 8.00.760 (SP3)
>> >
>> > 1. I am moving two databases to different location (Both ldf and mdf
>> > files
>> > because of size) on the same server. Can I automate the process and
>> > schedule
>> > to run it at midnight. When I try to create a restore task using
>> > enterprise
>> > manager it does not give me a option to schedule the task.
>> >
>> > 2. While performing same task(restore), few services on another server
>> > (Non
>> > sql server) needs to be stopped, once restore is complete needs to be
>> > started
>> > again. How to automate (start and stop services).
>> > --
>> > ontario, canada
>>

Restore database...schedule

SQL Server Enterprise Edition
Microsoft Windows NT - 5.2 (3790)
Product version 8.00.760 (SP3)
1. I am moving two databases to different location (Both ldf and mdf files
because of size) on the same server. Can I automate the process and schedule
to run it at midnight. When I try to create a restore task using enterprise
manager it does not give me a option to schedule the task.
2. While performing same task(restore), few services on another server (Non
sql server) needs to be stopped, once restore is complete needs to be started
again. How to automate (start and stop services).
ontario, canada
Probably better to detach the database(s), move the files, thn re-attach
Check out sp_detach_db and sp_attach_db in Books Online. You can write a
few simple T-SQL statements and schedule these as a SQL job for the Agent to
run
Step 1 - sp_detach...etc.
Step 2 - xp_cmdshell 'copy the files...'
Step 3 - sp_attach_db
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"db" <db@.discussions.microsoft.com> wrote in message
news:63CA1294-582D-47BF-9508-65E44EDF74C6@.microsoft.com...
> SQL Server Enterprise Edition
> Microsoft Windows NT - 5.2 (3790)
> Product version 8.00.760 (SP3)
> 1. I am moving two databases to different location (Both ldf and mdf files
> because of size) on the same server. Can I automate the process and
> schedule
> to run it at midnight. When I try to create a restore task using
> enterprise
> manager it does not give me a option to schedule the task.
> 2. While performing same task(restore), few services on another server
> (Non
> sql server) needs to be stopped, once restore is complete needs to be
> started
> again. How to automate (start and stop services).
> --
> ontario, canada
|||Can I schedule database restore. I have schedules non sql services to stop
at desired time.
ontario, canada
"Kevin3NF" wrote:

> Probably better to detach the database(s), move the files, thn re-attach
> Check out sp_detach_db and sp_attach_db in Books Online. You can write a
> few simple T-SQL statements and schedule these as a SQL job for the Agent to
> run
> Step 1 - sp_detach...etc.
> Step 2 - xp_cmdshell 'copy the files...'
> Step 3 - sp_attach_db
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "db" <db@.discussions.microsoft.com> wrote in message
> news:63CA1294-582D-47BF-9508-65E44EDF74C6@.microsoft.com...
>
>
|||You can. Create a job with a RESTORE Database statement in it...
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"db" <db@.discussions.microsoft.com> wrote in message
news:4B5A046B-5A3F-4FB7-8FED-D4319B59DF81@.microsoft.com...[vbcol=seagreen]
> Can I schedule database restore. I have schedules non sql services to
> stop
> at desired time.
> --
> ontario, canada
>
> "Kevin3NF" wrote:

restore database to different partition

Our client has an SBS 2000 server with SQL 2000 installed.
The server has 3 separate physical hard drives. I am
moving the data to a new server with 1 large physical hard
drive. My question is what is the easiest method to move
the data from the old server to the new server, keeping in
mind that the partions are changing. I don't want to
create the partions on the new server.
Thanks for the help,
JohnSee sp_attach_db and sp_detach_db in BOL. Or you can use
DTS or the backup/ restore method.
>--Original Message--
>Our client has an SBS 2000 server with SQL 2000
installed.
>The server has 3 separate physical hard drives. I am
>moving the data to a new server with 1 large physical
hard
>drive. My question is what is the easiest method to move
>the data from the old server to the new server, keeping
in
>mind that the partions are changing. I don't want to
>create the partions on the new server.
>Thanks for the help,
>John
>.
>|||I like the Copy Wizard myself.
Put database in single user mode.
Right click on server in ent. mgr, then do all tasks/Copy
Database Wizard.
>--Original Message--
>Our client has an SBS 2000 server with SQL 2000
installed.
>The server has 3 separate physical hard drives. I am
>moving the data to a new server with 1 large physical
hard
>drive. My question is what is the easiest method to move
>the data from the old server to the new server, keeping
in
>mind that the partions are changing. I don't want to
>create the partions on the new server.
>Thanks for the help,
>John
>.
>|||Here are some good articles:
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"John Chase" <johnc@.hcd.net> wrote in message news:06a001c39efe$b1f08e80$a001280a@.phx.gbl...
> Our client has an SBS 2000 server with SQL 2000 installed.
> The server has 3 separate physical hard drives. I am
> moving the data to a new server with 1 large physical hard
> drive. My question is what is the easiest method to move
> the data from the old server to the new server, keeping in
> mind that the partions are changing. I don't want to
> create the partions on the new server.
> Thanks for the help,
> John

Restore backup on different machine

We are moving backups from being written on a local box, to writing tham on a
NAS and making a daily copy to a report server. So, to start, I made a manual
copy of the backup files to the NAS and then wen't to restore tham.
What I get is an error message that includes the path name from the machine
where the backup was made as well as the path name for the log file.
Duh!
I can see that I need to add the 'WITH MOVE' parameters to the restore
command, but I can't get them to work. This is probably because I flat-out
don't understand what is happening. Once I say where the full backup is, why
does it care about the path is was backed up to? Why does it care about
restoring a log file I didn't ask for?
Once I change the backup path on the production machine to the NAS (so that
the paths are the same, will this issue just go away?> I can see that I need to add the 'WITH MOVE' parameters to the restore
> command, but I can't get them to work. This is probably because I flat-out
> don't understand what is happening. Once I say where the full backup is,
> why
> does it care about the path is was backed up to?
Because when it restores the database, it needs to create an MDF and LDF
file of the same size for the database to be restored correctly and usable.
> Why does it care about
> restoring a log file I didn't ask for?
When you restore a database, you get the data file(s) and the log file(s).
This is not negotiable.
> Once I change the backup path on the production machine to the NAS (so
> that
> the paths are the same, will this issue just go away?
That depends, if you mean that you intend to restore to the exact same
location as an existing data/log file location, then no, that won't work.

Restore backup on different machine

We are moving backups from being written on a local box, to writing tham on a
NAS and making a daily copy to a report server. So, to start, I made a manual
copy of the backup files to the NAS and then wen't to restore tham.
What I get is an error message that includes the path name from the machine
where the backup was made as well as the path name for the log file.
Duh!
I can see that I need to add the 'WITH MOVE' parameters to the restore
command, but I can't get them to work. This is probably because I flat-out
don't understand what is happening. Once I say where the full backup is, why
does it care about the path is was backed up to? Why does it care about
restoring a log file I didn't ask for?
Once I change the backup path on the production machine to the NAS (so that
the paths are the same, will this issue just go away?
> I can see that I need to add the 'WITH MOVE' parameters to the restore
> command, but I can't get them to work. This is probably because I flat-out
> don't understand what is happening. Once I say where the full backup is,
> why
> does it care about the path is was backed up to?
Because when it restores the database, it needs to create an MDF and LDF
file of the same size for the database to be restored correctly and usable.

> Why does it care about
> restoring a log file I didn't ask for?
When you restore a database, you get the data file(s) and the log file(s).
This is not negotiable.

> Once I change the backup path on the production machine to the NAS (so
> that
> the paths are the same, will this issue just go away?
That depends, if you mean that you intend to restore to the exact same
location as an existing data/log file location, then no, that won't work.

Restore backup on different machine

We are moving backups from being written on a local box, to writing tham on
a
NAS and making a daily copy to a report server. So, to start, I made a manua
l
copy of the backup files to the NAS and then wen't to restore tham.
What I get is an error message that includes the path name from the machine
where the backup was made as well as the path name for the log file.
Duh!
I can see that I need to add the 'WITH MOVE' parameters to the restore
command, but I can't get them to work. This is probably because I flat-out
don't understand what is happening. Once I say where the full backup is, why
does it care about the path is was backed up to? Why does it care about
restoring a log file I didn't ask for?
Once I change the backup path on the production machine to the NAS (so that
the paths are the same, will this issue just go away?> I can see that I need to add the 'WITH MOVE' parameters to the restore
> command, but I can't get them to work. This is probably because I flat-out
> don't understand what is happening. Once I say where the full backup is,
> why
> does it care about the path is was backed up to?
Because when it restores the database, it needs to create an MDF and LDF
file of the same size for the database to be restored correctly and usable.

> Why does it care about
> restoring a log file I didn't ask for?
When you restore a database, you get the data file(s) and the log file(s).
This is not negotiable.

> Once I change the backup path on the production machine to the NAS (so
> that
> the paths are the same, will this issue just go away?
That depends, if you mean that you intend to restore to the exact same
location as an existing data/log file location, then no, that won't work.

Restore a Suspect Database

Is there a quick way of restoring a suspect database without recycling the
services ?. I did set the status to -32768 and moving the database into
another database..........Any other (Easier way) ?
Thanks.
DXC
Last good backup of this database
"DXC" <DXC@.discussions.microsoft.com> wrote in message
news:9C67B96A-312B-41E7-9F38-48A12D8BD7D9@.microsoft.com...
> Is there a quick way of restoring a suspect database without recycling the
> services ?. I did set the status to -32768 and moving the database into
> another database..........Any other (Easier way) ?
>
> Thanks.
>
|||You need a good backup
or
If its not available.
Try to export tables data using DTS.
May be you are successful to import the tables if that one is not
corrupted.
Regards
|||That is OK..........For some reason when I delete (Dropped) the database,
it did not delete the *.mdf and *.ldf files. Then I was able to attached the
database......
"DXC" wrote:

> Is there a quick way of restoring a suspect database without recycling the
> services ?. I did set the status to -32768 and moving the database into
> another database..........Any other (Easier way) ?
>
> Thanks.
>

Restore a Suspect Database

Is there a quick way of restoring a suspect database without recycling the
services ?. I did set the status to -32768 and moving the database into
another database..........Any other (Easier way) ?
Thanks.DXC
Last good backup of this database
"DXC" <DXC@.discussions.microsoft.com> wrote in message
news:9C67B96A-312B-41E7-9F38-48A12D8BD7D9@.microsoft.com...
> Is there a quick way of restoring a suspect database without recycling the
> services ?. I did set the status to -32768 and moving the database into
> another database..........Any other (Easier way) ?
>
> Thanks.
>|||You need a good backup
or
If its not available.
Try to export tables data using DTS.
May be you are successful to import the tables if that one is not
corrupted.
Regards|||That is OK..........For some reason when I delete (Dropped) the database,
it did not delete the *.mdf and *.ldf files. Then I was able to attached the
database......
"DXC" wrote:
> Is there a quick way of restoring a suspect database without recycling the
> services ?. I did set the status to -32768 and moving the database into
> another database..........Any other (Easier way) ?
>
> Thanks.
>

Restore a Suspect Database

Is there a quick way of restoring a suspect database without recycling the
services ?. I did set the status to -32768 and moving the database into
another database..........Any other (Easier way) ?
Thanks.DXC
Last good backup of this database
"DXC" <DXC@.discussions.microsoft.com> wrote in message
news:9C67B96A-312B-41E7-9F38-48A12D8BD7D9@.microsoft.com...
> Is there a quick way of restoring a suspect database without recycling the
> services ?. I did set the status to -32768 and moving the database into
> another database..........Any other (Easier way) ?
>
> Thanks.
>|||You need a good backup
or
If its not available.
Try to export tables data using DTS.
May be you are successful to import the tables if that one is not
corrupted.
Regards|||That is OK..........For some reason when I delete (Dropped) the database,
it did not delete the *.mdf and *.ldf files. Then I was able to attached the
database......
"DXC" wrote:

> Is there a quick way of restoring a suspect database without recycling the
> services ?. I did set the status to -32768 and moving the database into
> another database..........Any other (Easier way) ?
>
> Thanks.
>