There are a few feature-request for mysql-quota / adding the db-size to the webquota with a lot of votes. In the master-branch is already a function to gather the db-size for a database so this can (easily) be integrated (currently this function is used by the monitor-tool to display the db-size for all (mysql)-databases). But I don´t know how to handle a database (or website, too) which exceed the quota. 1. disable the db - bad idea, the client can´t reduce the db-size to get the limit back to "ok". 2. disable write-access for the db-user - see above 3. disable the correspondig website - the db-size could grow anyway I thinkyou can only send warnings if the size reached the defined limit. Any comments?