Re: Charging for Informix usage

You might want to use the sysuserthreads table in sysmaster to monitor the activity of each users threads and somehow charge by the amount of reading a writing by summing these values across all of the threads the user has. Vic Goldberg wrote: > Folks -- > > I work at a university, where, for all sorts of arcane reasons, we > need to charge back users for usage of the database. We need to make > this reflect our actual costs as much as possible, without going to huge > effort to get the information. The obvious, easy, metric is the amount > of disk space that a user is consuming. This would skew the costs > (probably unfairly) towards a large database vs. a small one, even if > the small one is much more active. > > Does anyone have any suggestions for ways to get information that > would allow me to charge multiple independant users seperately? I don't > need the accounting side, just getting the metrics. One thought is to > set up seperate instances, and track usage for each one, but that would > be less efficient than a single instance with multiple databases. > > Thoughts? TIA! > > Vic > > ---- > Vic Goldberg > Assistant Director, Data Operations, CIT > Cornell University > (607) 254-7441 (Voice) (607) 255-6982 (Fax) > "Do not argue with Dragons, > for you are crunchy and taste good dipped in ketchup. "

Yes but, what if there is an inefficient usage of database? For example running into a sequential scan may result very high reads... And this would be unfair I guess.I'd combine read+writes with connect time and have some kind of a threshold. But, you'll need some coding ... Alkin TEZUYSAL INFORMIX DBA The Beef Man wrote: > You might want to use the sysuserthreads table in sysmaster to monitor the > activity of each users threads and somehow charge by the amount of reading a > writing by summing these values across all of the threads the user has. > > Vic Goldberg wrote: > > > Folks -- > > > > I work at a university, where, for all sorts of arcane reasons, we > > need to charge back users for usage of the database. We need to make > > this reflect our actual costs as much as possible, without going to huge > > effort to get the information. The obvious, easy, metric is the amount > > of disk space that a user is consuming. This would skew the costs > > (probably unfairly) towards a large database vs. a small one, even if > > the small one is much more active. > > > > Does anyone have any suggestions for ways to get information that > > would allow me to charge multiple independant users seperately? I don't > > need the accounting side, just getting the metrics. One thought is to > > set up seperate instances, and track usage for each one, but that would > > be less efficient than a single instance with multiple databases. > > > > Thoughts? TIA! > > > > Vic > > > > ---- > > Vic Goldberg > > Assistant Director, Data Operations, CIT > > Cornell University > > (607) 254-7441 (Voice) (607) 255-6982 (Fax) > > "Do not argue with Dragons, > > for you are crunchy and taste good dipped in ketchup. "