By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,497 Members | 1,287 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,497 IT Pros & Developers. It's quick & easy.

Schedule Local Package to perform FTP and DB restore

P: n/a
Hi,

Did anyone successfully set up a local package to first ftp a db.bak
and second perform an automated db restore?

I need to perform an automated task, which ftp nightly backup file to
another server and then restore onto a database and leave the database
in read-only mode for additional transaction logs restore during the
day.

Can someone help and provide the procedures on how to do that?

Thanks in advance.
Jul 20 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a

"xo55ox" <xo****@hotmail.com> wrote in message
news:ab**************************@posting.google.c om...
Hi,

Did anyone successfully set up a local package to first ftp a db.bak
and second perform an automated db restore?

I need to perform an automated task, which ftp nightly backup file to
another server and then restore onto a database and leave the database
in read-only mode for additional transaction logs restore during the
day.

Can someone help and provide the procedures on how to do that?

Thanks in advance.


You don't mention your MSSQL version or edition, but you might want to check
out this article about implementing log shipping with the SQL 2000 Standard
edition using a reskit tool:

http://www.winnetmag.com/Article/Art...231/23231.html

Or try these links:

http://sqlguy.home.comcast.net/logship.htm
http://www.sql-server-performance.co...g_shipping.asp

If you want to use DTS, it might be easier to execute the package on the
destination (standby) server, because the DTS FTP task can only GET, not
PUT. There is an alternative implementation that will do both here, by the
way:

http://www.sqldts.com/?302

To implement a log shipping package should be straightforward:

1 - Run BACKUP DATABASE on the source server (Execute SQL task)
2 - Use an FTP task to GET the backup file on to the destination server
3 - Run RESTORE DATABASE WITH STANDBY on the target server (Execute SQL
task)

But to add error handling, logging etc. can become more complicated, so you
may want to see if one of the existing solutions is good enough for you.

Simon
Jul 20 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.