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
DocumentationTDSQL-C for MySQLOperation GuideDatabase ProxyManaging Database ProxyTransaction Split Feature

Transaction Split Feature

PDF
Focus Mode
Font Size
Last updated: 2026-01-29 18:04:29
The TDSQL-C for MySQL database proxy provides the transaction split feature. This feature separates read and write operations in a transaction to different instances for execution and forwards read requests to read-only instances, thereby effectively reducing the load on the read-write instance.
Note：
Explicit transactions (such as begin or start transaction) currently do not support splitting.
Enabling or disabling the transaction split feature will affect newly established connections only.


Background

By default, the TDSQL-C for MySQL database proxy sends all requests within a transaction to the read-write instance to ensure transaction correctness. However, certain frameworks may encapsulate all requests in non-autocommit transactions, leading to increased load on the read-write instance. In such cases, you can use the transaction split feature. To enable or disable the transaction split feature, you can go to Database Proxy > Overview > Connection Address. Then, click Adjust Configurations in the Operation column.

Prerequisites

You have enabled database proxy. For details, see Enabling Database Proxy.

Directions

1. Log in to the TDSQL-C for MySQL console.In the cluster list, select the cluster with the proxy enabled and click its ID to navigate to the Cluster Management page.
2. Open the topology in Cluster Management > Cluster Details, hover over the database proxy area, and click Details to go to the database proxy management page. Alternatively, click the Database Proxy tab on the cluster management page to go to the database proxy management page.
3. On the Database Proxy Management page, select Access Policy, find the target access policy, and click Adjust Configuration.
Note：
You can also find the target proxy address in Database Proxy > Overview > Connection Address. Then, click Adjust Configurations in the Operation column.
4. In the Adjust Configuration window, enable or disable the transaction split feature and click OK to save the changes.


Related APIs

API
Description
This API (ModifyProxyRwSplit) is used to configure database proxy read-write splitting.
Previous Topic: Momentary Disconnection Prevention FeatureNext Topic: Access Mode

Help and Support

Was this page helpful?

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

Feedback