February 5, 2011 at 12:18 pm
Comments posted to this topic are about the item Let the optimizer drive
February 6, 2011 at 2:25 am
I'm not sure I understand how the query optimizer can fix up a poor performing query just by letting it figure out the problem and fixing it. I've never seen that happen, so I just don't believe it is possible. Especially when I analyze the schema, think about what the query is doing. Realize what is wrong. Change the query and get immediate improvement in performance. Run a quick query and verify my query is 50 to a 1000 times faster. (Does the same thing, but aborts itself within seconds to not impact the production system.)
I then let the existing production code continue ineffectively cleaning up the data a few days, while I report back to the developement team about the pour performing query, how to fix it, and why it will fix it. They take my suggestion, apply it to their production code after doing their own tests.
About this time the "daily" update process is running 3 days straight before the job finishes. We stop the job, apply the updates and restart the job. It takes 3 hours to complete the updates to catch up with the backlog. The daily update runs in 1 hour.
Sorry, understanding the schema, optimizing the query to take advantage of the schema trumps a pour performing query every time.
February 6, 2011 at 9:46 am
Hi Ken, if you wish I've some samples where QO can and do change your queries to get better performance...
I think the main point about this topic is to understand what is happening, and why something is not good for performance (in terms of code optimization).
I agree that sometimes is hard to apply change in a production environment, but unfortunately that’s life ?. But this still cheaper than an hardware improvement.
Cheers
[]s
Fabiano Amorim
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply