Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I read a post where the writer said that OData is slower than a Direct Query of SQL Server data. I was wondering if the majority of people agree with it or if it's just a known fact. If it is, is there a reason you would choose OData if given the choice of both methods?
Hi @ASQLGuy,
They are two different things that are used in different scenarios.
1. OData can't act like Direct Query. We don't need to store data locally when using Direct Query.
2. OData is a protocol which is usually used in web service while Direct Query is a connection method.
I think Direct Query is faster. Because Power BI send queries directly into the database. It's obvious we can't do this with OData.
Reference: http://www.odata.org/getting-started/understand-odata-in-6-steps/
https://docs.microsoft.com/en-us/power-bi/desktop-use-directquery
Best Regards,
Dale
According to OData spec and experience, OData allows select, where, group (v4), etc. so it is possible to formulate many SQL queries as effectively in OData.
User | Count |
---|---|
76 | |
75 | |
46 | |
31 | |
27 |
User | Count |
---|---|
99 | |
91 | |
51 | |
49 | |
45 |