Re: Transaction Log Shipping setup
- From: "Kevin3NF" <kevin@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 11 Jan 2008 14:00:42 -0600
Ron,
In SQL 2005 Log Shipping, you have a Standby option in the restore tab of
the Log Shipping Properties GUI, which will put your database in read-only
between restores. If your logs take 30 minutes to restore and you restore
every 30 mionutes, you'll be perpetually restoring...
--
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.
"Ron" <Ron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:82650E96-2E17-4435-AF9B-5FF154AB8F10@xxxxxxxxxxxxxxxx
I was wondering the same thing. Our databases are in "restoring" mode and
transaction logs are being applied every 30 minutes.
I vaguely remember reading that to get the database to a readable state
you
must recover the database. I'm not sure what the syntax would be or if
it's
a dummy restore with recover.
Ron
"David" wrote:
We setup Log Shipping on our servers and all seems to have gone well.
However, on the secondary server, the restored database seems to be in a
perpetual restore state. I cannot find any documentation that goes past
the
setup. Is this normal, and if so how do you stop the restore to verify
the
data is being restored correctly.
SQL 2005 SP2
David
.
- Follow-Ups:
- Re: Transaction Log Shipping setup
- From: Ron
- Re: Transaction Log Shipping setup
- Prev by Date: replicated commands not executed on the subscriber side?
- Next by Date: Re: Log Shipping Question
- Previous by thread: Re: Transaction Log Shipping setup
- Next by thread: Re: Transaction Log Shipping setup
- Index(es):
Relevant Pages
|