October 16, 2007 at 2:32 pm
Hi,
I Implemented Transactional replication (with immediate updating subscribers) between two sql 2005 servers. The server has got one database and this entire database has to be replicated to the other server. First i created the publication by selecting all the tables and store procs on the master server
Then on subscriber i ran the script to create DB and created a subscription.
It seems i got the data from the publisher but along with it i also got a few more tables like dbo_conflict_publicationame_table name for all the tables. How to get rid of these unwanted tables
secondly, if i create a new table, can that be replicated ?..how should i add it to the existing publication..does it automatically get added?
Thanks
Murali
October 17, 2007 at 5:51 am
Typically, it is best to let replication create and use a snapshot to initialize a subscriber. This will ensure you get the correctly selected articles in the subscriber database rather than everything. Replication allows you to choose whether to include keys, constraints, indexes, etc. on each article, so make sure you scripted just what you are replicating or let replication create and apply a snapshot.
As far as tables being added - the answer is "it depends". If you add a table to the publisher and the table is added to the subscription, and replication is configured to create this new article (typically through a snapshot), it will be created on the subscriber.
Replication has a lot of options. It is easy to set up with all of the defaults, and typically simple to maintain when set up like this. If you stray from the default behavior in any way (which by not initializing with a snapshot, you already really have), you should really get a book on SQL replication and read up on it first.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply