tencent cloud

TencentDB for SQL Server

Release Notes and Announcements
Release Notes
Product Announcements
User Guide
Product Introduction
Overview
Product Architecture
Strengths
Use Cases
Regions and AZs
Major Version Lifecycle Explanation
Features and Differences
Instance Types
Instance Specifications
Storage Types
Common Concepts
Network Environment
License Statement
Purchase Guide
Billing Overview
Product Pricing
Purchase Methods
Renewal Instructions
Payment Overdue
Refund
From Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fees Description
Local Backup Space Billing
Cross-Region Backup Billing
Viewing Bill Details
Getting Started
Creating TencentDB for SQL Server Instance
Connecting to TencentDB for SQL Server Instance
Managing TencentDB for SQL Server Instance
Operation Guide
Constraints and Limits
Usage Specifications and Suggestions
Maintaining Instance
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)
Data Synchronization (DTS) 
Practical Tutorial
TencentDB for SQL Server Methods for Regular Maintenance
TencentDB for SQL Server Optimization of Slow SQL
How to Better Use Tempdb
Cross-Account Backup Restoration
Creating VPC for TencentDB for SQL Server
Connecting Kingdee K/3 WISE to TencentDB for SQL Server
Account Permissions and Permission Control
Enabling and Disabling the CDC Feature
Shrinking a Database
API Documentation
History
Introduction
API Category
Making API Requests
Sales and fee related APIs
Instance Management related APIs
Operation and maintenance management related APIs
Network management related APIs
Account management related APIs
Database management related APIs
Security group management related APIs
Data security encryption related APIs
Parameter configuration related APIs
Extended Event related APIs
Log management related APIs
Read only instance management related APIs
Publish and subscribe related APIs
Backup related APIs
Rollback related APIs
Data migration (cold standby migration) related APIs
SQL Server Integration Services (SSIS) related APIs
Data migration (DTS old version) related 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-Related
Parameter Modification
Features
Performance, Space, and Memory-Related FAQs
Service Agreement
Service Level Agreement
Terms of Service
Performance Evaluation
Performance Test Report
Glossary
Contact Us

Instance Connection Scenarios

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-01-18 17:16:54
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.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック