Hi,

I have a log shipping setup between two servers. There is a need to
utilize the database at the subscriber once a week and then replace it
with the fresh production copy and continue with log shipping.
So here is the plan: .
1. Start log shipping (running it for 4 days).
2. Stop log shipping by a script.
3. Make the subscription database accessible to everybody.
4. Use subscription database for processing (for 1 day)
5. Reinitialize log shipping with the script (including the full
backup).

Go through that scenario every week. Replication is not an option
here for multiple reasons (too long to mention here).
The problem here is the script that can stop logshipping, apply last
transaction log and then re-initialize all over again. Can anybody
suggest what to do here (any sample scripts)?

Anatoliy

Off the top of my head:

Script out the stopping of the four jobs (backup, copy, restore, alert)

Script making the db available (restore Database MyDB with recovery)

When done,

Script a full backup and restore on the destination

Script that re-enables the jobs...LS should pick right up with the first
t-log backup created after the scripted full.

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

Blog posts for new DBAs:
http://kevin3nf.blogspot.com/search?q=sql+101

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.

Twitter: Kevin3NF

"tolcis" <nytollydba (AT) gmail (DOT) com> wrote

Hi
Perhaps you also want to look at SNAPSHOT databases

"tolcis" <nytollydba (AT) gmail (DOT) com> wrote