Re: Transaction Log Shipping setup

The restore only takes a few seconds. I now understand it's "restoring"
because it's in nonrecovery mode within log shipping and I could change it to
standby.

However, how do you get the database to be fully functioning (read/write)?
Will removing the instance from the log shipping setup on the primary
database delete the secondary jobs and recover the secondary database?

Thanks

"Kevin3NF" wrote:

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




.

Relevant Pages

  • Re: Transaction Log Shipping setup
    ... use the GUI on the source and remove the log shipping. ... In the second case (server blown to pieces), run all the LS_Restore jobs to ... restore database MyDestinationDB with recovery ... how do you get the database to be fully functioning? ...
    (microsoft.public.sqlserver.replication)
  • Database goes into Supect or Loading state after Restore
    ... I am do log shipping from one server to another. ... It just stays there until I do a manual restore. ... only difference between this database and the others is the size. ... RESTORE DATABASE W3Data ...
    (microsoft.public.sqlserver.replication)
  • Re: log shipping
    ... Databases are in 'STANDBY ' after a RESTORE DATABASE command using the ... I support the Professional Association for SQL Server ...
    (microsoft.public.sqlserver.clustering)
  • Re: How best to move large databases?
    ... He also covers many issues about making sure that once you have moved the database it has all the supporting jobs, shares,, and other components. ... You will notice that he discusses using log shipping a little over halfway down. ... Restore a backup of your database to the new server either using WITH NORECOVERY or WITH STANDBY. ...
    (microsoft.public.sqlserver.server)
  • Re: Restore leaves DB in Loading state
    ... Here's the SQL statement I'm using for the restore. ... STANDBY because this is a warm standby server. ... You can issue a 'RESTOER DATABASE ...
    (microsoft.public.sqlserver.server)