Service limitations of MySQL Database on Azure

This article discusses the current service limitations of MySQL Database on Azure. If you have any questions, contact technical support.

The limitations include:

  • Because MySQL Database on Azure uses the customized user-account authentication plug-in, you can create a user account only in the Azure portal, and you cannot create a new database user account directly by using the SQL command line.
  • You can create databases only by using the Azure portal. Creating databases directly by using the SQL command line is not supported.
  • Users do not have shutdown permissions, and so you cannot shut down MySQL database servers.
  • Users do not have super permissions, and so you cannot change any global variables, for example.
  • Users do not have file permissions. For more information, see MySQL 5.7 user permissions.
  • The MySQL built-in system tables do not support write permissions. The following tables do not currently support read/write permissions:

    • columns_priv
    • db
    • general_log
    • host
    • ndb_binlog_index
    • plugin
    • procs_priv
    • servers
    • slow_log
    • tables_priv
    • user
    • proxies_priv
  • The MyISAM storage engine is not currently supported, and so we suggest InnoDB for users, although other available non-InnoDB engines might cause problems under certain conditions.

  • Because of differences in cache architectures, we do not currently offer support for downgrading MP (for example, MP1 or MP2) directly to MS (for example, MS6). If you do need to downgrade from MP to MS, you can do so by using the backup and restore method. That is, you can restore the full backup of a particular MP instance to an MS instance.