Actually, if you're doing a *lot* of inserts without bind variables, try
shrinking your shared pool. You'll be parsing everything anyway and that way it
takes less time to fail the hashtable lookup.
I have such a beastie, and this works for me -- it was able to roll over a 200M
shared pool in ju
Lisa Koivu asked about:
I am thinking of just implementing a schema in my current database
for this purpose and making the table as quick for inserts as possible
(no primary key, minimal indexing, PCTUSED set appropriately, etc.)
Lisa,
I recently did the exact same thing:
created a schema fo
Title: One Database, Multiple Apps
Hello all -
I have one medium-large production database here. Our system is hybrid but more similar to OLTP. As far as I know quick inserts are not a problem.
I need to implement tracking software, where all I'd have to do from the database side is
Lisa,
One of the biggest advantages that jumps right out is the user administration at the
OS level. One login can get the user to more than one application/instance. At the
Oracle level you have all of your scripts on one server and that makes it easier to
manage the database. It's not the q
