Forum Discussion
Can Storage Engine answer Simple Queries Independently?
Both EnterpriseDNA and SQLBI agree that Storage Engine (SE) deals with simple queries, SE is faster and use multiples cores, it has a limited/basic functions as mentioned but it can filter, join and summarize very well. EnterpriseDNA says SE can handle them alone, while SQLBI adds that SE deals with different types of queries and gives the data to Formula Engine (FE) for further work. FE can handle sophesticated and complex calculations over the data cache (raw data) retuned by SE, it's singles threaded (slower).
Yes, when FE figures out the best way to handle a query, it can let Storage Engine (SE) do the actual work because SE is good at it.
When EnterpriseDNA says "SE can do it all by itself," it means SE can handle simple queries alone without relying too much on Formula Engine (FE), such as when there are no callbacks. It doesn't skip FE but shows SE can manage simpler tasks independently, whether it's using in-memory or compressed data. SE returned non compressed data into data cache from the vertipacq engine.
Both EnterpriseDNA and SQLBI agree that Storage Engine (SE) deals with simple queries, SE is faster and use multiples cores, it has a limited/basic functions as mentioned but it can filter, join and summarize very well. EnterpriseDNA says SE can handle them alone, while SQLBI adds that SE deals with different types of queries and gives the data to Formula Engine (FE) for further work. FE can handle sophesticated and complex calculations over the data cache (raw data) retuned by SE, it's singles threaded (slower).
Yes, when FE figures out the best way to handle a query, it can let Storage Engine (SE) do the actual work because SE is good at it.
When EnterpriseDNA says "SE can do it all by itself," it means SE can handle simple queries alone without relying too much on Formula Engine (FE), such as when there are no callbacks. It doesn't skip FE but shows SE can manage simpler tasks independently, whether it's using in-memory or compressed data. SE returned non compressed data into data cache from the vertipacq engine.
Thanks Fowmy
Your answer helps with Q2 & Q3
I'll see if someone else responds to Q1- or else marks yours as an answer
From your overall comment, for Q1, I feel the word "Answer" is an inapt word by EnterpriseDNA, it supplies the answer or datacache back to FE- so I will assume SQLBI is using the right terminology there
GulianiG
To answer Q1, The formula engine turns a DAX query into a query plan with steps for execution. Each step corresponds to an operation by the formula engine. Storage Engine (SE) fetches data from the Tabular model and sends it to FE for further calculations. When you asked about "SE answering simple queries,", yes it true, it means SE handles straightforward queries directly for visualization without needing FE for additional calculations. For the second part about "SE providing raw data," it's always true as FE can't access data; SE retrieves and supplies data to FE, regardless of the query complexity.
So, there two statements in the question, both are true.