Help Center> Database Security Service> Service Overview> Database Protection> Constraints
View PDF

Constraints

Database protection is subject to certain constraints.

Supported Database Types

The following types of databases on HUAWEI CLOUD can be protected:

  • RDS instances
  • Databases on ECSs
  • Databases on BMSs

Supported Database Versions

  • Microsoft SQL Server 2008 to Microsoft SQL Server 2014
  • MySQL 5.5 to MySQL 5.7
  • PostgreSQL 9.4 to PostgreSQL 9.5
  • DWS 1.2.3

Restrictions on DDM Usage

When using DDM as a protected database, pay attention to the following restrictions:

  • The database protection instances you purchase should be in the same Virtual Private Cloud (VPC) as DDM.
  • When configuring protected databases in database protection, you need to configure the connection addresses of the DDM instances. Therefore, confirm the number of the connection addresses of the protected DDM instances and the database protection type before purchasing database protection instances. A maximum of eight addresses of a DDM are supported.
  • Currently, DDM supports only some MySQL syntax. For MySQL syntax that DDM does not support, the database protection proxy can forward the data normally, but DDM will return an error.
  • DDM does not support views, functions, and stored procedures. Therefore, database protection does not support views, functions, and stored procedures for DDM.
  • The current database protection version does not support DDM as the log storage location.
  • DDM users are different from those of MySQL. Database protection cannot obtain DDM user list or generate reports about database users
  • The connection between HexaTier and database protection is not encrypted because DDM does not support SSL connections.
  • While a protected database is created, database protection needs to connect to the database by using a DDM account with read permission. You can create the account on the DDM management console.
  • When creating a protected database, the test connection is required for default databases. You need to configure the existing logical database in DDM instances for the test connection.

Other Constraints

  • If you choose RDS as the remote log database, you must change the value of database configuration parameter local_infile to ON (the default value is OFF).
  • If you want to protect an RDS instance, you must change the value of database configuration parameter lower_case_table_names to 1 (the default value is 0).
  • Advanced activity monitoring

    Chinese names of data tables are not supported.

Parent topic: Database Protection