Forum Discussion

supton's avatar
supton
Helper I
9 years ago
Solved

Poor Performance using Azure SQL Database and Direct Query

Hello! I was just wondering if anyone else has experienced very poor performance using Direct Query on an Azure SQL Database. I have limited the number of rows that I am using in my queries but this ...
General Comment
Need Help
  • Anonymous's avatar
    Anonymous
    9 years ago

    supton,

    I am afraid that there is no way around this. Generally speaking, import models will be faster, and 500 thousand rows is not a large dataset, it is recommended that you use “Import” mode to import data to Power BI.

    Regards,
    Lydia

supton's avatar
supton
Helper I
9 years ago

I understand. This was the route which I took initially. But I was unable to schedule a refresh because of the largest table (which was 1.5 million before it was split). The refresh took too much time, and the scheduled refresh would crash because of this. It would take over an hour to process any refresh of the data on my local machine.

Anonymous's avatar
Anonymous
Not applicable
9 years ago

supton,

Do you still encounter the performance issue after you use In-Memory technologies ?

Regards,

  • supton's avatar
    supton
    Helper I
    9 years ago

    I refactored to use import from azure and it seems to work fine now. The Dynamics 365 Connector must just be quite slow then because I previously was using the same data but it would error out because it would take to long. Anyways, all good now. Thanks!