We have a database (SQL Server 2008r2) that is being transactionally replicated, namely tables, sprocs, views, indexed views and UDFs only, to another server (SQL Server 2014) as part of a cautious (read: slow) upgrade process. However, we still need to deploy new code or changes to it in the meanwhile.
Whenever we try to deploy new/changed code to it, using DACPAC under Visual Studio, we get a slew of the following errors:
Error SQL72035: [dbo].[SomeTable] is replicated and cannot be modified.
Is there anyway to avoid this? I was thinking if we could script the drop and create of the replication, we could put it in pre and post-deploy script, respectively, but I'm not sure if a) that is a good approach, and b) common practice.