The following table describes the limits and constraints of SQL Server features and accounts to provide more safe and stable services.
Feature
| Limitations
|
Deploy
| The cloud server on which a DB instance is deployed is invisible to the user, only accessible to applications through IP addresses and ports.
|
Database Access | • For DB instances that have not enabled Internet access, only cloud servers within the same Virtual Private Cloud (VPC) can access the instance. • The cloud server must be in the allowlist of the security group to which the SQL Server instance belongs. • When a DB instance and a cloud server are in different security groups, the access is forbidden by default. You must add an inbound rule to the security group of the DB instance to allow the access. · |
Database Version
| The following editions are supported: • 2022 Enterprise Edition (Instance type upgrade not supported) • 2022 Standard Edition • 2016 Enterprise Edition • 2016 Standard Edition • 2014 Enterprise Edition • 2014 Standard Edition · |
SA Permission of Database
| The super admin (SA) permission cannot be disabled once enabled. Besides, after you create an SA account for a DB instance, the instance is no more protected by the SLA.
|
Modify Database Parameters | Most database parameters can be modified in the console. For some parameters, the modification can only take effect after the DB instance is restarted.
|
Configure Database Replication | By default, SQL Server provides dual-node clusters based on the active/standby architecture, free of user efforts. Replication between active and standby nodes is asynchronous by default and cannot be modified. Standby nodes are invisible to users and cannot be accessed by applications.
|
Restart an Instance | DB instances cannot be restarted through CLI. You can only restart a DB instance in the SQL Server console.
|