Issues capturing MDS schema in SSDT project

Alex 21 Reputation points
2022-05-27T04:34:37.907+00:00

Using MDS on SQLServer 2019/Windows 2019. Database version 15.0.5.1. VS2019 with SSDT.

The presence of a fully qualified view name (master.sys.syslanguages) in one of the MDS stored procedures seems to cause problems when trying to compare the schema and load it into a local project:

udpTransactionSave, line 131: 

SELECT @Dateformat = CAST([dateformat] AS NVARCHAR(6)) FROM master.sys.syslanguages where langid = @@langid

Adding a database reference to the master database won't work using Add Database Reference\System Database. As a workaround, I used Add Database Reference\Data-tier Application (.dacpac), pointing to the physical location of the master.dacpac file (not using $(DacPacRootPath) variable), with the option "Same database". This leaves this particular unresolved reference as a warning, but at least there are not dozens of errors that prevent the project from building correctly.

I don't know of any way to submit this as an issue to Microsoft.
This might help others; there was fairly little about this issue online, except the standard "add master database reference", which won't help in this case.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,778 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Erland Sommarskog 101.4K Reputation points MVP
    2022-05-27T08:56:17.04+00:00

    The place ti submit bugs and suggestions - short of opening a support case - is https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0.

    0 comments