Docs

Database Workshop

Overview

Limits

Limits

This topic describes the limits of Database Workshop (DBW).

Data retention period limits

Item			Description	Remarks
SQL Window	Execution history	SQL execution history is retained by default for 30 days.	None
Ticket list			Ticket data will be permanently retained.	None
Managing tasks			You can create up to 10 tasks per instance. In a cyclic task, if the execution time exceeds the set cycle, up to 3 executing subtasks can exist under a task at the same time. If 3 tasks are already in progress, subsequent subtasks scheduled for execution will be automatically skipped.	None
Operation Audit	Ticket execution logs	Ticket data is retained permanently.	Null
		Database console	SQL execution logs are retained by default for 30 days.	None
		Operation and maintenance observation logs	Operation and maintenance observation logs are retained for 30 days.	For other retention duration requirements, submit a ticket to contact technical support.
Session Management	Session snapshot list	Conversation snapshots are retained for 30 days. The query time range for snapshots in the list cannot exceed 24 hours.	For other retention period requirements, please submit a ticket to contact technical support.
Slow log			Slow logs are retained for 30 days.	For other retention period requirements, please submit a ticket to contact technical support.
Database Audit Logs	V1	1 day to 3650 days	Configured by TLS
Database Audit Logs		V2	Supports selecting 1 day (default), 7 days, 30 days, 180 days, 1 year, or 3 years.	For other retention period requirements, submit a ticket to contact technical support.
Transaction & Lock Snapshot			Transaction and lock snapshot information is retained for 30 days. The query time range for snapshot points in the transaction and lock snapshot list cannot exceed 24 hours.	For other retention period requirements, submit a ticket to contact technical support.
Diagnosis report			Diagnostic data is retained for 7 days.	For other retention period requirements, submit a ticket to contact technical support.
Automated O&M event			Operation event records are retained for 30 days.	For other retention period requirements, submit a ticket to contact technical support.

Other limits

Item	Description	Remarks
Allowlist	When logging in to your target instance, the system will prompt you to add DBW's service IP to the instance allowlist. Do not modify or remove this allowlist entry, as doing so will render DBW unavailable for this database instance.	None
Account	On the DBW, you can create a database account in a managed database instance. You can view the account information on the account management screen of the database instance. Do not modify or delete the related account information. Otherwise, the DBW may become unavailable.	None
Session	To ensure that the additional load generated by the management service of DBW remains at a reasonable level, DBW sets limits on the session execution time, session retention period, and other information. Specific limits are as follows: Session execution time: Up to 300 seconds. Session retention period: Up to 30 minutes. Rows to return for data query: Up to 3,000 rows. Rows of log retrieval results: Up to 100,000 rows. Size of a result set: Up to 200 MB. Number of session windows: Up to 100. Number of database connections: Up to 50 per region.	For special requirements, submit a ticket for technical support.
Database console	SQL execution logs are retained by default for 30 days.	None
Operation and maintenance observation logs	Operation and maintenance observation logs are retained for 30 days.	For other retention duration requirements, submit a ticket to contact technical support.
Data import/export	File size limits for data import and export: Data import tasks: Currently only supports uploading files in CSV and SQL formats (Excel format not supported). The maximum file size cannot exceed 1GiB. Data export tasks: A Single table cannot exceed 10GiB, and a single task cannot exceed 50GiB.	None
Full SQL insight	Full SQL insight captures, audits, and analyzes all SQL statements to help improve database performance and stability. The feature maintains a maximum SQL statement recording limit of 4,096 bytes, with any exceeding content automatically truncated. The actual recorded length follows these rules. When the parameter is less than or equal to 4,096 bytes, the system uses the parameter value as the maximum length (with excess truncated), though the effective recorded length becomes slightly shorter due to added prefix annotations during processing. When the parameter exceeds 4,096 bytes, the system enforces a strict 4,096-byte limit (with excess truncated), though the effective recorded length becomes slightly shorter due to added prefix annotations during processing.	None

Last updated: 2025.09.24 11:49:41