Forum Discussion

manoj_0911's avatar
manoj_0911
Kudo Commander
2 months ago
Solved

Can a report using DirectQuery to a Power BI Semantic Model generate SQL queries against the underly

Can a report using DirectQuery to a Power BI Semantic Model generate SQL queries against the underlying database?

 

Hi Community,

I am investigating a SQL Server deadlock issue and need clarification on the query flow.

 

Current architecture:

SQL Server → Power BI Semantic Model ("LOS QUEUE SUMMARY & DETAIL REPORT") → Power BI Report

 

semantic model is configured as Import mode

 

The report's Data Source Settings show:

"DirectQuery to AS - Power BI Semantic Model"

 

My understanding is that the report is connected to the semantic model and not directly to SQL Server.

 

My questions are:

  1. If a report uses DirectQuery to a Power BI Semantic Model, does report activity (filters, slicers, page loads, etc.) send queries to the underlying SQL Server database?

  2. If the semantic model is Import mode, can report usage still generate SQL Server activity outside of dataset refreshes?

  3. Could report activity from reports contribute to SQL Server deadlocks if the semantic model uses DirectQuery?

I am trying to determine whether usage of a report connected to our semantic model could be contributing to database deadlocks.

 

Thanks in advance.

  • Hi manoj_0911  - if the semantic model is truly 100% Import mode, report usage is unlikely to be the source of the SQL Server deadlocks, and the investigation should focus on dataset refreshes or other processes accessing the database.

    If the semantic model is configured as Import mode, those queries are answered from the in-memory VertiPaq cache, not from the underlying SQL Server database.

    Semantic model modes in the Power BI service - Power BI | Microsoft Learn

    Hope this helps. 

     

  • manoj_0911 

     

    Your understanding is correct.Your understanding is correct. Import mode means report activity never touches SQL Server.

    1. No. "DirectQuery to AS" means the report queries the Analysis Services model, not SQL Server. The model is the report's data source.
    2. No. After refresh, all report queries hit the in-memory cache. SQL Server only sees activity during refresh.
    3. No, not from report usage. Only the model refresh hits SQL Server.

4 Replies

  • Hi manoj_0911  - if the semantic model is truly 100% Import mode, report usage is unlikely to be the source of the SQL Server deadlocks, and the investigation should focus on dataset refreshes or other processes accessing the database.

    If the semantic model is configured as Import mode, those queries are answered from the in-memory VertiPaq cache, not from the underlying SQL Server database.

    Semantic model modes in the Power BI service - Power BI | Microsoft Learn

    Hope this helps. 

     

  • manoj_0911 

     

    Your understanding is correct.Your understanding is correct. Import mode means report activity never touches SQL Server.

    1. No. "DirectQuery to AS" means the report queries the Analysis Services model, not SQL Server. The model is the report's data source.
    2. No. After refresh, all report queries hit the in-memory cache. SQL Server only sees activity during refresh.
    3. No, not from report usage. Only the model refresh hits SQL Server.

  • v-hjannapu's avatar
    v-hjannapu
    Community Support

    Hi manoj_0911,

    I would also take a moment to thank Kedar_Pande  , rajendraongole1  for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
     

    I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

    Regards,
    Community Support Team.

    • v-hjannapu's avatar
      v-hjannapu
      Community Support

      Hi manoj_0911,
      I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We are always here to support you.


      Regards,
      Community Support Team.