By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,432 Members | 795 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,432 IT Pros & Developers. It's quick & easy.

Replication and sql server 2005

P: n/a

Reading an article on replication for sql server 2k, it mentioned about
sp_repladdcolumn/sp_repldropcolumn stored procs, implying that when a
new column is added or dropped from source table, one needs to execute
some sp to ensure that related replication meta data would be in sync.
I'm just thinking loud here, essentially there are two ways to do it
(by design):
* manually making replication meta data match with source table meta
data (as now with 2k server). Big disadvantage: one can easily forget
about this step.

* automatically making replication meta data match with source table
meta data whenever source meta data changes. Some assumptions and cost
for this option:
a) the need to add or drop a column for the source table would also
exist for the replicated data;
b) the mechanism to perform replication meta data update when ddl
occures at source table (price)

So, maybe there's a time one wants to do it manually and other time
doing it automatically would be more desirable. Easily solved if
server/database setup configuration has an option to support that.

Jul 23 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.