Forum Discussion

HarderT's avatar
HarderT
Helper II
1 year ago
Solved

SQL Endpoint from Lakehouse is SUSPECT

Hello,   Since the May 22nd update, some of the Lakehouse SQL endpoints are showing as SUSPECT in SSMS.   I can see the data in Lakehouse, but when I switch to the SQL endpoint, I don't see any d...
Lakehouse
  • v-dineshya's avatar
    v-dineshya
    1 year ago

    Hi HarderT ,

    I have suggested all the possible solutions. I recommend opening a Microsoft support ticket so they can trace the issue. To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:

    How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

     

    If my response has resolved your query, please mark it as the "Accepted Solution" to assist others. Additionally, a "Kudos" would be appreciated if you found my response helpful.

    Thank you

     

v-dineshya's avatar
v-dineshya
Community Support
1 year ago

Hi HarderT ,

Please follow below steps.

1. Use Azure Data Studio with Azure Active Directory - Universal with MFA

SSMS does not handle token refresh well, especially in Fabric/AAD contexts.

open Azure Data Studio, Try connecting using Authentication type: Azure Active Directory - Universal with MFA

Server: your-sql-endpoint-url (from Fabric Lakehouse). If it connects and shows your tables, the issue is SSMS specific.

2. Manually Refresh SQL Endpoint Metadata (with Admin Rights)

You mentioned not seeing the “Refresh Metadata” option this might be restricted to Fabric Admins or require certain roles.

Try this workaround to fix:

Go to Fabric > Lakehouse, From the Lakehouse Explorer panel, create a dummy table or modify a schema slightly
(e.g create/drop a test table). This sometimes forces a metadata refresh under the hood, similar to how auto-refresh gets triggered in dataflows. Then try reconnecting via SSMS or Power BI Desktop.

If my response has resolved your query, please mark it as the "Accepted Solution" to assist others. Additionally, a "Kudos" would be appreciated if you found my response helpful.

Thank you

v-dineshya's avatar
v-dineshya
Community Support
1 year ago

Hi HarderT ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

 

Thank you.

  • HarderT's avatar
    HarderT
    Helper II
    1 year ago

    Hi v-dineshya ,

     

    we are trying all your steps, but none of them works.

     

    We have recreated everything, but now we have the problem that when we create a new semantic model and change the connection in the Powerbi report, it creates a new report and does not overwrite the old one.

    • v-dineshya's avatar
      v-dineshya
      Community Support
      1 year ago

      Hi HarderT ,

      I have suggested all the possible solutions. I recommend opening a Microsoft support ticket so they can trace the issue. To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:

      How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

       

      If my response has resolved your query, please mark it as the "Accepted Solution" to assist others. Additionally, a "Kudos" would be appreciated if you found my response helpful.

      Thank you

       

      • v-dineshya's avatar
        v-dineshya
        Community Support
        1 year ago

        Hi HarderT ,

        We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?

        If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community.

         

        Thank you for your understanding and participation.