By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,414 Members | 1,586 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,414 IT Pros & Developers. It's quick & easy.

SQL 2000 log shipping question

P: n/a
Hi,

In the MS SQL 2000 Server, if the log shipping is set up right, does that
mean data in primary server changed will mapped to secondary server later
on?
Thanks.

Jason
Jul 23 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a

"Jason Huang" <Ja************@hotmail.com> wrote in message
news:ct**********@news.seed.net.tw...
Hi,

In the MS SQL 2000 Server, if the log shipping is set up right, does that
mean data in primary server changed will mapped to secondary server later
on?
Thanks.

Jason


All changes to the source database are applied to the target database -
check out "Log Shipping" in Books Online for all the details.

Simon
Jul 23 '05 #2

P: n/a
Jason

Another big reason to use Log Shipping for you DR/Standby solution.
Only the log shipping can update your DR/Standby database. This helps
protect the integrity of your database. If for any reason your
production and standby database do get out of synch, the log shipping
will fail, letting you know very quickly that there is a problem, so
you can fix it.

Regards

John
Simon Hayes wrote:
"Jason Huang" <Ja************@hotmail.com> wrote in message
news:ct**********@news.seed.net.tw...
Hi,

In the MS SQL 2000 Server, if the log shipping is set up right, does that mean data in primary server changed will mapped to secondary server later on?
Thanks.

Jason

All changes to the source database are applied to the target database

- check out "Log Shipping" in Books Online for all the details.

Simon


Jul 23 '05 #3

P: n/a
Do I need to sync the time first for the Primary server and the Secondary
server? 'cuz there's some out of sync messages in the event viewer log.

<jo************@yahoo.co.uk>
???????:11**********************@f14g2000cwb.googl egroups.com...
Jason

Another big reason to use Log Shipping for you DR/Standby solution.
Only the log shipping can update your DR/Standby database. This helps
protect the integrity of your database. If for any reason your
production and standby database do get out of synch, the log shipping
will fail, letting you know very quickly that there is a problem, so
you can fix it.

Regards

John
Simon Hayes wrote:
"Jason Huang" <Ja************@hotmail.com> wrote in message
news:ct**********@news.seed.net.tw...
> Hi,
>
> In the MS SQL 2000 Server, if the log shipping is set up right, does that > mean data in primary server changed will mapped to secondary server later > on?
> Thanks.
>
> Jason
>


All changes to the source database are applied to the target database

-
check out "Log Shipping" in Books Online for all the details.

Simon

Jul 23 '05 #4

P: n/a

"Jason Huang" <Ja************@hotmail.com> wrote in message
news:ct**********@news.seed.net.tw...
Do I need to sync the time first for the Primary server and the Secondary
server? 'cuz there's some out of sync messages in the event viewer log.


<snip>

http://support.microsoft.com/default...b;en-us;329133

Simon
Jul 23 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.