RE: Large IN LIST in an OBIEE query
- From: Michael Dinh <mdinh@xxxxxxxxx>
- To: "greg@xxxxxxxxxxxxxxxxxx" <greg@xxxxxxxxxxxxxxxxxx>, "Hemant.Chitale@xxxxxx" <Hemant.Chitale@xxxxxx>
- Date: Sun, 30 Oct 2011 14:34:25 -0700
LOL - I asked the same question.
Would it surprise you to know the IN list is from querying against the tables
in application schema?
________________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx [oracle-l-bounce@xxxxxxxxxxxxx] On Behalf
Of Greg Rahn [greg@xxxxxxxxxxxxxxxxxx]
Sent: Sunday, October 30, 2011 1:13 PM
To: Hemant.Chitale@xxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Large IN LIST in an OBIEE query
I know there have been numerous comments on possible solutions thus
far, but I'm going the opposite direction (not *what* is being done,
but *why* it's being done):
Where does this list come from?
It's probably safe to say no user keys in 1000 values, so do they have
their own discrete list they copy/paste or is it a hard coded discrete
list in OBIEE?
Either way, it seems it would make more sense to have that in a table,
which seems to avoid the problem you observe, no?
On Fri, Oct 28, 2011 at 1:50 AM, Chitale, Hemant Krishnarao
<Hemant.Chitale@xxxxxx> wrote:
> I have a few OBIEE queries that "perform poorly". Apparently, the users
> are allowed to "insert" a list of values to query for. OBIEE then
> constructs the query with a large IN LIST.
> If I move the IN LIST values into a temporary table and then join the
> temporary table, I get better performance. However, making this change
> in OBIEE requires a change to the OBIEE data model.
--
Regards,
Greg Rahn
http://structureddata.org
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
