Frequently Asked Questions (FAQs)

Use the Change Plan menu on the Settings tab to scale your cluster up. To scale a cluster down, migrate or fork it to a new, smaller cluster.

You cannot create superuser accounts. To create a standard user account, use the Vultr Customer Portal.

A cluster can only have one primary node, but you can assign multiple replica (read-only) nodes.

Yes, you must use primary keys for all database tables, which is enforced through the database configuration.

Yes, all managed databases are backed up for disaster recovery purposes. In addition, all plans other than Hobbyist offer user-initiated recovery, forking, and point-in-time backups. You can use these backups to restore a cluster, which overwrites the current cluster's data. You can also fork a cluster from the backup, creating a new cluster with the backup data and not modifying the existing cluster. You'll find those options in the Actions section of your cluster's information page.

MySQL databases offer point-in-time recovery history; the duration available depends on your node plan.

• Premium: 30 days
• Business: 14 days
• Startup: 2 days
• Hobbyist: None

You can deploy managed databases in several node plans, which are a shorthand way of identifying the available size and number of nodes. We offer Hobbyist, Startup, Business, and Premium node plans.

After you deploy a managed database, look in the General Information section of your cluster's information page. The Node Plan appears below the Monthly Price. The plan name format is Vultr-Dbaas-[plan type]-[other internal information].

The node plan determines what backup and recovery options are available.

Yes, you can use the Vultr API or Vultr CLI to provision a managed database for MySQL.

Vultr's managed database clusters use the latest MySQL version.

Yes. MySQL can operate in different SQL modes. You can apply these modes in the database server's Settings tab through the Vultr Customer Portal. See the MySQL documentation to learn more about SQL modes.

Notes about MySQL Modes:

• The ANSI (Combination Mode) SQL mode includes the following SQL modes: REAL_AS_FLOAT, PIPES_AS_CONCAT, ANSI_QUOTES, IGNORE_SPACE, and ONLY_FULL_GROUP_BY.
• You can toggle some modes individually, but if ANSI (Combination Mode) is enabled, that setting will take precedence. For example, if you want to disable ONLY_FULL_GROUP_BY, you will also need to disable ANSI (Combination Mode) because it is a part of that mode bundle.
• According to the MySQL documentation, TRADITIONAL (Combination Mode) includes the following SQL modes: STRICT_TRANS_TABLES, STRICT_ALL_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, and NO_ENGINE_SUBSTITUTION.
• We do not support the NO_BACKSLASH_ESCAPES or PAD_CHAR_TO_FULL_LENGTH SQL modes at this time.

Some features that you cannot set globally can be enabled per session. For example, you cannot set binlog_row_value_options = partial_json globally, but you can set it per session using the following command:

SET SESSION binlog_row_value_options = partial_json;

Users cannot change MySQL database properties or use the root user for cluster stability. However, you can view the database properties with the SHOW VARIABLES; SQL query.