title: SqlPackage and sensitivity classification
body: <p>I've recently updated the <code>SqlPackage</code> and it now tries to rebuild tables every time I deploy (<code>&lt;Alert Name=&quot;DataMotion&quot;&gt;</code>):</p>
  <pre><code>PRINT N'Starting rebuilding table [dbo].[Users]...';
  
  
  GO
  BEGIN TRANSACTION;
  
  SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
  
  SET XACT_ABORT ON;
  
  CREATE TABLE [dbo].[tmp_ms_xx_Users] (
      &lt;columns&gt;
  );
  
  IF EXISTS (SELECT TOP 1 1 
             FROM   [dbo].[Users])
      BEGIN
          INSERT INTO [dbo].[tmp_ms_xx_Users] (&lt;columns&gt;)
          SELECT   &lt;columns&gt;
          FROM     [dbo].[Users]
          ORDER BY [Id] ASC;
      END
  
  DROP TABLE [dbo].[Users];
  
  EXECUTE sp_rename N'[dbo].[tmp_ms_xx_Users]', N'Users';
  
  COMMIT TRANSACTION;
  
  SET TRANSACTION ISOLATION LEVEL READ COMMITTED;
  
  
  GO
  </code></pre>
  <p>I boiled down the problem. The problem is that <code>SqlPackage</code> now has a native support of <code>ADD SENSITIVITY CLASSIFICATION</code> statements.</p>
  <p>Because the classifications were not supported, we had them added as a big post-deployment script.</p>
  <p>I tried to include the script into the model, but then <code>SqlPackage</code> complains that the table XXX is not found when trying to apply the annotations.</p>
  <pre><code>EXEC : error SQL70511: Table 'Users' was not found [xxxproj]
  </code></pre>
  <p>It seems that <code>SqlPackage</code> want the annotations to be present in the table definition scripts. But doing this would require an extensive rewrite which I would like to avoid.</p>
  <p>The question is: is there a switch to ignore the classifications to stop the table rebuilds?</p>