Database Workshop
Database Workshop
Database Workshop
Document
What's new
Announcement
Overview
Billing
Permission management
Quick start
Operation guide
Data management
Data interaction platform
Ticket list
Operation and maintenance management
Enterpise security
Approval workflow
Action trail management
User guide (RDS for MySQL)
Instance list
Data management
SQL window
Database management
Ticket list
Data change ticket
SQL review ticket
Clear table tickets
Data cleanup and archiving ticket
Data import and export ticket
Permission application ticket
Operation and maintenance management
Observation and diagnosis
Session management
Monitoring
Enterprise security management
User guide (veDB for MySQL)
Instance List
Data management
SQL window
Database management
Ticket list
Data change ticket
SQL review ticket
Clear table ticket
Data cleanup and archiving ticket
Data import and export ticket
Permission application ticket
Operation and maintenance management
Observation and diagnosis
Session management
Log management
Enterprise security management
User guide (RDS for PostgreSQL)
Instance list
Data management
SQL window
Ticket list
Data change ticket
SQL review ticket
Permission application ticket
Operation and maintenance management
Enterprise security management
User guide (RDS for SQL Server)
Instance list
Data management
Ticket management
Permission application ticket
Operation and maintenance management
Enterprise security management
User guide (Cache for Redis)
Instance list
Data management
SQL window
Ticket list
Permission application ticket
Operation and maintenance management
Enterprise security management
User guide (Document Database for MongoDB)
Instance list
Data management
SQL window
Ticket management
Permission application ticket
Operation and maintenance management
Enterprise security management
User guide (External instance user guide)
Developer tools
Best practices
API reference
Compliance Agreement
Instance access
SQL task
Operation and maintenance management
Audit log management
Slow log and optimization suggestions
Diagnostics and Snapshots
SQL insights and auditing
Ticket management
Security control
Appendixes
FAQ
FAQ about permission management
Troubleshooting
- Documentation
Database WorkshopUser guide (veDB for MySQL)Data managementTicket listData import and export ticketCreating a data import ticket
Copy page
Download PDFData import and export ticket
Creating a data import ticket
Copy pageDownload PDFCreating a data import ticket
This topic describes how to create a data import ticket for a veDB MySQL instance on the Database Workshop (DBW) console.
Prerequisites
- The NDB for MySQL instance is created and an account with read and write permissions on the target database is created. For detailed steps, refer to Creating an instance and Creating an account.
- The instance has enabled security control. For detailed steps, refer to Enabling security control.
- The Volcano Engine sub-user has been added as a DBW role. For detailed steps, refer to Adding a user.
- The Volcano Engine sub-user added as a DBW role has been granted relevant permissions. For detailed steps, refer to Permission management.
Precautions
- Only one import task can be created at a time. Concurrent imports are not supported.
- System databases do not support data imports.
- Before importing data, verify that the source and target table structures match, including column names, data types, lengths, and order. If structures differ, manually adjust or convert the data to avoid data loss, truncation, or task failure.
- Only CSV and SQL files are supported for upload, with a maximum size of 1 GiB. Excel files are not supported.
- An import task may fail under the following conditions:
- Insufficient database account permissions.
- The target database or table is deleted or renamed during import.
- Target instance restart or configuration change during import.
- The character set of the import file is not utf8, utf8mb4, latin1, or ascii.
Procedure
- Log on to the DBW console.
- On the top menu bar, select the project and region.
- On the left navigation bar, select Data management > Ticket list.
- On the Ticket list page, click Create ticket.
- In the dialog box that appears, select Data import/export > Data import/export.
- On the Fill in the ticket configuration wizard of the Create data import/export ticket control panel, configure the following parameters.
- Create an import CSV file ticketCreate an import SQL file ticketTypeParameterDescriptionBasic informationCreatorDefaults to the currently logged-in account and can not be modified.Ticket titleOptional. Custom ticket title. The ticket title can not exceed 200 characters. If not set, it defaults to empty.Database typeSelect veDB for MySQL.Ticket typeSelect Data import.Execution methodDefaults to Automantic execution after approval, meaning data import tickets will run automatically once approved. This parameter can not be modified.Data import/export configurationInstanceFrom the drop-down list, select the target instance.DatabaseFrom the drop-down list, select the target database.File typeSelect CSV.Target tableFrom the drop-down list, select the target table.Upload fileClick Upload to upload a CSV file, with a maximum size of 1GiB.Data locationSelect data location. The following options are currently supported:
- First row attributes: The first row of the table contains field names.
- First row of data: The first row of the table contains data.
Write methodSelect the file write method from the drop-down list. The following options are currently supported:- INSERT INTO: Data will be inserted using the insert into method. In case of data conflicts, an error will be reported, and the insertion will stop.
- REPLACE_INTO: When a duplicate record exists in the table, the existing data will be overwritten.
Character setSelect the target character set from the drop-down list. Currently supported options include UTF8, UTF8MB4, LATIN1, and ASCII.tipIt is recommended to use the suggested character encoding. Based on the database and target table you select, DBW automatically retrieves the character sets from all relevant tables and provides a recommended option.Exception errorOptional. Check whether to ignore errors in case of exceptions. Unchecked by default.- Checked: Skip the current erroneous statement and continue execution in case of exceptions.
- Unchecked: Terminate the import task immediately upon any error.
Ticket remarksOptional. Customize your ticket remarks. We recommend aligning them with your business for easier tracking.TypeParameterDescriptionBasic informationCreatorDefaults to the currently logged-in account and can not be modified.Ticket titleOptional. Custom ticket title. The ticket title can not exceed 200 characters. If not set, it defaults to empty.Database typeSelect veDB for MySQL.Ticket typeSelect Data import.Execution methodDefaults to Automantic execution after approval, meaning data import tickets will run automatically once approved. This parameter can not be modified.Data import/export configurationInstanceFrom the drop-down list, select the target instance.DatabaseFrom the drop-down list, select the target database.File typeSelect CSV.Target tableFrom the drop-down list, select the target table.Upload fileClick Upload to upload a CSV file, with a maximum size of 1GiB.Data locationSelect data location. The following options are currently supported:- First row attributes: The first row of the table contains field names.
- First row of data: The first row of the table contains data.
Write methodSelect the file write method from the drop-down list. The following options are currently supported:- INSERT INTO: Data will be inserted using the insert into method. In case of data conflicts, an error will be reported, and the insertion will stop.
- REPLACE_INTO: When a duplicate record exists in the table, the existing data will be overwritten.
Character setSelect the target character set from the drop-down list. Currently supported options include UTF8, UTF8MB4, LATIN1, and ASCII.tipIt is recommended to use the suggested character encoding. Based on the database and target table you select, DBW automatically retrieves the character sets from all relevant tables and provides a recommended option.Exception errorOptional. Check whether to ignore errors in case of exceptions. Unchecked by default.- Checked: Skip the current erroneous statement and continue execution in case of exceptions.
- Unchecked: Terminate the import task immediately upon any error.
Ticket remarksOptional. Customize your ticket remarks. We recommend aligning them with your business for easier tracking.
- Click Next step: Pre-check.
- On the Ticket pre-check configuration wizard of the Create data import/export ticket control panel, you can view the Permission check pre-check item.
tip
If pre-check fails, you can click View details in the Result details column of the check item to review the specific reasons for the failure. After making corrections, recreate the ticket.
- Click OK.
Last updated: 2026.08.04 11:16:29
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
