SQL Server Performance

pro and con for setting a publication for each article and one publicationn for all articles

Discussion in 'SQL Server 2008 Replication' started by WingSzeto, May 16, 2013.

  1. WingSzeto Member

    Hi all,

    We are using push transaction replication and distributor is on its own server in a SQL 2008 env.
    Within a user db, I normally set up one publication for all articles I want to publish in that db. But I also see other dba set up one publication for each article. Are there benefits doing one publication for each article? If there are a lot of articles, there will be so much to manage. Obviously for creating a publication for each article, each article will have its own jobs (snapshot, distribution). Is this good or bad? If there is a high volume and high insert rate table in a db (ie. 8000 insert per min), would it be a good reason to seperate it to its own publication?


Share This Page