title: Can I ALTER an existing table schema using a post-deployment script?
body: <p>Using </p>
  
  <ul>
  <li>SQL Server 2008 (not R2) </li>
  <li>Visual Studio 2012 Premium </li>
  <li>SQL Server Database Project/SQL Server Data Tools (SSDT)</li>
  </ul>
  
  <p>Are there any problems\potential issues with altering a table schema using a post-deployment script?</p>
  
  <p>My company has a web application (App A) whose backend database has tables that are replicated to another company application's database (App B) using CDC Replication. Making schema changes to these tables causes SSDT to use DROP/CREATE when generating the deployment script. This is a problem for App B's database that uses CDC Replication on these tables, because when the table is dropped and recreated, App B's database's CT_[table_name] tables are dropped, bringing App B down. My solution is to use a post-deployment script to make ALTERations to these tables, instead of allowing SSDT to generate DROP/CREATE. Are there any potential problems or issues with this approach?</p>
  
  <p>I could really use some help.</p>