Sensitivity classification feature in SQL 2019

Lindgren, Lars 1 Reputation point
2021-08-10T06:43:32.19+00:00

We have SQL Database projects with Target platform “SQL Server 2019 (and in addition Azure SQL databases managed instance” in VS2019 for some our databases).
We regularly deploy database code via Azure YAML multistage deployment pipelines using MSBuild publish, that uses Schema compare feature.
Recently we started to use new Sensitivity classification feature in SQL 2019 Server and have classified about 20 000 columns in one database.
After adding that to code, MSBuild.exe which builds our project, started to run dramatically longer – 3h, after some optimization (added MSBuild arguments -m /p:CmdLineInMemoryStorage=TRUE ) – 1 h. If we do not store classifications in code, lines are dropped from database in every deployment.
The one thing, that could help us is Ignore or DoNotDrop key in database.publish.xml configuration file , that we use , for example for logins we have row like <DoNotDropLogins>True</DoNotDropLogins>.

In this case we could store classifications in separate script, that is not analyzed during build.
We tried to find appropriate flag for Sensitivity classification in Microsoft.Data.Tools.Schema.SqlTasks.targets file, but did not succeeded.
Will that exists, but not documented? Or do we need to find other approach?

Hope anyone can help us,

Br Lars

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
14,494 questions
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.