Forum Discussion
Can Storage Engine answer Simple Queries Independently?
- 2 years ago
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.
additionally a good way to understand what the storage engine does and what the formula engine does is it to play with it in dax studio and run queries to get a feel for it, its a lot of information. Its one of my favourite things to spend hours on š
effectively the formula engine and storage engine(s) work together, but they each have their own 'jobs'.