Good one!

We can actually use "cache" because there are 100,000 + hits a day on this
procedure, and we are just looking for a magnitude. We are not concerned
about absolute precision or "losing" values because they are not used for
keys. Getting within 1% of the true number would be completely
satisfactory.

Thanks,

Udi

This message and any files or text attached to it are intended only for
the recipients named above, and contain information that may be
confidential or privileged. If you are not an intended recipient, you
must not read, copy, use, or disclose this communication. Please also
notify the sender by replying to this message, and then delete all copies
of it from your system. Thank you.




"Chamberlain John "
<oracledba-ezmlmshield-x2329187.[Email address protected]
12/28/2005 07:23 AM

To: "LazyDBA Discussion" <[Email address protected]
cc:
Subject: RE: counting hits in an application


Why not use a sequence?

This assumes you do not need 100% accuracy, but this will be pretty close:

Create sequence app_counter nocache;

(Note with nocache there could be contention issues if the proc is heavily
called, so you may want to use a cache. However, with cache, you lose all
cached values if the database is restarted and also the last_number in
dba_sequences will reflect the highest number cached)

Then insert in procedure (or app code):

Select app_counter.nextval from dual;

Then you can set up a process (dbms_job or cron job) to query
dba_sequences
and record its value:

Select last_number from dba_sequences where sequence_name="APP_COUNTER";

HTH!!


-----Original Message-----
From: Udi [mailto:oracledba-ezmlmshield-x34036238.[Email address
protected]
Sent: 28 December 2005 00:29
To: LazyDBA Discussion
Subject: Fw: counting hits in an application

Thanks! sounds just like what we need. We will explore.

Thanks,

Udi

This message and any files or text attached to it are intended only for
the recipients named above, and contain information that may be
confidential or privileged. If you are not an intended recipient, you
must not read, copy, use, or disclose this communication. Please also
notify the sender by replying to this message, and then delete all copies
of it from your system. Thank you.


--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html

-----------------------------------------
Information in this email may be privileged, confidential and is intended
exclusively for the addressee. The views expressed may not be official
policy, but the personal views of the originator. If you have received it
in error, please notify the sender by return e-mail and delete it from
your
system. You should not reproduce, distribute, store, retransmit, use or
disclose its contents to anyone. Please note we reserve the right to
monitor all e-mail communication through our internal and external
networks.



--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these terms:
http://www.lazydba.com/legal.html



Oracle LazyDBA home page