Provide a way to update SSDT system database reference DACPACs
Please provide a method for updating the master.dacpac and model.dacpac reference databases that install with SSDT.
The versions that install with SSDT are static and do not reflect any changes/enhancements/bug-fixes that are made within SQL Server.
For example, the SQL Server 2017 master.dacpac is missing the new system DMV's [sys].[dmoshostinfo] and [sys].[dmdblogstats], and the recently released SQL Server 2016 SP2 adds a new DMV [sys].[dmdbloginfo] and new columns to the DMV [sys].[dmossysinfo] which will be missing from the SQL Server 2016 master.dacpac.
Any referenes to new DMV's/columns generate 71502 (unresolved reference) errors. The workaround is to ignore these errors, but it would be better to have a mechanism in place to ensure the reference system database DACPACs were up-to-date.
Jetzer, Bill commented
I agree. I would love to check the "Treat warnings as errors" box to keep our developers from being sloppy, but my (SQL 2012) project currently has a few dozen 71502 errors regarding master.dbo.spt_values, sys.dm_exec_query_stats, and sys.dm_exec_sql_text.
Have been toying with the idea of extracting the master dacpac and distributing it to all developers, then adding a script in Azure DevOps so that prior to building the solution we overwrite the master dacpac on the build server (if the location can be determined programmatically and we have write permission on the file).