How many articles can take part in merge replication?
I need to replicate about 200 tables. From them 25 are common for all my
subscribers and do not need to be filtered. Other I plan to filter with
static filters.
Is there benefit to allocate this 25 common tables in separate publication
or it will be better to include them in all publications where tables with
filters are placed?
Ideally you would have a single publication. There is no performance impact
by having multiple publications. If you are going to have multiple
publications (perhaps a publication for each article), you should group
articles which are related (PK-FK) relationships into the same publication.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"massa" <massa@.discussions.microsoft.com> wrote in message
news:460AB955-4C93-4EE0-BC24-3B479E7807CF@.microsoft.com...
> How many articles can take part in merge replication?
> I need to replicate about 200 tables. From them 25 are common for all my
> subscribers and do not need to be filtered. Other I plan to filter with
> static filters.
> Is there benefit to allocate this 25 common tables in separate publication
> or it will be better to include them in all publications where tables with
> filters are placed?
>
Showing posts with label replicationi. Show all posts
Showing posts with label replicationi. Show all posts
Monday, March 26, 2012
Wednesday, March 7, 2012
Replication Monitoring
What would be a best practice for monitoring Replication?
I have Transactional Replication going from the Production database (SQL00) to the Reporting database (SQL03).
Are there some Alerts I need to make sure I have setup to notify me?
Should I do a Validate Subscription once a week or so?
What would you do to have peace of mind that your reporting database is exactly in sync with your production database?
Thanx!
This depends on the stability of your links. If you are well connected, i.e. have highly reliable links set up the replication alerts to alert you when your job fails.
If your links are somewhat unstable set up the replication alerts to alert you when a job fails, but make sure you click on the response tab, and set a threshold to be alerted at, i.e. once per day, hour, etc.
You can schedule validations using sp_publication_validation. Use this proc in conjunction with the Replication: Subscriber has failed data validation alert.
How frequently you wish to run a validation depends on what you are doing. In general with a read only subscriber I never feel the need to run one. Your comfort level (or your bosses') might vary from mine.
With an updateable subscriber (immediate, queued, or merge) you might feel the need to run validations more often.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23juwUyqjEHA.2764@.TK2MSFTNGP11.phx.gbl...
What would be a best practice for monitoring Replication?
I have Transactional Replication going from the Production database (SQL00) to the Reporting database (SQL03).
Are there some Alerts I need to make sure I have setup to notify me?
Should I do a Validate Subscription once a week or so?
What would you do to have peace of mind that your reporting database is exactly in sync with your production database?
Thanx!
I have Transactional Replication going from the Production database (SQL00) to the Reporting database (SQL03).
Are there some Alerts I need to make sure I have setup to notify me?
Should I do a Validate Subscription once a week or so?
What would you do to have peace of mind that your reporting database is exactly in sync with your production database?
Thanx!
This depends on the stability of your links. If you are well connected, i.e. have highly reliable links set up the replication alerts to alert you when your job fails.
If your links are somewhat unstable set up the replication alerts to alert you when a job fails, but make sure you click on the response tab, and set a threshold to be alerted at, i.e. once per day, hour, etc.
You can schedule validations using sp_publication_validation. Use this proc in conjunction with the Replication: Subscriber has failed data validation alert.
How frequently you wish to run a validation depends on what you are doing. In general with a read only subscriber I never feel the need to run one. Your comfort level (or your bosses') might vary from mine.
With an updateable subscriber (immediate, queued, or merge) you might feel the need to run validations more often.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23juwUyqjEHA.2764@.TK2MSFTNGP11.phx.gbl...
What would be a best practice for monitoring Replication?
I have Transactional Replication going from the Production database (SQL00) to the Reporting database (SQL03).
Are there some Alerts I need to make sure I have setup to notify me?
Should I do a Validate Subscription once a week or so?
What would you do to have peace of mind that your reporting database is exactly in sync with your production database?
Thanx!
Subscribe to:
Posts (Atom)