Disable inserts/updates for databases once a user reaches their quota
Open Discussion
Like Disk quota (MB) , but for mysql size
And other function ... send email when near to limit
I think this 2 features will be usefull
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
I think having a MySQL quota would easily break MyISAM tables, and possibly InnoDB as well when the user reaches the limit.
I think having a MySQL quota would easily break MyISAM tables, and possibly InnoDB as well when the user reaches the limit.
I think that this can be achieved removing INSERT privilege from all MySQL users (including cPanel user) after defined disk quota was exceeded.
This option can be defined under every package, mysql INSERT privilege will be disabled when client account or mysql database hit defined limit. So option can be: after hitting defined account disk space limit, after hitting 50% (or any other defined percent) of disk space limit or another option after hitting defined limit just for mysql disk usage.
This will not break any MySQL dabatases/tables as we will only disable inserting new data into MySQL database. And this will successfully prevent using 1GB or more MySQL space under account that was limited to 100MB.
Then, after account or mysql disk space usage was lowered or account upgraded to bigger package just enable back INSERT privilege.
Additionally, temporary remove INSERT privilege from "cPanel -> MySQLDatabases" while disk usage was over defined limit, to prevent creating new mysql user with INSERT privilege that will override existing users or modifying existing user privileges.
I think that this can be achieved removing INSERT privilege from all MySQL users (including cPanel user) after defined disk quota was exceeded.
This option can be defined under every package, mysql INSERT privilege will be disabled when client account or mysql database hit defined limit. So option can be: after hitting defined account disk space limit, after hitting 50% (or any other defined percent) of disk space limit or another option after hitting defined limit just for mysql disk usage.
This will not break any MySQL dabatases/tables as we will only disable inserting new data into MySQL database. And this will successfully prevent using 1GB or more MySQL space under account that was limited to 100MB.
Then, after account or mysql disk space usage was lowered or account upgraded to bigger package just enable back INSERT privilege.
Additionally, temporary remove INSERT privilege from "cPanel -> MySQLDatabases" while disk usage was over defined limit, to prevent creating new mysql user with INSERT privilege that will override existing users or modifying existing user privileges.
How would implementing this feature beneficial to your business?
How would this add value to your customers?
How would implementing this feature beneficial to your business?
How would this add value to your customers?
It would benefit customers by ensuring a reliable service for them.
It would benefit customers by ensuring a reliable service for them.
I'd love this feature as well - I happen to have customers that tend to have a lot more SQL activity (inserts/updates) than actual data on disk, so they can grow a lot over the quota.
A customer could even use blobs and store images/other data in the DB to bypass a quota limitation, so blocking INSERT/UPDATE on quota exceeded would be awesome :-)
I'd love this feature as well - I happen to have customers that tend to have a lot more SQL activity (inserts/updates) than actual data on disk, so they can grow a lot over the quota.
A customer could even use blobs and store images/other data in the DB to bypass a quota limitation, so blocking INSERT/UPDATE on quota exceeded would be awesome :-)
Hello,
I'm reviewing this request. While there may be some troublesome situations with revoking permissions, we could approach this from a different angle.
If we added a setting that allowed the administrator to enable automatic account suspension when a user exceeds their quota, would this help solve the problem?
Hello,
I'm reviewing this request. While there may be some troublesome situations with revoking permissions, we could approach this from a different angle.
If we added a setting that allowed the administrator to enable automatic account suspension when a user exceeds their quota, would this help solve the problem?
Replies have been locked on this page!