A ApsaraDB for MyBase for SQL Server instance allows you to have more permissions than those you can have on an ApsaraDB RDS for SQL Server instance. This topic provides an overview of MyBase for SQL Server and introduces related concepts.
MyBase for SQL Server
- You can create one or more hosts in a MyBase for SQL Server dedicated cluster. Then, you can deploy instances to these hosts. This way, you can isolate resources among hosts.
- You can use a compact or balanced resource allocation policy and configure the availability status of a host. For more information, see Enable or disable instance allocation on a host.
- You can configure resource overcommitment ratios to maximize resource usage and reduce costs.
- You can temporarily scale up resources for an instance for short-term use. This helps you handle business traffic surges. For more information, see Modify the configuration of a MyBase for SQL Server instance.
Supported instance editions
|SQL Server 2019 Enterprise Edition Always On||Always On|
|SQL Server 2017 Enterprise Edition Always On|
|SQL Server 2017 Enterprise Edition||
|SQL Server 2017 Standard Edition|
|SQL Server 2016 Enterprise Edition|
|SQL Server 2016 Standard Edition|
|SQL Server 2012 Enterprise Edition|
|SQL Server 2012 Standard Edition|
|SQL Server 2017 Web||Basic Edition|
|SQL Server 2016 Web|
|SQL Server 2012 Web|
Comparison between MyBase for SQL Server and ApsaraDB RDS for SQL Server
|Database feature||ApsaraDB for MyBase||RDS|
|Intended customers||Large and medium-sized enterprises.||Enterprise users and individual users that work in development and test environments.|
|Resource isolation||The CPU, memory, disk, and network resources in a dedicated cluster are isolated from the resources of other clusters. Database administrators can allocate resources based on business requirements.||In most cases, all resources in a dedicated cluster are isolated from the resources of other clusters.|
|Resource scheduling||Automatic resource scheduling is supported.||No scheduling policies are used.|
|Resource overcommitment||The maximum CPU overcommitment ratio is 300%.
Note The CPU overcommitment ratio can range from 100% to 300%. The default ratio is 200%. If you use the default value, the system can allocate twice the number of the provided CPU resources.
|Resource overcommitment is not supported.|
|OS permissions||In addition to the permissions to develop your own management systems, you are also granted permissions on the database hosts.||You are granted the permissions to develop your own management systems.|
|Database management permissions||You have all permissions on the databases.||You have most permissions on databases. However, you do not have the super user or super admin permissions on databases.|
|High database security||
||You can secure your data by using access link encryption, disk data encryption based on Bring Your Own Key (BYOK). You can also perform data and operation audits.|
|Improved O&M capabilities||