Forum Discussion

cw88's avatar
cw88
Helper IV
2 years ago
Solved

Azure Data Studio Database Project: Reference to Lakehouse

Hi all,  i try to create a database project in azure data studio. The import of all objects works fine, but when i try to build the project i get errors with the message "... [Object] contains an un...
data warehouse
  • AndyDDC's avatar
    AndyDDC
    2 years ago

    Hi cw88 only Fabric Warehouses are officially supported in Azure Data Studio.

     

    However, I have been able to also import a Lakehouse schema into an Azure Data Studio project where the target platform is set to Fabric Warehouse.  Then the only way I could get the cross-database dependency to build from the Warehouse to the Lakehouse was to successfully build the Lakehouse, then in the Warehouse create a Database Reference to the Lakehouse dacpac.

     

    In the image below I have a Warehouse and a Lakehouse project.  The Warehouse has a Database Reference to the Lakehouse dacpac.

     

    I did use the Azure Data Studio Insiders build for this.

     

    https://github.com/microsoft/azuredatastudio#try-out-the-latest-insiders-build-from-main-branch

     

     

AndyDDC's avatar
AndyDDC
Most Valuable Professional
2 years ago

Hi cw88 only Fabric Warehouses are officially supported in Azure Data Studio.

 

However, I have been able to also import a Lakehouse schema into an Azure Data Studio project where the target platform is set to Fabric Warehouse.  Then the only way I could get the cross-database dependency to build from the Warehouse to the Lakehouse was to successfully build the Lakehouse, then in the Warehouse create a Database Reference to the Lakehouse dacpac.

 

In the image below I have a Warehouse and a Lakehouse project.  The Warehouse has a Database Reference to the Lakehouse dacpac.

 

I did use the Azure Data Studio Insiders build for this.

 

https://github.com/microsoft/azuredatastudio#try-out-the-latest-insiders-build-from-main-branch

 

 

vitaly's avatar
vitaly
Advocate II
2 years ago

Hi AndyDDC ,

 

We are using a similar solution.

 

The challenge is that while SQLCMD variables work, the literal strings do not work during the build. This means we have to manually update all the references to Lakehouse objects to use variables. This presents two challenges:

 

1) It's a manual step and adds effort to each new object

2) The variable references come up as a "change" during each database => database project schema comparison

 

Have you been able to make references to work using the standard 3-part name, without involving code changes and variables?