Re: billing cpu usage of a monthly basis

Instead of billing by CPU cycles, have you thought about billing by other statistics, such as 'user calls' or I/O rates? Not all db transactions are created equally and some will consume more CPU than others. But then again, not all db transactions will consume I/O rates equally.

HTH,
Brian

Hans de Git wrote:
>
> Hi,
>
> We're planning to consolidate a large amount of our production
> database into one database. Our customers will be charged based on
> their use of the central machine's resources (other suggestions are
> very welcome). I saw a method of keeping track of resource usage, by
> means of the auditing mechanisms in Oracle:
> - drop the sys.aud$ table
> - create a new audit table in another schema
> - provide sys with a synonym or view for that newly created aud$
> - build a trigger which recognises logon and logoff.
>
> I assume that'll work just fine. However, I'm not sure how to charge
> our customer for aborted sessions.
>
> Any suggestions are very welcome.
>
> HTH,
> Hans de Git

-- 
===================================================================

Brian Peasland
dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"