Business volume may surge during large-scale events. This poses significant challenges to database usage and data security. This topic describes how to use Data Management (DMS) to help you sail through the challenges during large-scale events. You can use DMS to evaluate the usage of your database. Then, you can take preventive measures to ensure the stability of your business during large-scale events and prevent economic losses due to a system breakdown caused by database overload.

Background information

During large-scale events, traffic spikes can affect the performance of databases. When you prepare for large-scale events, evaluate the usage of your databases and estimate the access traffic from your customers and developers in your company.

In the following cases, business was affected because the operator and developer did not take preventive measures to prevent system breakdowns during large-scale events:
  • An operator executed slow queries to collect data generated during large-scale events. This results in business failures.
  • A developer executed a schema change statement, which affected an event in another line-of-business that uses the same database.

Configure timeout periods for queries and export tasks

To prevent SQL statements from being executed over a long period, specify a query timeout period and a export timeout period for your database instance in the Edit dialog box of the DMS console. Slow queries may affect your business.

During normal business periods, we recommend that you set the query timeout period to 60s and the export timeout period to 600s. During large-scale events, we recommend that you set the query timeout period to 5s and the export timeout period to 60s.

For more information, see Modify a database instance.

Configure timeout periods for queries and export tasks

Configure the maximum size of tables on which full scans are performed

On the Security Rules tab of the DMS console, set the Limit the maximum allowed SQL full table scan (MB) rule to prevent business interruptions caused by full scans on large tables during large-scale events.

During normal business periods, we recommend that you set the value of the Limit the maximum allowed SQL full table scan (MB) rule to 10240 MB. During large-scale events, we recommend that you set the value to 5120 MB. For more information, see Security rules on the SQL Console tab.

Limit queries

Block high-risk SQL statements

To prevent high-risk SQL statements from being executed, manage high-risk SQL statements, such as data query language (DQL), DDL, DML, and data control language (DCL), on the Security Rules tab of the DMS console. High-risk SQL statements may affect your business.

During normal business periods, we recommend that you allow high-risk SQL statements based on your business requirements. During large-scale events, we recommend that you block high-risk SQL statements such as DDL. For more information, see Security rules on the SQL Correct tab.

Modify approval processes

During large-scale events, we recommend that you add a supervisor or a business-related member in approval processes.

During normal business periods, we recommend that you configure R&D engineers, data owners, and database administrators (DBAs) in the approval process as needed. During large-scale events, we recommend that you configure R&D engineers, data owners, supervisors of the data owners, and DBAs in the approval process. For more information, see Approval processes.

Approval processes during large-scale events

Increase the security levels of sensitive fields

Increase security levels of sensitive fields, such as personal information, mobile phone numbers, ID card numbers, and money. Mask these fields to improve data security. For more information, see Adjust field security levels.

Increase the security levels of fields

Enable the digital watermark feature

Enable the digital watermark feature in the DMS console. After you enable this feature, DMS adds watermarks to the DMS console. Watermarks discourage users from sharing screenshots which may lead to data leaks. For more information, see Add digital watermarks. An example of visible watermarks

Manage data change periods

Allow or forbid data changes to database instances in the specified periods of time in the underlying execution engine.

This feature is unavailable in the DMS console. If you want to use this feature, submit a ticket or contact the customer service in the DingTalk group of DMS.

Seek help

A set of dedicated services are provided for you to get started with DMS. Scan the following QR code by using DingTalk or search for the DingTalk group number 21991247 to join the group.

QR code