问题
I have the following questions about how transactional replication handles the following. For the sake of example, assume database 'A' is being replicated (via transactional replication) to database 'B'.
- If a table in database ‘A’ is dropped, will the table get dropped in ‘B’?
- If a table in ‘A’ is renamed, what happens to the table in ‘B’?
- If we drop a column in a table in database ‘A’, what will happen to the column in the same table in database ‘B’?
- If we rename a column in a table in database ‘A’, what will happen to the column in the same table in database ‘B’?
- Is replicating stored procs, views and UDF’s are optional?
- Is there any way to avoid all the stored process being created in database ‘B’ as a result of it being the subscriber of a replication? a. If not, can we at least dictate what schema they are created in?
回答1:
Most of your questions are answered here: Frequently asked questions for Replication Administrators
- You cannot drop a table that is replicated. You have to first drop the article.
- You cannot rename a table that is replicated. You have to first drop the article.
- Issuing ALTER TABLE … DROP COLUMN at the Publisher, will result in the command being replicated to the Subscriber.
- You cannot rename a column "whilst" it is being replicated. You need to remove it from replication first.
- Yes, it's optional.
- What do you mean by created?
All of these items can be tested very easily by creating a very simple Replication topology on a test server. I suggest you do so in order to both plan for and practice your changes.
来源：https://stackoverflow.com/questions/4316701/transactional-replication-questions