Did you ever try to drop a replicated table? Of course this is disallowed! It was always that way right?
If you do try it what you’ll see is a variation on the following message:
Well actually this has now changed and you can merrily drop the table.
It’s not enabled by default but if you run the following you’ll be permitted to do it.
@publication = ‘yourpublicationname’,
@property = N’allow_drop’,
@value = ‘true’
If when you run the above you get a nasty error message as follows:
Msg 21183, Level 16, State 1, Procedure sp_MSrepl_changepublication, Line 274 [Batch Start Line 0]
Invalid property name ‘allow_drop’.
……that means that you have other problems: your SQL server is not up to date! Naughty DBA! This facility came in with SQL 2014 Service Pack 2 and SQL 2016 Service Pack 1. Sorry but nothing doing for SQL 2012/2008R2/2008!
Once it is set, you can happily drop tables in the publication database and the replication agents won’t error. The log reader will clean up the metadata related the article and ignore any remaining unprocessed commands related to the table. It also removes the article from the publication. The distribution agent processes the article records already sent to it by the log reader and when it reaches the cleanup command it has completed the processing for this article.
Note that the distribution agent doesn’t report the fact that the drop table has been processed during a synchronization. So we will not really be aware this has happened. Also the distribution agent doesn’t send the “Drop” statement down to the Subscriber either so the table is left there intact. This is quite unlike other DDL changes which keep the publisher and subscriber in sync. It’s safer this way but it’s a pity an additional option to send the delete doesn’t exist.
Finally, once it is set you’ll not see it so easily in syspublications. Another explicit column for this setting would have been nice but instead it is hidden in the logic of the options bitmap. However you can run the following to check if it is enabled:
EXEC sp_helppublication @publication = ‘yourpublicationname’
And then you’ll have a clear report of the flag setting….