Sql-server – Will SSDT publish always fail with “Data Loss May Occur” when table is rebuilt

I've been tempted to bypass that flag also but have come down on the side of your co-workers and now try to deal with these issues "correctly". The (marginally) less clunky route is to use pre and post deployment scripts to do the work with a rename.

• Rename the existing table in a pre-deployment script.
• With the existing table missing the table in focus will be created as per the new schema definition.
• In a post-deployment script copy from the renamed original table to the new version.

Depending on the nature of the target you may of course need to take care of dropping and recreating foreign key constraints.

In our processes using Database projects and DacPacs, we decided against using DacPacs to deploy anything except the basic components that are changed as part of ongoing maintenance and support. This is just tables, views, stored procedures, extended properties, user defined data and table types, Scalar and table Valued Functions.

We instead manage security and database settings via a collaborative approach including the development teams and the database team.

Of course we are not in a situation where we are creating databases from scratch very often and security is pretty stable requiring infrequent changes.But the security is included in the project. To fix the problems we originally had with the logins causing build failures, we changed the Create User objects to eliminate the password:

Create User [user] Without Login;

We have not had problems with drift being detected on these user objects. You could try this aproach to see if it fixes your problem.