![]() ![]() ![]() If the Storage Engine is not taking much time then it is the Query Processor which is making things slow, in that case you need to focus on optimizing the MDX queries. In this case you need to optimize the dimension design, design of the aggregations and create partitions to improve query performance (discussed in details in next tips in this series). If most of the time is spent in the Storage Engine with long running Query Subcube events, the problem is more likely with the Storage Engine. Formula Engine = Total execution time (Query End event) - Storage Engine time (A).Storage Engine Time = Add elapsed time for each Query Subcube event.To understand this you can use SQL Server Profiler and capture certain events which will tell you the time taken by these components for a cold cache (empty cache, to learn more about cache warning refer to the next tip in this series): ![]() While troubleshooting you need to understand which component is taking more time and needs to be optimized such as the Query Processing Engine or Storage Engine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |