Quotas are separate by storage
IaGenify reports usage and included capacity separately for NoSQL Database, SQL Database, and Object Storage. A full storage can reject writes even while another storage in the same account has available space. This separation helps keep each service's usage and limits visible instead of combining unlike data stores into one pool.
Database add-on space is shared by the account's NoSQL and SQL databases, while object storage add-on capacity is tracked separately. Check the usage for the specific service that is failing before buying an add-on or changing a plan; adding database capacity will not resolve an object storage quota error.
Free space or add capacity in the affected service
If a particular storage is full, remove data that is no longer needed from that storage or choose an add-on that matches its service type. Before deleting objects or database records, confirm the target and preserve a backup if the data may be needed. Deletion and quota changes affect the selected storage, not all account storage at once.
Use the account's current usage report to confirm the relevant quota, because available capacity and plan allowances can vary. If writes still fail after usage appears below the limit, inspect the exact error and refresh the usage view before retrying. Do not move or remove data from an unrelated storage expecting it to free space in the affected one.