Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
ASQLGuy
New Member

SQL vs OData very different speeds

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? 

2 REPLIES 2
v-jiascu-msft
Microsoft Employee
Microsoft Employee

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

Community Support Team _ Dale
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

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.

Helpful resources

Announcements
July 2025 community update carousel

Fabric Community Update - July 2025

Find out what's new and trending in the Fabric community.

July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.