September 23, 2013 at 11:36 am
I have replication running with a 2 publications coming out of the same database. Publication number 1 has all but 300 of a 8000 table database, publication number two has only the 300 of the 8000 tables. So basically I have all the data published, i just have 300 tables subscribed to one database and the remaining 7700 subscribed to the other database.
Both are transactional push. When I monitored the Log Reader Agent Status, I was very surprised to see that both publications were delivering the exact same transactions/commands which leads me to believe that with transactional replication, everything is delivered to the distributor and then from there the decision is made as to which articles are pushed to the subscriber.
So in other words if I have an 8000 table, 2TB database, and I only want 1 table to be transactionally replicated. All changes for all 8000 tables will be delivered to the distributor and only the changes for the 1 table will be applied to my subscription database.
Does this seem accurate?
thanks!
September 23, 2013 at 3:57 pm
Only one table changes not all.
September 24, 2013 at 5:41 am
If I publish only one table(article), only one table on the subscriber gets updates, but updates for all the tables (whether published or not) go across the network to the distributor and it is there where it is determined which tables are published.
Or maybe it's just my imagination?
September 24, 2013 at 7:45 am
There will only be a single log reader for each published database. Both of your publications are referring to the same log reader agent which explains why you're seeing a higher than expected command throughput.
The log reader processes commands that affect any article marked for publication (across any of the publications on the published database).
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply