views:

652

answers:

3

I am adding SQL Replication (Transactional, single-publisher/distributor with many subscribers, using SQL 2005) to a website and have searched everywhere in the manual and on Google for this.

I am curious -- do I have to actually create a snapshot for new objects to get propagated, or is adding that new object (e.g., table, stored procedure, function) to the list propagate it to the remote subscribers?

A: 

Depending on the configuration of the subscriptions you may or may not have to explicitly update them after adding a new article.

MSDN Details

cmsjr
+1  A: 

Thank you, but I'm still confused. I have a standard Transactional Replication with Initial Snapshot working, where the Master SQL 2005 database is indeed synchronized with a subscribing node (machine). But when I add new sprocs or tables to the publisher, and add them as an Article to the Publication, they do not seem to automatically carry over to the subscribing box. Checking properties of both the subscription and the publisher doesn't seem to reveal any setting that would replicate these changes. (I do have "replicate schema changes turned ON.) I have to be missing something simple... it can't really be true that every time I create a new sproc or table or UDF, that I have to generate a new snapshot of the entire DB, is it?

+1  A: 

You need to run the snapshot, but it will only propagate what has changed (what is new).