Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Same article in multiple publications


Same article in multiple publications

Author
Message
psteja2000
psteja2000
SSC Rookie
SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)

Group: General Forum Members
Points: 26 Visits: 65
We have a merge replication scenario with pull subscriptions. Currently there is only one publication but we are adding a new publication, where some articles are going ot be common. Some of the common articles are going to be download only. but some are updateable on both sides. With this information, can someone please point me the right direction to achieve this? Obvious goal is to do it right the first time even if the solution seems eccentric. Thank you.
Robert Davis
Robert Davis
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1702 Visits: 1623
the best practice here is to not put an article in multiple pulbications. It's bad for performance. Breal it up into smaller publications if you have to and send multiple publications to the same subscribers, but don't do what you propose.



My blog: SQL Soldier
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master, SQL Server MVP
Database Engineer at BlueMountain Capital Management
psteja2000
psteja2000
SSC Rookie
SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)

Group: General Forum Members
Points: 26 Visits: 65
So for a bidirectional(but always inserted at the subscriber) article, across publications, even if it is guaranteed that a uniquely identified row exists at only one subscriber (other than the publisher of course), you think it still might cause performance bottleneck? This is a filtered article in both publications.

As an example, let's say this is a 'UserLog' table. only subscribers log and not the publishers. There are two different publications, but only one 'UserLog' table, so we got to include it in both publications. We filter subscriptions by userid, so all datasets are disjoint wrt userid.

Do you think this still is a performance bottleneck?
Robert Davis
Robert Davis
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1702 Visits: 1623
When it an article is in multiple publications, it is tracked separately for each one. So every update to the table will be tracked multiple times. This will cause there to be more records in the tracking tables. You are better off putting that table into a publication by itself and subscribing both subscriptions to it.



My blog: SQL Soldier
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master, SQL Server MVP
Database Engineer at BlueMountain Capital Management
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search