- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on Changing External Network Links
- Interface Authentication Upgrade Announcement
- Maintenance Time Change from Local Time to Beijing Time
- Account Type and Permission Changes
- Product Architecture Name Change
- Disk Storage Space Composition Change
- Ending Support for Classic Network [2022.12.31]
- Backup Billing Start [2022.07.10]
- Ending Sale for Basic Edition 1-Core Specification [2022.03.07]
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Constraints and Limits
- Usage Specifications and Suggestions
- Maintaining Instance
- Renaming Instance
- Setting Instance Remarks
- Setting Instance Tag
- Setting Instance Project
- Modify Instance-level Character Set Collation
- Modify System Time Zone
- Setting Instance Maintenance Information
- Multi-AZ Disaster Recovery
- Restarting Instance
- Terminating Instance
- Migrating Across AZs
- Manual Primary-Secondary Switching
- Recycle Bin
- Adjusting Instance Configuration
- Read-Only Instance
- Network and Security
- Account Management
- Database Management
- Data Security
- Parameter Configuration
- Monitoring and Alarms
- Backup and Restoration
- Log Management
- Publish-Subscribe
- SSIS
- Data Migration (New)
- Data Migration (Legacy)
- Practical Tutorial
- API Documentation
- History
- Introduction
- API Category
- Sales and fee related APIs
- Network management related APIs
- Account management related APIs
- Instance Management APIs
- Data security encryption related APIs
- Parameter configuration related APIs
- Log management related APIs
- Extended Event APIs
- Read only instance management related APIs
- Backup APIs
- Rollback APIs
- Data migration (cold standby migration) related APIs
- CreateBackupMigration
- ModifyBackupMigration
- StartBackupMigration
- DescribeBackupMigration
- DeleteBackupMigration
- DescribeUploadBackupInfo
- CreateIncrementalMigration
- ModifyIncrementalMigration
- StartIncrementalMigration
- DescribeIncrementalMigration
- DescribeBackupCommand
- DescribeBackupUploadSize
- DeleteIncrementalMigration
- Data migration (DTS old version) related APIs
- Making API Requests
- Database APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- Overview
- Model Selection
- Pricing and Selection
- Connection and Network
- Account and Permission
- Backup and Rollback
- Data Migration
- Publish/Subscribe
- Read-Only Instance
- Version and Architecture Upgrade
- Disk Space and Specification Adjustment
- Monitoring and Alarms
- Log
- Parameter Modification
- Features
- Performance/Space/Memory
- Service Agreement
- Performance Evaluation
- Glossary
- Contact Us
- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on Changing External Network Links
- Interface Authentication Upgrade Announcement
- Maintenance Time Change from Local Time to Beijing Time
- Account Type and Permission Changes
- Product Architecture Name Change
- Disk Storage Space Composition Change
- Ending Support for Classic Network [2022.12.31]
- Backup Billing Start [2022.07.10]
- Ending Sale for Basic Edition 1-Core Specification [2022.03.07]
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Constraints and Limits
- Usage Specifications and Suggestions
- Maintaining Instance
- Renaming Instance
- Setting Instance Remarks
- Setting Instance Tag
- Setting Instance Project
- Modify Instance-level Character Set Collation
- Modify System Time Zone
- Setting Instance Maintenance Information
- Multi-AZ Disaster Recovery
- Restarting Instance
- Terminating Instance
- Migrating Across AZs
- Manual Primary-Secondary Switching
- Recycle Bin
- Adjusting Instance Configuration
- Read-Only Instance
- Network and Security
- Account Management
- Database Management
- Data Security
- Parameter Configuration
- Monitoring and Alarms
- Backup and Restoration
- Log Management
- Publish-Subscribe
- SSIS
- Data Migration (New)
- Data Migration (Legacy)
- Practical Tutorial
- API Documentation
- History
- Introduction
- API Category
- Sales and fee related APIs
- Network management related APIs
- Account management related APIs
- Instance Management APIs
- Data security encryption related APIs
- Parameter configuration related APIs
- Log management related APIs
- Extended Event APIs
- Read only instance management related APIs
- Backup APIs
- Rollback APIs
- Data migration (cold standby migration) related APIs
- CreateBackupMigration
- ModifyBackupMigration
- StartBackupMigration
- DescribeBackupMigration
- DeleteBackupMigration
- DescribeUploadBackupInfo
- CreateIncrementalMigration
- ModifyIncrementalMigration
- StartIncrementalMigration
- DescribeIncrementalMigration
- DescribeBackupCommand
- DescribeBackupUploadSize
- DeleteIncrementalMigration
- Data migration (DTS old version) related APIs
- Making API Requests
- Database APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- Overview
- Model Selection
- Pricing and Selection
- Connection and Network
- Account and Permission
- Backup and Rollback
- Data Migration
- Publish/Subscribe
- Read-Only Instance
- Version and Architecture Upgrade
- Disk Space and Specification Adjustment
- Monitoring and Alarms
- Log
- Parameter Modification
- Features
- Performance/Space/Memory
- Service Agreement
- Performance Evaluation
- Glossary
- Contact Us
This document describes some scenarios and methods of connecting to a TencentDB for SQL Server instance from a Windows CVM instance or local Windows system through SQL Server Management Studio (SSMS). For detailed directions, see Connecting to TencentDB for SQL Server Instance from Windows CVM Instance and Connecting to TencentDB for SQL Server Instance from Local System.
Connecting to a TencentDB for SQL Server Instance from a Windows CVM Instance
Scenario 1
The CVM and TencentDB for SQL Server instances are in the same VPC or classic network in the same region under the same Tencent Cloud root account.
Example: Under account 1, the CVM instance is in subnet A in VPC 1 in Guangzhou region, and the TencentDB for SQL Server instance is in subnet B in VPC 1 in Guangzhou region.
Connection method: Connect them over the private network.
Scenario 2
The CVM and TencentDB for SQL Server instances are in different VPCs in the same region under the same Tencent Cloud root account.
Example: Under account 1, the CVM instance is in subnet A in VPC 1 in Guangzhou region, and the TencentDB for SQL Server instance is in subnet B in VPC 2 in Guangzhou region.
Connection method: We recommend that you connect them through CCN.
Scenario 3
The CVM and TencentDB for SQL Server instances are in different regions under the same Tencent Cloud root account.
Example: Under account 1, the CVM instance is in subnet A in VPC 1 in Guangzhou region, and the TencentDB for SQL Server instance is in subnet B in VPC 2 in Beijing region.
Connection method: We recommend that you connect them through CCN.
Scenario 4
The CVM and TencentDB for SQL Server instances are under different Tencent Cloud root accounts.
Example: The CVM instance is in subnet A in VPC 1 in Guangzhou region under account 1, and the TencentDB for SQL Server instance is in subnet B in VPC 2 in Beijing region under account 2.
Connection method: We recommend that you connect them through CCN.
Connecting to a TencentDB for SQL Server Instance from a Local Windows System
Two-node (formerly High Availability/Cluster Edition) instance
Option 1: Use VPN, or Direct Connect, or CCN for interconnection, which are more secure and stable.
Option 2: Connect to the instance over the public network by enabling the public network address or binding the instance to CLB to enable public network access in the console as instructed in Connecting to TencentDB for SQL Server Instance from Local System.
Option 3: Use a Linux CVM instance with a public IP to map the ports as instructed in Connecting to TencentDB for SQL Server Instance from Local System.
Single-node (formerly Basic Edition) instance
Option 1: Use VPN, or Direct Connect, or CCN for interconnection, which are more secure and stable.
Option 2: Connect to the instance over the public network by enabling the public network address in the console as instructed in Connecting to TencentDB for SQL Server Instance from Local System.
Option 3: Use a Linux CVM instance with a public IP to map the ports as instructed in Connecting to TencentDB for SQL Server Instance from Local System.
Yes
No
Was this page helpful?