Before you use the features of ApsaraDB MyBase, you must create an instance on a host in your ApsaraDB MyBase dedicated cluster. The system creates an instance on a host based on the specified resource allocation policy.
Prerequisites
A host is created in an ApsaraDB MyBase for SQL Server dedicated cluster. For more information, see Create a host in an ApsaraDB MyBase for SQL Server dedicated cluster.
Background information
For more information about ApsaraDB MyBase, see What is ApsaraDB MyBase?
Supported engine editions and instance editions
Engine edition | Instance edition | Description |
---|---|---|
SQL Server 2019 Enterprise Edition Always On | Cluster Edition (Always On) | Before you create an instance of the Cluster Edition (Always On), add at least two hosts that use the same storage type to the dedicated cluster. |
SQL Server 2017 Enterprise Edition Always On | ||
SQL Server 2019 Standard Edition |
|
|
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 | Before you create an instance of the Basic Edition, add one host to the dedicated cluster. |
SQL Server 2016 Web | ||
SQL Server 2012 Web |
Comparison among different instance editions
Instance edition | Description | Scenario |
---|---|---|
Basic Edition | An ApsaraDB MyBase for SQL Server instance of the Basic Edition is a standalone instance that decouples computing and storage. This edition is cost-effective. |
|
High-availability Edition | This edition uses a primary/secondary architecture to ensure high availability and is suitable for more than 80% of business scenarios. |
|
Cluster Edition (Always On) | An ApsaraDB MyBase for SQL Server instance of the Cluster Edition (Always On) is built on top of the Always On availability groups feature and decouples computing and storage. By default, the Cluster Edition (Always On) uses an architecture that has one primary instance and one read-only instance. If you want to split read and write requests, enable read/write splitting and specify a read/write splitting endpoint. You can also increase the number of read-only instances based on your business requirements. This helps improve the read performance of your ApsaraDB MyBase for SQL Server instance of the Cluster Edition (Always On). For information about how to add read-only instances, see Use an ApsaraDB MyBase for SQL Server Always On instance. | Production databases for large-sized enterprises and medium-sized enterprises, such as online retailers, automobile companies, and enterprise resource planning (ERP) providers |