Besides user diskspace quota's, I'd be interested in knowing how you guys handle database quota's (MySQL, Postgres, et al.).

Erik

Our system is somewhat flexible for the end user.

We allow them to monitor thier disk usage (mysql, files, etc.) through our control panel..

Then at the end of the month, we have a script that goes through all the accounts, and checks for over usage (bandwidth, or file space) and bills them appropriately (if there is any)...

Our admin panel also has a section which allows us to monitor accounts.. We keep an eye out for certain accounts that we know are database heavy - and send out emails if the customer needs to add more disk space.

This may not be the best solution.. but seems to work well for us.

That's seems like a fair policy. Users can view both their personal directory disk usage and MySQL usage in their cp. I can easily modify my admin view to monitor user database usage. Thanks for the insight.

Erik

Originally posted by AudiBoy
Then at the end of the month, we have a script that goes through all the accounts, and checks for over usage (bandwidth, or file space) and bills them appropriately (if there is any)...



This solution basically works on the belief that you get new clients only on the 1st of the month. right? or do you grant your users the extra time if they signup on the 2nd? :)

Kunal

Well, when it comes to bandwidth - you are correct, the time difference is taken into consideration... But with storage space, Megabytes aren't time dependent...