![]() | |
![]() |
| | Thread Tools | Display Modes |
#61
| |||
| |||
|
|
Which brings us back to the need for hints even for very simple queries - when my question was: "how do you do it without hinting". I don't think we differ conceptually. |
#62
| |||
| |||
|
|
BTW, the IBM position (which may or may not match mine) is that the user tells support (i.e. last resort) that they are stuck and support provides the hint (i.e. no need to wait for a patch). If hints are truly rarely needed then this ought to be an acceptable compromise between idealism and pragmatism. |
#63
| |||
| |||
|
|
BTW, the IBM position (which may or may not match mine) is that the user tells support (i.e. last resort) that they are stuck and support provides the hint (i.e. no need to wait for a patch). If hints are truly rarely needed then this ought to be an acceptable compromise between idealism and pragmatism. |
#64
| |||
| |||
|
|
On 2/13/2011 7:51 AM, Jonathan Lewis wrote: Which brings us back to the need for hints even for very simple queries - when my question was: "how do you do it without hinting". I don't think we differ conceptually. My point is that the hint should supply the missing information (e.g. selectivity) and not dictate the plan. It's still a hint. |
#65
| |||
| |||
|
|
Ultimately it's much harder (and much less reasonable) for the DBA to decide what the right information is for a particular query than it is to know enough to determine a sensible path. |
#66
| |||
| |||
|
|
The funniest part was when Watson said "Harry Potter" when the correct question was "Voldemort." 2880 POWER7 processor cores and 16 Terabytes of RAM, got it exactly backwards in 3 seconds. |
![]() |
| Thread Tools | |
| Display Modes | |
| |