Release Notes and Announcements
- Release Notes
- Product Announcements
Beginner's Guide
Product Introduction
- Overview
- Strengths
- Use Cases
- Architecture
- Product Specifications
- Instance Types
- Product Feature List
- Database Versions
- Regions and AZs
- Common Concepts
- Use Limits
- Suggestions on Usage Specifications
Kernel Features
- Kernel Overview
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Security Features
- Stability Feature
- Analysis Engine Features
- Inspection and Repair of Kernel Issues
Purchase Guide
- Billing Overview
- Product Pricing
- Creating Cluster
- Specification Adjustment Description
- Renewal
- Payment Overdue
- Refund
- Change from Pay-as-You-Go to Yearly/Monthly Subscription
- Change from Pay-as-You-Go to Serverless Billing
- Value-Added Services Billing Overview
- Viewing Billing Statements
Getting Started
Database Audit
Serverless Service
- Serverless Introduction
- Creating and Managing a Serverless Cluster
- Elastic Scaling Management Tool
- Serverless Resource Pack
- Multi-AZ Deployment
- Configuration Change
- FAQs
- Serverless Cost Estimator
Operation Guide
- Operation Overview
- Switching Cluster Page View in Console
- Database Connection
- Instance Management
- Configuration Adjustment
- Instance Mode Management
- Cluster Management
- Scaling Instance
- Database Proxy
- Account Management
- Database Management
- Database Management Tool
- Parameter Configuration
- Multi-AZ Deployment
- GD
- Backup and Restoration
- Operation Log
- Data Migration
- Parallel Query
- Columnar Storage Index (CSI)
- Analysis Engine
- Database Security and Encryption
- Monitoring and Alarms
- Basic SQL Operations
- Connecting to TDSQL-C for MySQL Through SCF
- Tag
Practical Tutorial
White Paper
- Security White Paper
- Performance White Paper
Troubleshooting
- Connection Issues
- Performance Issues
API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- Multi-Availability Zone APIs
- Other APIs
- Audit APIs
- Database Proxy APIs
- Backup and Recovery APIs
- Parameter Management APIs
- Billing APIs
- serverless APIs
- Resource Package APIs
- Account APIs
- Performance Analysis APIs
- Data Types
- Error Codes
FAQs
Service Agreement
- Service Level Agreement
- Terms of Service
TDSQL-C Policy
- Privacy Policy
- Data Privacy and Security Agreement
General References
- Standards and Certifications
Glossary
Contact Us

Loading Data into an Analysis Cluster

Focus Mode

Font Size

Last updated: 2025-10-17 12:04:14

This document introduces how to load data into an analysis cluster for data analysis and querying.
Prerequisites
An analysis cluster has been prepared. See Creating an Analysis Cluster.
﻿A data source has been added.
The cluster status is Running.
Operation Steps
Note:
After an analysis cluster is enabled, a database account named "txsqlPlugins_analytics_repl" is created by default. This account is used by the analysis cluster to pull data from the data source. Do not delete this account.
During the initial data loading into the analysis cluster, data is pulled from the data source, thereby causing slow SQL. Ignore the slow SQL information generated under the "txsqlPlugins_analytics_repl" account.
1. Log in to the TDSQL-C for MySQL console and select MySQL (Analytic Cluster) at the top.
2. Click the target cluster in the cluster list on the left to enter the cluster management page.
3. On the cluster details page, click Details in Compute Node to access the instance details page.
﻿
4. On the instance details page, click Modify objects, select the target database or table in the Object Modification pop-up window, and click Next.
Note:
After the objects to be synchronized to the analysis cluster are selected and the setting is completed, data objects will be continuously loaded into the analysis cluster. Once loaded, they can be viewed in the object list.
﻿
5. Perform the mapping settings and click OK.
Note:
For mapping settings, "Forcibly set mapping names for all databases and tables according to the default rule" or "Maintain consistency with the source database and table names, and automatically cancel mapping for objects with the same name" can be selected. You can also choose not to select them temporarily. Note that objects with no mapping settings cannot be queried in the analysis engine.
For detailed instructions on mapping settings, see Database/Table Mapping. For detailed instructions on database/table merging, see Database/Table Merging.
﻿