Keepthe number of publications small Inparticular, try not to
referencethe same table in many different publications.
Thework the database server needs to do is proportional to the number of
publications. Keeping the number low and making effectiveuse of
subscriptionslightens the load on the database server.
Whenoperations occur on a table, the database server and the Message
Agentmust do some work for each publication that contains the table.
Havingone publication for each remote user will drastically increase the
loadon the database server. It is much better to have a few publications
thatuse SUBSCRIBE BY and have subscriptions for each remote user.
Thedatabase server does no additional work when more subscriptions are
addedfor a publication. TheMessage Agent is designed to work
efficientlywith a large number of subscriptions.
Grouppublications logically Forexample, if there is a table that every
remoteuser requires, such as a price list table, make a separate
publicationfor that table. Makeone publication for each table where the
datacan be partitioned by a column value.
Usesubscriptions effectively When remote users receivesimilar
subsetsof the consolidated database, always use publications that
incorporateSUBSCRIBE BY expressions. Donot create a separate
publicationfor each remote user.
Payattention to Update Publication Triggers Inparticular:
Usethe NEW / OLD SUBSCRIBE BY syntax.
Tunethe SELECT statements to ensure they are accessing the database
efficiently.
Monitorthe transaction log siz e Thelarger the transaction log, the
longerit takes the Message Agent to scan it. Renamethe log regularly
anduse the DELETE_OLD_LOGS option.
104