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

Creating a GD

PDF
Focus Mode
Font Size
Last updated: 2025-07-25 15:50:49
This document introduces the operations and instructions for creating a global database (GD) through the console.
Note:
The GD feature is currently in the beta testing phase. If you want to experience it, submit a ticket for application.

Prerequisites

A cluster is created as the primary cluster for the GD. During the creation process, the database proxy should be enabled for the primary cluster, and the specifications of the read-write instance should be 4 cores or higher.

Precautions

The database proxy is enabled by default when a secondary cluster is created.
When the GD feature is enabled, the database proxy for both the primary cluster and secondary cluster in the GD cannot be disabled.

Introduction of Supported Modes and Versions

Supported instance mode: provisioned resource. Serverless clusters are not supported currently.
Supported versions: including kernel minor version TDSQL-C for MySQL 8.0 3.1.16.100 and later versions. To upgrade to this version, submit a ticket to obtain solutions. For details about upgrading the kernel minor version, see Upgrading the Kernel Minor Version.

Billing Instructions for Features

Currently, the cross-region traffic transmission for the GD feature is free of charge. You only need to pay for the fees associated with each cluster. For details on cluster pricing, see Product Pricing.

Introduction of Feature Limitations

Currently, this feature only supports the TDSQL-C for MySQL 8.0 version.
A GD contains a primary cluster and up to 2 secondary clusters.
The primary cluster and secondary cluster share a set of global parameters.
To enable the GD feature, the specification of the read-write instance is required to be 4 cores or higher.
Neither the primary cluster nor the secondary cluster in the GD supports the Serverless configuration feature or the operation to convert instances to Serverless mode.

Supported Regions and AZs

For details about the supported regions and AZs, see Overview.

Creating a GD

1. Log in to the TDSQL-C for MySQL console.
2. Click GDN in the left sidebar.
3. Click Create GD on the interface.

4. In the pop-up window, complete the following configurations, and click OK.

Parameter
Description
Name
Name of the GD, which should be configured with business significance (subsequent modification is supported) for easy identification. Input format: Start with uppercase and lowercase letters or Chinese characters, consisting of digits, underscores (_), or hyphens (-), with a length of 2 to 126 characters.
Primary Region
Select the region where the primary cluster is located.
Note:
First, confirm which cluster you want to select as the primary cluster and then select the region where the cluster is located.
Source AZ
Select the primary AZ in the region where the primary cluster is located.
Primary Cluster
Select an existing cluster as the primary cluster for the GD.
Note:
The database proxy should be enabled for the primary cluster, and the specification of the read-write instance should be 4 cores or higher.
5. (Optional) After successful creation of the GD, you can add a secondary cluster. For directions, see Managing Secondary Clusters.

Help and Support

Was this page helpful?

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

Feedback