Comments on: Proactive Tuning

By: Proactive behaviour « lifeskillsguru

Proactive behaviour « lifeskillsguru — Thu, 19 Jul 2012 13:24:59 +0000

[...] Proactive Tuning (jonathanlewis.wordpress.com) [...]

By: rlivermoRob

rlivermoRob — Fri, 13 Jul 2012 17:54:44 +0000

Set it to 11 “_sql_go_fast=11′, it’s one more than 10.

By: savvinov

savvinov — Fri, 13 Jul 2012 17:06:56 +0000

I think the reason why the word “proactive” is (ab)used so frequently is that it can serve as a euphimism for “I have no idea why I’m doing this”.

By: Jonathan Lewis

Jonathan Lewis — Fri, 13 Jul 2012 10:35:32 +0000

K3nnyp,

True, and echoed in Timur’s article referenced below.
For most people, “proactive” turns out to mean “faster reactive”.

By: Jonathan Lewis

Jonathan Lewis — Fri, 13 Jul 2012 10:33:49 +0000

Timur,

Nice article – thanks for the link.

By: Timur Akhmadeev

Timur Akhmadeev — Fri, 13 Jul 2012 08:48:19 +0000

Here's an article on the same topic appeared in my RSS feed: Proactive vs Reactive: How to prevent problems instead of fixing them faster. Maybe it will be interesting to somebody.

By: k3nnyp

k3nnyp — Thu, 12 Jul 2012 23:34:41 +0000

Unfortunately proactive tuning often refers to tuning before the customer complains or the current bottleneck hits 100%.

By: Noons

Noons — Thu, 12 Jul 2012 21:44:49 +0000

Good grief! I’m surprised that SQL in OTN doesn’t have a DISTINCT in it!!! Can I hire that developer?
WARP_DRIVE indeed! Good old Billy, he’s always good value! :)

By: Marcus

Marcus — Thu, 12 Jul 2012 15:52:59 +0000

> “_sql_go_fast” ? – doesn’t work anymore?
It is deprecated for a long time. The new one is /*+ WARP_DRIVE(9) */
https://forums.oracle.com/forums/thread.jspa?messageID=4333700

Marcus

By: July Reading » Peasland Database Blog

July Reading » Peasland Database Blog — Thu, 12 Jul 2012 15:12:02 +0000

[...] Lewis talks about proactive tuning on his blog. Personally, I’ve never performed any sort of proactive tuning and Jonathan helps me [...]