|
|
|
|
|
|
| Re: performance related issue in discoverer report [message #277758 is a reply to message #277122] |
Wed, 31 October 2007 06:59   |
skooman
Messages: 913
Registered: March 2005
Location: Netherlands
|
Senior Member |
|
|
| abhishekpaliwal24 wrote on Mon, 29 October 2007 01:04 |
it is taking 2.5 hours when i m running in sql editor
|
Well, how do you expect Discoverer to do this any faster then? You're just lucky that it's faster if you use parameter values. Perhaps it's just a whole lot of data to select without any where clauses?
If the problem is that you need all the data (so, you don't want to use parameter values), and you feel it whould give the result faster then in 2,5 hours, then please post the SQL statement and explain plan here, we'll have a look at it (or forward it to the performance forum). Also please describe your data and the expected resultset (how many rows).
As for the LOV: same thing, if it's a lot of data, it will take some time to give the values. However, with LOV's there is something you have to check. Sometimes, you see in an EUL that the LOV is based directly on the "main" source table. So, let's say I have some table containing millions of rows, and in that table there is a column that only contains 10 different values. If, in Administrator, I select that column and choose create item class (and LOV), than everytime I use that LOV, the database has to go through those millions of rows only to find 10 different values. That's ridiculous of course. So, you'll have to find a clever way to create a "lookup table" (or something from dual) to only store or generate these 10 values and create the LOV on that one.
Regards,
Sabine
[Updated on: Wed, 31 October 2007 07:01] Report message to a moderator |
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
