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
ドキュメントTencentDB for SQL ServerPractical TutorialConnecting Kingdee K/3 WISE to TencentDB for SQL Server

Connecting Kingdee K/3 WISE to TencentDB for SQL Server

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-01-18 17:25:32
This document describes how to connect Kingdee K/3 WISE 15.0/15.1 to TencentDB for SQL Server so as to execute distributed transactions between the TencentDB for SQL Server and Windows CVM instances.
This solution consists of the following three steps:
1. Migrate data to TencentDB for SQL Server, i.e., restoring the full data backup of the account set database in a local Kingdee K/3 WISE instance to TencentDB for SQL Server.
2. Enable distributed transaction execution, i.e., adjusting the access settings of the TencentDB for SQL Server and Windows CVM instances to ensure that the relevant ports are open for distributed transaction execution.
3. Replace the account set management tool to make it compatible with TencentDB for SQL Server.
Note:
To support distributed transactions, additional resources are required for configuration; therefore, you can configure High-Availability Edition instances only in specification higher than "1-core 8 GB MEM". Please upgrade the instances that do not meet the minimum requirement before connection.
Adjust the TencentDB for SQL Server access settings to ensure that distributed transaction can be executed. You can submit a ticket for assistance. To improve the ticket processing efficiency, make sure that you have already read this document and completed data migration to TencentDB for SQL Server before submitting the ticket.

Step 1. Migrate data to TencentDB for SQL Server

Prerequisites: you have backed up the full data of the account set database files in your local Kingdee K/3 WISE instance.
1. Log in to the Windows CVM instance and install Kingdee K/3 WISE.
Note:
The CVM instance where Kingdee is installed and the TencentDB for SQL Server instance must be in the same VPC in the same region.
3. Upload the full backup file and restore the data. For detailed directions, please see Uploading Backup File to COS and Migrating Data Through Source File in COS.
4. Create a TencentDB for SQL Server account and authorize it. For more information, please see Creating Account.

Step 2. Enable distributed transaction execution

Setting TencentDB for SQL Server

Adjust the TencentDB for SQL Server access settings to ensure that distributed transactions can be executed. You can submit a ticket for assistance.

Setting CVM instance

Setting security group

1. Log in to the CVM Console, select the region where the instance resides, and click the instance ID to enter the management page.
2. Select the Security Group tab and modify the rules as follows:
"Source" IP information, which can be obtained by submitting a ticket.
"Protocol ports" of inbound and outbound rules. You need to open the ports 1433, 135, and 1024–65535.

Setting Windows OS

2. Open the hosts file located at C:\\Windows\\System32\\drivers\\etc\\hosts.
3. Add the VIP and host information (which can be obtained by submitting a ticket) provided by TencentDB for SQL Server to the end of the hosts file and save the change.
4. Open "Component Services" in "Control Panel" > "System and Security" > "Administrative Tools".
5. Select "Component Services" > "Computers" > "My Computer" > "Distributed Transaction Coordinator".
6. Right-click the local DTC on the right and select "Properties".
7. Select the "Security" tab, set as follows, and click OK.
8. In the pop-up MSDTC service dialog box, click Yes and wait for the MSDTC service to restart.

Step 3. Initialize account set management

1. Download the account set management tool: Kingdee K/3 WISE 15.1 or 15.0.
Note:
The required account set management tool varies by Kingdee K/3 WISE version.
2. Decompress the package and replace the files in the Kingdee installation directory K3ERP\\KDSYSTEM\\KDCOM with the extracted files.
3. Open Kingdee K/3 WISE.
4. On the pop-up account set management database settings page, set relevant identity verification information and data server.
Note:
Enter the private network address of the TencentDB for SQL Server instance as the data server, which can be viewed in the console.
5. In the "System" drop-down list, click Preset Connection and set the preset connection for easier use.
6. In the database drop-down list, click Register Account Set.
7. Select the corresponding database and click All.

Step 4. Log in to and use Kingdee K/3 WISE

After you complete all the settings above, distributed transactions can be supported between the CVM and TencentDB for SQL Server instances, and you can log in to and use Kingdee K/3 WISE normally.
If the following error message is displayed during login: Failed to create the transaction at the intermediate layer. Please contact the system administrator. Advanced display: error code: 5(5H)

ヘルプとサポート

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

フィードバック