February 28, 2012 at 7:54 am
Hi,
can we add a fresh table which is not from the replicated publisher environment?
will it break the replication?
thanks
ami
February 28, 2012 at 7:56 am
Not that it should break replication unless you're connecting the new table to an existing "article" table, but ...
Which side of replication are you intending to add the table?
February 28, 2012 at 8:19 pm
adding to the subscriber side
February 29, 2012 at 5:03 am
When I look this up, every reference I find is in regards to published objects. So long as this table is not being published to the subscriber, you should be able to add it to the subscriber just fine. I would advise doing so in T-SQL, though, rather than through the GUI, because you have more control over what the engine does by using code.
Also, so long as you don't try to create foreign keys between this new table and published tables, you should be fine. But if you do try to create that kind of connection, or if you are creating a published table, then you will break replication.
EDIT: Oh, I am so WRONG. Look up this article: http://technet.microsoft.com/en-us/library/ms151870.aspx
Schema changes should be made only at the Publisher, not at Subscribers (including republishing Subscribers). Merge replication prevents schema changes at the Subscriber. Transactional replication does not prevent the changes, but the changes can cause replication to fail.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply