Webcast: Avoid Slow SSAS Queries: MDX Query Troubleshooting
Do you have SSAS queries that you feel should be faster? Multidimensional Expressions, or MDX, is the language used to work with Analysis Services. Similar to SQL for the relational engine, MDX is a language for queries and DDL statements on multidimensional cubes in Analysis Services. Troubleshooting slow MDX queries is often challenging because the level of support provided by the tools and the Analysis Services engine is not as mature as that found in the relational engine. This session covers the methods for examining slow queries using the SQL Profiler and Performance Monitor to determine the need for aggregations, caching problems, memory constraints, and so forth. Best practices for optimizing MDX will be examined, and various server properties will be discussed as necessary to help correct query issues. Attendees will leave armed with a practical approach to locating bottlenecks and strategies for speeding up queries.
> Register Now
> Live date: 4/28/2010 at 12:00 Pacific
Interested in Learning About SQL Server Security?
Check out our upcoming virtual workshop! In the workshop, we’ll be going through things to know, SQL Server injection protection, overall security and best practices information and a lot more. This is not a sales presentation, it’s all technical and is several hours long – we’ll be covering a lot of ground (yes, there are breaks). At the end of the workshop, you can review materials, take the quiz and get a certificate for completing it.
I’ll be available throughout for live Q&A and to make sure it all makes sense.
This workshop is brought straight to your desktop and is practical, applicable information you can use immediately.
I hope to see you there – make sure you register here and save the date!
Interesting Question from DBASchool
One question (of many) that really stood out at this week’s DBASchool centers arround the accidental DBA and the various things to keep track of. This question, "What do I need to be doing on a daily basis," was a killer question. It sort of brought everything together and had me building out new presentations that answer this specific question.
To me, if you’re not full-time taking care of the databases, you’re faced with automating as much as possible, setting up alerts to make sure your automation is working, then dealing with the exceptions as they pop-up.
If you find yourself working with and supporting SQL Server on a part-time basis, what items are on your "must check" list on a *daily* basis? Are there thigns that need your attention daily, or do you have everything automated?
How are you approaching this? Let me know in an email, I’d love to hear your approach.