tencent cloud

TDSQL-C for MySQL

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
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use 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
Classified Protection Practice for Database Audit of TDSQL-C for MySQL
Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
Usage Instructions for TDSQL-C MySQL
New Version of Console
Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
Strengths of Database Proxy
Selecting Billing Mode for Storage Space
Creating Remote Disaster Recovery by DTS
Creating VPC for Cluster
Data Rollback
Solution to High CPU Utilization
How to Authorize Sub-Users to View Monitoring Data
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
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
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 the Read-Only Analysis Engine

PDF
Focus Mode
Font Size
Last updated: 2025-01-02 09:50:57
This document introduces how to load data into the read-only analysis engine for data analysis and queries by users.
Note:
Currently, only databases, tables, and views can be loaded into the read-only analysis engine.

Prerequisites

You have prepared a cluster in the provisioned resource instance mode. See Creating Cluster.
The cluster is in the running status.

Directions

The read-only analysis engine currently supports multiple data loading methods. Detailed operation methods are as follows.

Method 1: Loading Data During Creation of a Read-Only Analysis Engine

During creation of a read-only analysis engine instance, you can select a data loading method. Currently, there are three options: Full load, Partial objects, and No objects. The three different data loading methods correspond to different loading schemes.
1. The data loading method is full load.
In the full load mode, all database tables of the TDSQL-C for MySQL cluster will be automatically synchronized to the read-only analysis engine. Since some database table objects may not meet the loading conditions, these unsupported objects will be automatically ignored and not loaded into the read-only analysis engine.
2. Partial objects data loading method.
If the data loading method is selected as partial objects, you need to specify the objects to be loaded into the analysis engine during creation of a read-only analysis engine instance. If there are objects that do not meet the loading conditions, they will be ignored. If a table referenced by a view has not been loaded into the read-only analysis engine, an error will be reported that the table does not exist when the view is loaded.
3. No objects data loading method.
If the data loading method is selected as no objects, it means that no objects will be loaded during creation of a read-only analysis engine instance. Users need to manually specify the objects to be loaded when the instance is running. See Method 2: Manual Loading.

Method 2: Manual Loading

If the no objects method is selected during creation of a read-only analysis engine instance, or if you need to modify the object information loaded into the read-only analysis engine, you can use the following method.

Loading Objects in the Console

1. Log in to the TDSQL-C MySQL console and click the target cluster in the cluster list on the left to enter the cluster management page.
2. On the cluster details page, locate the read-only analysis engine instance for which you need to modify the loaded objects, and then click Details to enter the details page of the read-only analysis engine instance.
3. Click Modify Object. In the object modification dialog box, check or uncheck the objects to be loaded into the read-only analysis engine.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback