Reputation
270
Top tag
Next privilege 300 Rep.
Create new tags
Badges
1 6 20
Impact
~47k people reached

  • 0 posts edited
  • 0 helpful flags
  • 29 votes cast
Apr
3
awarded  Notable Question
Jan
7
awarded  Popular Question
Oct
14
awarded  Notable Question
Aug
10
awarded  Notable Question
Mar
2
awarded  Autobiographer
Feb
18
awarded  Popular Question
Dec
22
awarded  Popular Question
Nov
12
awarded  Popular Question
Sep
12
awarded  Notable Question
Jul
21
awarded  Popular Question
Jul
12
awarded  Famous Question
Jul
2
awarded  Curious
Jun
3
awarded  Popular Question
May
8
awarded  Critic
Sep
19
awarded  Popular Question
Sep
5
awarded  Popular Question
Jun
6
comment Index on foreign key makes query extremely slow
@JackDouglas, yes that was my first thought when I saw the improvement. I think a weekly job should do it.
Jun
6
accepted Index on foreign key makes query extremely slow
Jun
6
comment Index on foreign key makes query extremely slow
@JackDouglas, yes this is how I understoood it now. I have ran another query with this range scan only. It performs fast, returns 1.14 million rows but still has overall costs of 26212. So this is simply the root cause. Since your answer led me into the right direction. It deserves an accept.
Jun
5
comment Index on foreign key makes query extremely slow
@JackDouglas, I am not using the hint. It was just used to see how the query would perform with the index after gathering stats. Getting back to the table, it has more than 60 millions rows. Probably that range scan makes the search extremely slow -- even with an index. I can attached a fully expanded tree. Will that help somehow? I narrowed it down to the important spot. Regarding the cardinalities, how can I enable this in SQL Developer? Thank you very much for the tips.