Groups | Blog | Home
all groups > sql server replication > march 2007 >

sql server replication : Type of Replication?


EdwardH
3/7/2007 11:25:03 AM
I have SQL 2000 tables (5) that I want to replicate to SQL 2005 Workgroup on
Remote web Server which need to synchronise else say twice a day but without
jimkatsos NO[at]SPAM gmail.com
3/7/2007 5:03:06 PM
Assuming data is only read at the subscriber not updated. Then
snapshot replication may be a good choice here, as it is best suited
to end of day batch updating of the subscriber. Be aware if data
volumes are large that snapshot replication can take a long time as it
moves the entrire contents of the tables for each synchronise. Also
locks are placed on the publisher table so that a read consistent
point in time view of the source data is captured. So be carefull.

One way transactional replciation is also an option (if you have a
small tolerance of tables being offline at both ends) where changes
are progated almost immedaitely so that publisher and subscriber are
in sync. I would be considering this as well.

Regards Jim.
http://jims-spanakopita.blogspot.com/


Paul Ibison
3/8/2007 12:00:00 AM
We'd need to know a little more before answering. The Web server - is it
updatable and is it always connected to the publisher?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Hilary Cotter
3/8/2007 10:08:19 AM
It is unlikely your ISP will open port 1433 for inbound communication, so it
will be difficult to get this running unless they open a port for you and
you can configure your SQL Server to run on this port.

As ftp is probably open to you, you might be able to bcp the data out to an
ftp site, and have the remote SQL Server bcp the data into staging tables
and then only push the delta's into the live tables. With tracking you can
keep the data flow to a minimum.
--
Hilary Cotter

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



[quoted text, click to view]

EdwardH
3/11/2007 4:46:13 AM
Jim,
Many thanks,
I think I am tending towards transactional replication. The publisher data
would only flow to subscriber - is there much of an overhead on the publisher?

[quoted text, click to view]
EdwardH
3/11/2007 4:50:00 AM
Paul,
Many thanks,
The data flow would only go from Publisher to Subscriber via a "standard"
internet connection say 2Mb Broadband - always online.
I am beginning to tend towards transactional replication - would this
involve much of an overhead on publisher?

[quoted text, click to view]
EdwardH
3/11/2007 5:08:00 AM
Hilary,
Many thanks
It will be my own SQL Server box hosted in a DataCentre which should have
1433 open. Are you saying that tranactional replication would not be
practical? Dataflow would only go from Publisher to web subscriber. Two
tables of circa 50,000 recs need to be in synch.

[quoted text, click to view]
Paul Ibison
3/12/2007 12:00:00 AM
Yes - I would recommend Transactional Replication for this. As for the
overhead on the publisher, this has to be simply tested empirically, but I
find typically the log reader doesn't use much in the way of resources. If
this is a concern, then run the distributor agent on the subscriber (PULL)
and if you really want to optimise the system, you could have the
distributor on a separate server.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com



AddThis Social Bookmark Button