TencentDB for SQL Server
- Release Notes and Announcements
- Announcements
- Product Introduction
- Product Architecture
- Instance Specifications
- Purchase Guide
- Product Pricing
- Getting Started
- Connecting to TencentDB for SQL Server Instance
- Operation Guide
- Maintaining Instance
- Adjusting Instance Configuration
- Read-Only Instance
- Network and Security
- Account Management
- Database Management
- Data Security
- Access Management
- Parameter Configuration
- Monitoring and Alarms
- Backup and Restoration
- Backup
- Setting Automatic Backup
- Log Management
- Publish-Subscribe
- SSIS
- Data Migration (New)
- Using DTS to Migrate Data
- Pre-Validation Failure Handling
- Data Migration (Legacy)
- Migrating Data from SQL Server Instance Purchased at Other Cloud Service Provider or Built In-house
- Practical Tutorial
- API Documentation
- Sales and fee related APIs
- Operation and maintenance management 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
- Data migration (cold standby migration) related APIs
- Data migration (DTS old version) related APIs
- Making API Requests
- Database APIs
- Other APIs
- FAQs
- Service Agreement
- Performance Evaluation
DocumentationTencentDB for SQL ServerRelease Notes and AnnouncementsAnnouncementsAccount Type and Permission Changes
Account Type and Permission Changes
Last updated: 2023-04-06 16:51:55
To provide more comprehensive and convenient instance account management services, TencentDB for SQL Server will change the instance account types and permissions on February 9, 2023 as detailed below:
Account mappings
Instance Architecture | Old Account Type | New Account Type | Description |
Two-node (formerly High Availability/Cluster Edition) | Admin | Privileged account | The old admin account corresponds to the new privileged account, which has the owner permissions of all databases by default. |
| Non-admin | Standard account | The old non-admin account corresponds to the new standard account. |
| - | Designated account | A new designated account is added, which can only view and own the specified database. A designated account can be authorized to multiple databases, but a database can be authorized to only one designated account. |
Single-node (formerly Basic Edition) | Admin | Admin account | The old admin account corresponds to the new admin account, which has the highest-level sysadmin permission and the owner permissions of all databases. After the admin account is enabled, the product SLA will no longer be guaranteed. |
| Non-admin | Standard account | The old non-admin account corresponds to the new standard account. |
| - | Privileged account | A privileged account is added, which has the owner permissions of all databases by default. |
| - | Designated account | A new designated account is added, which can only view and own the specified database. A designated account can be authorized to multiple databases, but a database can be authorized to only one designated account. |
Permission mappings
Old Account Type | New Account Type | Old Account Permission | New Account Permission | Database-Level Permission |
Non-admin | Standard account | Read-only | Read-only | db_reader |
| | Read/Write | Owner | db_owner |
| | - | Read/Write | db_reader db_writer |
Note:
The old and new account types and permissions have already been made compatible, so existing instances won't be affected.
Contact us if you have any questions about instance account type and permission changes.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No