Re: Transaction Log Shipping setup

However, how do you get the database to be fully functioning
(read/write)? <<

Fully funtioning, as in "we don;t want to log ship anymore"

Or as in "our source server just blew up and we are pointing our
applications to the destination box?"

In the first case, use the GUI on the source and remove the log shipping. I
do not recall if this brings the former destination db online or not.

In the second case (server blown to pieces), run all the LS_Restore jobs to
bring it as current as possible, then:

Use Master
go

restore database MyDestinationDB with recovery

--

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:950C6DDD-8194-4B73-9D2A-41719D27D5AA@xxxxxxxxxxxxxxxx
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: Problem with disable msde connection pool
    ... 'ALTER DATABASE TestDB SET single_user WITH ROLLBACK after 10 ... ' Restart the server... ... ' Execute query through SQLDMO to run the restore TSQL command ... the connection pool must be disabled. ...
    (microsoft.public.dotnet.framework.adonet)
  • RE: Restore public folders and companyweb
    ... I understand that the Public Folder Store ... > database cannot be mounted due to integrity problems, ... > the pub.edb database from your backup of the old Server, ... please try the following steps to restore your public ...
    (microsoft.public.windows.server.sbs)
  • RE: Restore public folders and companyweb
    ... The new server must have the same domain name as the original server ... where the backup of the database. ... For the detailed steps to restore the SharePoint Services databases, ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL 2000 SP4 on 2003 Server - Single User Mode
    ... I found the section where you list the filename to restore to. ... rename the SQL Server the same as what is listed below Courthouse? ... Once you've created your database (simply right click on the Database ...
    (microsoft.public.sqlserver.setup)
  • RE: How to restore edb & stm files from bkf backup file on another exc
    ... copied to a different storage group on the same server or to a different ... On production server successfully backup information ... Restore Status ... Failed to find a database to restore to from the Microsoft ...
    (microsoft.public.exchange.admin)