Parallel Queries

Hi,

I have one point to discuss, please help me if you have experience or correct if I am wrong.

I am currently working with a huge database (about 1.5 billion records).

The database runs on a powerful Sun machine, has tons of RAM, Disk Arrays, other wonderful stuff and costs a zillion dollars.

Currently, parallel queries are active and, every time I run a query, the system creates 22 different sessions to gather data quickly and efficient.

We have used partitioning, paralellism, etc and I can say that the database is optmized to run about 90% of the queries.

However, some queries take a long time, no matter how good is your SQL statement (explain plan).

Since most queries have date periods as main criteria, I was wondering if it would be a good idea to create a different connection and, for example, have 2 different connections working on different date periods at the same time.

I would be responsible for joining the results and produce a consistent table or view (probably by using Access). The common sense leads to think that 2 different connections would create 44 sessions instead of 22.

Since the machine has some idle power, I think it would double the parallelism.

It it correct? Has anyone tried that before?

Thanks in advance, Received on Tue May 29 2001 - 05:43:08 CDT