Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
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.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!