Best Practices - what is better? One with many OR many with one? (cryptic subject or what? .. be pique'd, or piqued, or just curious)

  • Hi,

    When setting up replication from one server to another, I like to have my publications grouped in logical groupings; e.g. for a DataMart type DB, have a publication for the conformed common dimensions (e.g. DimDate, DimProperties, etc), and then have separate publications per 'topic' / 'domain'.
    It was suggested to me that I should simply have one subscription per target server, and if I need to modify some underlying tables etc then I can simply turn off the articles in the publication, do my change, turn it back on.

    Although keeping everything in one publication is somewhat handy, I still feel that organising the publications in smaller bits is more sensible.

    So I guess this is not at all a technical question but just a poll as to what happens out there, 

    Thanks,

    B

  • For posterity : having had a look around and read many (at least 3 possibly 4 ;)) discussions and thinking it through - I'll go for the option of putting as many articles in a publication as I can get away with and will create new publication only when business requirements demand a separate publication (i.e the actual property values have to be different from one publication to the other) ..

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply