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

Overview

PDF
Focus Mode
Font Size
Last updated: 2025-01-23 17:01:24
This document describes TDSQL-C for MySQL connection methods, their application scenarios, and troubleshooting methods.
Note:
Public network connections are susceptible to network issues. If you have high network requirements, it is recommended to use private network connections or Cloud Connect Network (CCN) connections.

Connection Methods

Connection Method
Application Scenario
Billing
FAQs
Without Cloud Virtual Machine (CVM), directly log in through the TDSQL-C for MySQL console to the Database Management Center (DMC) console for database management. For specific scenario descriptions, refer to Scenario 1.
Free of charge currently.
The CVM is Linux CVM that can be connected using a private or public network address. For specific scenario descriptions, refer to Scenario 2.
Free of charge currently.
The CVM is Windows CVM that can be connected using a private or public network address. For specific scenario descriptions, refer to Scenario 3.
Free of charge currently.
CVM and TDSQL-C for MySQL are in different Virtual Private Cloud (VPC) networks, or Lighthouse is used to connect to TDSQL-C for MySQL. For specific scenario descriptions, refer to Scenario 4.

Application Scenario Description

Scenario 1: Using the DMC to Connect to a Cluster

Without CVM, log in to the TDSQL-C for MySQL console using your Tencent Cloud account, find the target cluster, and click Log In on the cluster management page. Then, you are redirected to the DMC console for database management. DMC can provide a variety of services, including database/table-level operations, real-time monitoring, instance session management, SQL window, and data management.

Scenario 2: Connecting to a Cluster via a Private or Public Network Address from Linux CVM

Private network connections
The CVM is Linux CVM that is under the same Tencent Cloud root account as TDSQL-C for MySQL. Both CVM and TDSQL-C for MySQL are in the same region, use the VPC network type, and are within the same VPC.
For example:
Under account 1, CVM is in subnet A in VPC 1 in Guangzhou, and TDSQL-C for MySQL is in subnet B in VPC 1 in Guangzhou.
Public network connections
The CVM is Linux CVM. In scenarios where private network connections are not available, you can connect via the public network if TDSQL-C for MySQL has enabled public network access.
For example:
Under account 1, CVM is in subnet A in VPC 1 in Guangzhou, and TDSQL-C for MySQL with public network access enabled is in Guangzhou.
Under account 1, CVM is in subnet A in VPC 1 in Guangzhou, and TDSQL-C for MySQL with public network access enabled is in Beijing.
Under account 1, CVM is in subnet A in VPC 1 in Guangzhou, and under account 2, TDSQL-C for MySQL with public network access enabled is in Beijing.

Scenario 3: Connecting to a Cluster via a Private or Public Network Address from Windows CVM

Private network connections
The CVM is Windows CVM that is under the same Tencent Cloud root account as TDSQL-C for MySQL. Both CVM and TDSQL-C for MySQL are in the same region, use the VPC network type, and are within the same VPC.
For example:
Under account 1, CVM is in subnet A in VPC 1 in Guangzhou, and TDSQL-C for MySQL is in subnet B in VPC 1 in Guangzhou.
Public network connections
The CVM is Windows CVM. In scenarios where private network connections are not available, you can connect via the public network if TDSQL-C for MySQL has enabled public network access.
For example:
Under account 1, CVM is in subnet A in VPC 1 in Guangzhou, and TDSQL-C for MySQL with public network access enabled is in Guangzhou.
Under account 1, CVM is in subnet A in VPC 1 in Guangzhou, and TDSQL-C for MySQL with public network access enabled is in Beijing.
Under account 1, CVM is in subnet A in VPC 1 in Guangzhou, and under account 2, TDSQL-C for MySQL with public network access enabled is in Beijing.

Scenario 4: Connecting Through CCN

1. CVM and TDSQL-C for MySQL are in different VPCs (including the same account/different accounts and the same region/different regions).
2. Under the same Tencent Cloud account, if you have purchased Lighthouse and want to connect to TDSQL-C for MySQL, you need to connect through CCN.
For example:
Under account 1, CVM is in subnet A in VPC 1 in Guangzhou, and TDSQL-C for MySQL is in subnet B in VPC 2 in Guangzhou.
Under account 1, CVM is in subnet A in VPC 1 in Guangzhou, and TDSQL-C for MySQL is in subnet B in VPC 2 in Beijing.
Under account 1, CVM is in subnet A in VPC 1 in Guangzhou, and under account 2, TDSQL-C for MySQL is in subnet B in VPC 2 in Beijing.
Under account 1, Lighthouse is in subnet A in VPC 1 in Guangzhou, and TDSQL-C for MySQL is in subnet B in VPC 2 in Guangzhou.

Connection Troubleshooting

Help and Support

Was this page helpful?

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

Feedback