Forum Discussion

nbj-ksdh's avatar
nbj-ksdh
Frequent Visitor
1 year ago

OneLake shortcut to Lakehouse SQL endpoint fails to create table

We have an Eventhouse database with a single table synced to OneLake. We've then created a table shortcut from the Eventhouse to a lakehouse - and everything works as expected: The table is visible in the lakehouse explorer, and can be queried using the SQL endpoint of the lakehouse. All good. 

A week later we then try to create another table shortcut from the eventhouse (same table) to a new lakehouse (in a different workspace). Now, the table is visible in the lakehouse explorer, but it fails to load the table to the SQL endpoint, giving the error in the image attached. The original (and completely similar) shortcut still works, and can be seen/queried in the SQL endpoint with data up to date. 

How can a shortcut work, and continue to work, when established at one point in time, but not a week later - when the source and destinations are structurally identical?

All workspaces are hosted in the same region (West Europe).
Content Packs

5 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    1 year ago

    HI nbj-ksdh,

    Did these two workspaces host in the same data regions? Are there assign in the same environment and capacity?(trial or fabric capacity) Please share some more detail information to help us clarify your scenario and troubleshooting.

    Regards,

    Xiaoxin Sheng

    • nbj-ksdh's avatar
      nbj-ksdh
      Frequent Visitor
      1 year ago

      Hi Anonymous , 
      Everything is hosted on the same F16 Fabric capacity in West Europe. Even if i try to add a new lakehouse to the workspace where the shortcut works (in a different lakehouse), it will not work in the SQL endpoint, giving me the same error. Running OPTIMIZE on the table fails too.

      Is there a way to run notebooks against the OneLake table created in the Eventhouse? Currently, pressing the notebook 'related item' in the Eventhouse doesn't do anything. 

      • Anonymous's avatar
        Anonymous
        Not applicable
        1 year ago

        Hi nbj-ksdh,

        So you mean this issue only appear when you work with lakehouse shortcut and the table create in eventhouse? Have you test to use shortcut from another source? I'd like to confirm if this is a specific source issue.

        In addition, this issue sounds related to eventhouse, you can also try to post to the real-time intelligence forum to get better support.

        Eventhouse and KQL - Microsoft Fabric Community

        Regards,

        Xiaoxin Sheng