|
Home > Archive > microsoft.public.sqlserver.server > November 2002 > Log shipping misc
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Bob Atkinson 2002-11-04, 3:23 pm |
| Need advice on log-shipping details:
TARGET DB recovery mode:
If I specify STANDBY, can I still use this as a publisher
for replication service? What advantage is STANDBY?
Does the NORECOVERY mode make a difference as to whether
or not I allow read-only users, or publish replications?
The target database is set to read-only. So it seems
allowing users running reports, or replication service
jobs would be just fine.
THRESHOLDS:
Any recomendations?
| |
| Ron Talmage 2002-11-04, 3:23 pm |
| Bob,
No, you can't use any log shipping secondary as a replication publisher,
because replication needs to write to the publisher database.
STANDBY allows you to query the secondary, loading db, whereas NORECOVERY
does not allow anyone to read it.
I like to set thresholds to 3 or 4 times the normal copy/load frequency.
Normally I set load delay to 0.
Watch out for bulk loads or mass updates, etc. They may cause the tran log
files to get large, and the restores may take quite a bit longer.
Ron
--
Ron Talmage
SQL Server MVP
"Bob Atkinson" <Bob.Atkinson@tdh.state.tx.us> wrote in message
news:65ff01c28442$33f69060$2ae
2c90a@phx.gbl...
> Need advice on log-shipping details:
>
> TARGET DB recovery mode:
> If I specify STANDBY, can I still use this as a publisher
> for replication service? What advantage is STANDBY?
> Does the NORECOVERY mode make a difference as to whether
> or not I allow read-only users, or publish replications?
> The target database is set to read-only. So it seems
> allowing users running reports, or replication service
> jobs would be just fine.
>
> THRESHOLDS:
> Any recomendations?
>
>
| |
| Geoff N. Hiten 2002-11-04, 3:23 pm |
| Since replication depends on a logreader service, it flat out won't work
with a log-shipped target.
If you want your target database to be available to READ-ONLY users, you
must use the STANDBY clause. STANDBY gives the server a place to hold
uncommitted transactions until the next log restore. If you specify
NORECOVERY, the server applies all log entries, which may leave transactions
open and access to certain records blocked.
"Bob Atkinson" <Bob.Atkinson@tdh.state.tx.us> wrote in message
news:65ff01c28442$33f69060$2ae
2c90a@phx.gbl...
> Need advice on log-shipping details:
>
> TARGET DB recovery mode:
> If I specify STANDBY, can I still use this as a publisher
> for replication service? What advantage is STANDBY?
> Does the NORECOVERY mode make a difference as to whether
> or not I allow read-only users, or publish replications?
> The target database is set to read-only. So it seems
> allowing users running reports, or replication service
> jobs would be just fine.
>
> THRESHOLDS:
> Any recomendations?
>
>
|
|
|
|
|