|
|
|
|
|
Thank you DBSophic and Ami Levin for an incredible real-world performance tuning product! - Greg Swanson, Senior Solution Architect, NWP
- Kurt Hadermann, CIO, SmartFreightWare
- Matthew Gordon-Box, Senior Consultant, K3 Business Technology Group
- Christoph Weber, Head of Application Development, SUPER RTL
- Yaniv Etrogi, Production Environment Manager, SuperDerivatives
- Doron Yitzhaki, CTO, Clalit Health Services
- Shmuel Witman, VP of Development, Retalix |
In our scenario we have used Qure Analyzer to compare workloads for different iterations in our project. We had multiple rounds of testing. First we collected a baseline trace from our workload replay. Then we changed some clustered keys and collected another trace. Next a trace was collect after introducing table partitioning on top of the clustered key changes. Last we enabled SQL Server compression and collected yet another trace. Since we used the same workload replay we were able to have a side by side visual comparison of what executed and chose the best solution for us. I would recommend this tool to all database professional to make this a part of there optimizing tool set. Wonderful job DBSophic keep up the good work. - Erik Larson, BI Developer, Kaplan Inc.
During the series of incidents caused by the locking issue, the situation was escalating. Despite two 3rd parties and more than a couple of high profile managers being involved I was called on to look into the issue too. Within 20 minutes, I was able to have created a SQL Profiler trace, have it analysed by Qure Analyzer and quickly identify the offending query and illustrate what parameters had been used in the call and the effort involved by the SQL Engine in page reads, CPU, etc. From that I was able to advise what changes could be made to improve the performance and reduce the locking. That was it, I was done. It was (unofficially!) claimed that I’d achieved more in that 20 minutes than the 3rd parties had achieved in all the time they were working on the problem. Qure Analyzer had certainly achieved what it sets out to do and saved us hours of manual trace file analysis. - Steven Jones, SQL Database Analyst
- Doug Bernhardt, Medtronic
97 minutes it took for a crawling/scanning process to complete on our database. - Johan Kanselaar, Senior Software Engineer, Imtech ICT Integrated Solutions
Ami must be very proud! - John Alan |