asked on

Oracle Performance

I am using TTables to hold a vendor table in Oracle. Everything was fine until the user dumped 55000 records into it. Now it takes 75 seconds to post my purchase orders. (was <5 seconds) I don't understand the connection. The vendor is simply a field in the purchase order table. Anyway, is there anyway to tweek the database so posting is faster?

(One example was to include not null on fields that indexes during table creatation. Apparently, Oracle will ignore the index if it finds a null.)

JoeBooth

You should use tQuery instead of tTable when you are accessing an ORACLE server.

Are you familar with SQL?

CalvinDay

ASKER

I've heard that before. And, I am familar with SQL. However, I seem to have problem with it being updateable.

Also, the table are connected in master/detail situation. Could this be a problem?

JoeBooth

When you design a query, you should assume it will not be updatable. I typically have a query called WORKQUERY which I use for all my UPDATE and INSERT statements.

When a change needs to be recorded, write the SQL in the Workquery and use the ExecSQL method, rather than relying on the table to update it.

The master detail could be the problem, it depends on how the Oracle schema is defined. If you have a cascading updates option, what appears to be a single row update could actually be updating a large number of records.

ASKER CERTIFIED SOLUTION

kretzschmar

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

CalvinDay

ASKER

Good comments.

CalvinDay

ASKER

BTW

>(i can send you sample how to configure it)

please do send > calvin@data-trak.com

kretzschmar

hi cal,
sorry, didn't forget you,
sample comes in ~9 hours
(must search it first)
meikl