Replicated tables and development 1

[flstffatboy]

I'm looking for a little advice on SQL Server 2000 replication best practices and how to deal with table design changes in regards to replication.

Background: Currently using transaction replication. Initially, tables were identifed for transactional replication. The initial publication created contained 25 tables. When more tables are identified for replication a new publication is created for the requirement. Occasionally development is done on the previous replicated tables such as adding new fields.

On the subscriber side certain tables have legacy data inserted into them for reporting purposes. This data does not exist in the tables on the publisher side.

Questions:
1. Is there a way to easily synchronize table design changes on the subscriber side from the publisher side without reinitializing the whole subscription? Does reinitializing the whole subscription basically delete data on the subscriber tables and then make table schema changes before publishing the data back into the subscriber tables?

2.If table development changes are frequent, would I be better off creating many smaller publications with fewer tables so reinitializing the subscriptions is easier.

As you can tell this is fairly new to me so I'm probably confusing terms.

Thanks in advance.

FLSTF

 

[ptheriault]

You can only add new columns to currently replicated tables. And this must be added through the replication monitor. Any other changes will require you to drop and recreate the publication.

If you are making frequent changes it may be less eassier for you to create many small publications\subscriptions.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[flstffatboy]

Thanks Paul.