We're looking at another point of presense for our websites.
What would be the best way to keep the external sql server updated with
current data from the main server? Would a cluster license be required?
Thanks for any advice
Richard
It its one way data flow, use transactional replication. Otherwise I would
suggest merge replication or bi-directional transactional replication.
You would not require a cluster license for this - whatever that is.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Richard" <rcowell%nospam%@.britainusa.com> wrote in message
news:OjmxyB9fEHA.1984@.TK2MSFTNGP10.phx.gbl...
> Hello
> We're looking at another point of presense for our websites.
> What would be the best way to keep the external sql server updated with
> current data from the main server? Would a cluster license be required?
> Thanks for any advice
> Richard
>
|||Richard,
I'd like to know a bit more about your requirements, but firstly, is the
'other point of presence' read only or read/write? If it is read only, you
have a choice between log-shipping and transactional replication (have a
look at the articles section on http://www.replicationanswers.com/ for a
comparison of functionality).
If read/write, have a look at merge replication.
Clustering isn't suitable as it won't duplicate your data - it provides
automatic failover of the SQL server based on a single source of data - RAID
or SCSI array.
HTH,
Paul Ibison
|||Hi
The new presence will be read/write.
We currently have 2 sql servers here, one live and another backup - ideally
i'd have both of them live if possible. I'm not familiar with merge
replication, is it available in standard sql 2000?
Rich
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ewZVoJ9fEHA.3048@.TK2MSFTNGP09.phx.gbl...
> Richard,
> I'd like to know a bit more about your requirements, but firstly, is the
> 'other point of presence' read only or read/write? If it is read only, you
> have a choice between log-shipping and transactional replication (have a
> look at the articles section on http://www.replicationanswers.com/ for a
> comparison of functionality).
> If read/write, have a look at merge replication.
> Clustering isn't suitable as it won't duplicate your data - it provides
> automatic failover of the SQL server based on a single source of data -
> RAID
> or SCSI array.
> HTH,
> Paul Ibison
>
|||Richard,
Standard Edition is fine. BOL has plenty of details on setting up merge and
here is a walkthrough you can use:
http://www.mssqlcity.com/Articles/Re...MR/SetupMR.htm
HTH,
Paul Ibison
|||That's great thanks a lot for your help, Paul & Hilary
Rich
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23jeIJV9fEHA.3964@.TK2MSFTNGP12.phx.gbl...
> Richard,
> Standard Edition is fine. BOL has plenty of details on setting up merge
> and
> here is a walkthrough you can use:
> http://www.mssqlcity.com/Articles/Re...MR/SetupMR.htm
> HTH,
> Paul Ibison
>
No comments:
Post a Comment