FAQ
I am unable to insert records into my database. What gives?
If you are on one of JawsDB’s shared plans, you may have breached the database size allotted via your plan. When a database grows larger than the plan allows, INSERT privileges are revoked on the database user until the database is brought back into compliance. SELECT, UPDATE, and DELETE privileges are still available during this time. Once the database size is reduced back under the maximum allowed size, the INSERT privilege will be granted back.
The following can be run against the database or placed into a databite in order to see current database size in MB and whether the account currently has INSERT privileges.
select
s.schema_name
,sp.grantee user
,cast(round(sum(coalesce(t.data_length + t.index_length, 0)) / 1024 / 1024, 3) as char) db_size_mb
,sp.has_insert
from
information_schema.schemata s
inner join
information_schema.tables t on s.schema_name = t.table_schema
inner join (
select
spi.grantee
,spi.table_schema
,max(
case
when spi.privilege_type = 'INSERT' then 1
else 0
end
) has_insert
from
information_schema.schema_privileges spi
group by
spi.grantee
,spi.table_schema
) sp on s.schema_name = sp.table_schema
group by
s.schema_name
,sp.grantee
,sp.has_insert;
I am getting an error saying I have exceeded the ‘max_questions’ resource. What is that?
The ‘max_questions’ value is a limit that is placed on shared plan accounts to help preserve computing power for other shared plan users on the same server. It is essentially a limit on the number of queries that can be executed from that account in an hour. After 1 hour of reaching the limit, the limit will be reset and queries can again be executed.
HINT: Cached queries do not count against the query limit of ‘max_questions’. Taking advantage of the cache is a good way around this limit.
Plan | Max Questions |
---|---|
Single-tenant plans | No Limit |
Kitefin | 3,600/hr |
Leopard | 18,000/hr |
Blacktip | 36,000/hr |
How do I access my database backups?
JawsDB backups are in an Amazon-proprietary snapshot format and must be restored by the JawsDB team. Please see the section entitled Database Backups for more information.
Why do I get an error when attempting to change my plan?
In some specific situations, changing plan requires a manual migration. Please check the section entitled Plan Changes to find out whether this applies to your particular situation.
Does JawsDB support Encryption at Rest?
Encryption at Rest (EAR) is a new feature applying transparent AES-256 encryption to the underlying data storage of a JawsDB database and is available on a subset of our plans. Check the desired plan’s description to see if EAR is supported.