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 |
Procedure
- In the left-side navigation pane, click Instances. On the Hosts page, click Create Instance.
- In the panel that appears, configure the parameters. The following table describes
the parameters.
Parameter Description Database Engine The database engine that the instance runs. The database engine is set to SQL Server. You cannot change the database engine. Current Version The edition of the database engine that the instance runs. The following editions are supported: - SQL Server 2019 Enterprise Edition Always On
- SQL Server 2017 Enterprise Edition Always On
- SQL Server 2019 Standard Edition
- SQL Server 2017 Enterprise Edition
- SQL Server 2017 Standard Edition
- SQL Server 2017 Web
- SQL Server 2016 Enterprise Edition
- SQL Server 2016 Standard Edition
- SQL Server 2016 Web
- SQL Server 2012 Enterprise Edition
- SQL Server 2012 Standard Edition
- SQL Server 2012 Web
Edition The edition of the instance. The following editions are supported: - High Availability Edition
- Basic Edition
- Cluster Edition (Always On)
Note Specify the Edition parameter based on the value of the Engine Version parameter. For more information, see Supported engine editions and instance editions.Storage Type The storage type of the instance. The following storage types are supported: - Enhanced SSD (Recommended)
- PL2 Enhanced SSD (Recommended)
- PL3 Enhanced SSD (Recommended)
Instance Specifications The type of the instance. Storage Capacity The storage capacity of the instance. Deployment Method The deployment method that you want to use. You can select Default Policy or Specified Host. - If you set Deployment Method to Default Policy, the balanced allocation policy is used. In this case, the system preferentially deploys the instance on a host that has no loads or small loads.
- If you set Deployment Method to Specified Host, you must select a host on which you
want to deploy the instance.
Note
- If you set Edition to Cluster Edition (Always On) or High-availability Edition, you must specify Primary Host and Secondary Host.
- If you set Edition to Basic Edition, specify only Primary Host.
vSwitch The vSwitch to which the host of the instance is connected. If no vSwitches are available, click Create vSwitch to create a vSwitch. Note This parameter is available only if you set Deployment Method to Default Policy.Billing Method The billing method of the instance. The parameter is automatically set to Pay-as-you-go. Note When you purchase a host that uses an enhanced SSD (ESSD), you are charged only for the computing resources. Therefore, when you create an instance on a host that uses an ESSD, you are charged for your actual storage usage. You are charged for a storage plan based on the subscription billing method. A storage plan can help you reduce storage costs. You can use a storage plan to offset the storage costs of pay-as-you-go instances deployed in the region where the storage plan is purchased.