Hi,

i am facing a scenario like this,

i am having a table having around 1 million rows, and 15 columns.
This is the logging table, mostly insertion only happens.
the query we use from front end uses almost any one or two of the 10
columns in the where condition.
since it a log table and insertions are heavy, i cant create index for
all the columns.
Need some alternate solution.

Regards
Ram

ramprakash wrote:
And we need more information. Please post DDL, versions and some
typical queries.

Cheers

robert

Hi,

Its oracle 9i release 2, running on windows box.
if i need to create index,
i have to index all the columns because, where condition in the select
query contains almost all the columns.

for example take the emp table
one of the query where condition is NAME in another hiredate , mgr ...

Regards
Ram

On 20 Mar 2006 07:04:05 -0800, "ramprakash" <ramprakash.a (AT) gmail (DOT) com>
wrote:

So you believe full table scans are bad. When in the previous
milennium did you learn Oracle, or read the performance tuning manual?
Or do you like to believe fairy tales?

--
Sybrand Bakker, Senior Oracle DBA

Take a copy of the table to a test table.

Create indexes until you are happy. Or, probably drop indexes until
you are happy.
More indexes mean slower insert.

No indexes, faster insert.
Try gathering stats on the table... that may or may not improve
performance depends on what is there.

test test test
Then test again.

And finally one last test before you test it just before putting it
into production.