Database instances¶
Create and manage database instances in the MatrixOne Intelligence Instance Management Platform, then connect and sign in to them.
Instance types¶
Type |
Description |
|---|---|
Serverless |
Compute resources scale automatically with your workload. Supports production and free instances |
Standard |
Dedicated, stable compute node specifications. Compute can be billed by subscription or pay-as-you-go, while storage is billed by usage |
When creating an instance, select a public cloud and region. Common regions currently available in the console include Alibaba Cloud, China East 1 (Hangzhou). Refer to the actual list on the creation page.
Create a Serverless instance¶
Sign in and enter the Instance Management Platform. Select Instances > + Create Instance.
Select Serverless as the instance type.
Select a cloud provider and region.
Configure capacity and the billing policy:
Production use: Dedicated, scalable compute. You can configure a spending limit (the behavior when the monthly/daily quota is reached) and service continuity (whether to continue serving at reduced performance after reaching the limit). For billing details, see Instance billing.
Free instance: Up to five per account, with free CU and storage quotas. When resources are exhausted, reads, writes, viewing details, and other operations are restricted. Free instances are suitable for evaluation and learning and can be converted to production instances.
Configure access control:
Administrator (admin) password: At least 8 characters and must contain digits, uppercase letters, and lowercase letters.
Network policy: Allow all public IP addresses, or allow specified IP addresses (recommended). After creation, you can change this setting under Network Policy > Edit for the instance.
Name the instance, review the summary on the right, and click Create Instance. The status changes from Creating to Available.
In the instance list, select Connect > Connect Using a Third-Party Tool, and copy the client connection command.
To convert a free instance to a production instance, select … > Convert Instance Type in the list, or open the overview page and select Convert Instance Type. The conversion takes effect immediately. Refer to the console prompts to determine whether the converted instance still counts toward the current month’s free-instance quota and for other details.
Create a Standard instance¶
Sign in and select Instances > + Create Instance, then select Standard.
Select a cloud and region as described above.
Configure capacity:
Node specification (common options include 8 cores/32 GiB and 16 cores/64 GiB; refer to the creation page for the supported node-count range)
Storage: Pay-as-you-go and billed hourly
Select a compute billing method:
Subscription: Select the duration and discount. You can enable automatic renewal (the fee is deducted automatically before expiration; see Instance billing) or renew later from the instance card.
Pay-as-you-go: Use resources before payment; the fee for the previous hour is deducted hourly.
Set the admin password and network policy (with the same requirements as for Serverless).
Name the instance and confirm creation. For a subscription, payment is deducted on the payment page (vouchers are used first by default and combined payment is supported; custom payment combinations are generally not supported for automatic renewal).
After creation, similarly select Connect > Connect Using a Third-Party Tool to obtain the connection command.
In addition to the compute charges shown on the creation page, storage, object-storage requests, public network traffic, and other resources may be billed separately based on actual usage. See Instance billing.
Connect to an instance¶
By tool¶
Method |
Description |
|---|---|
MySQL protocol client |
MySQL Client, Navicat, DBeaver, and so on |
Java |
JDBC/ORM |
Python |
Official/community drivers |
Go |
go-mysql-driver and other drivers |
For driver installation and examples in each language, see Development. Installation details are not covered on this page.
By network¶
Method |
Description |
|---|---|
Public network |
Fastest and simplest. Pay attention to security and stability, and use an IP allowlist |
Private network |
Private access through VPC endpoints and similar services (more secure and stable) |
Database Management Platform |
Open the instance-side web management interface in a browser |
Obtain connection information from the instance’s Connect entry. For network policies and allowlists, see Access Control in the creation procedure and Permissions: MatrixOne.
Sign in to the Database Management Platform for an instance¶
Find the target instance in the instance list, select Connect > Connect Through Cloud Platform, and enter a username and password to open the Database Management Platform.
User |
Description |
|---|---|
admin |
The highest-privileged user configured when the instance was created; the default sign-in user |
Regular user |
A user, role, and grants must first be created by an account with the required permissions |
Example steps for a regular user (run the SQL in an admin session):
Create a user:
create user u2 identified by '……';Create a role:
create role if not exists role2;Grant permissions and assign the role, for example:
grant all on account * to role2;grant all on database * to role2;grant all on table *.* to role2;grant role2 to u2;Sign in with the username format
username:role_name(for example,u2:role2). If no role is specified,publicis used by default.
For details about the permission model, see Permissions: MatrixOne.
Terminate and restore an instance¶
Caution: The platform does not retain terminated instances permanently. Proceed carefully, and restore an accidentally deleted instance as soon as possible.
Terminate¶
Select Instances > Available Instances, then click Terminate on the instance card.
Confirm the name. The instance enters the Terminating state and appears on the Terminated Instances tab when the operation is complete.
Notes:
Termination immediately closes all database access connections.
Data is retained for 7 days after termination and is permanently deleted afterward.
Restore¶
On the Terminated Instances tab, select an instance, click Restore, and confirm. The instance becomes available again after several seconds.
Instance states¶
State |
Meaning |
Typical available operations |
|---|---|---|
Creating |
The instance is being created |
No instance operations |
Available |
Normal service |
Terminate; connect, monitor, view details, edit the spending limit, and so on |
Restricted |
Free resources are exhausted, the spending limit is reached, the account is in arrears, and so on |
Terminate; in some scenarios connect (for example, when the limit is reached and service continuity is enabled), monitor, view details, and edit limits |
Invalid |
An exception prevents full service |
Terminate; monitor, view details, and edit limits |
Terminating |
The instance is being terminated |
Monitoring and similar read operations may be available |
Terminated |
The instance has been terminated |
Restore |
Restoring |
The instance is being restored |
None |
Common causes of the Restricted state include exhausted free CU or storage, a production spending limit reached without service continuity enabled, a spending limit reached with service continuity enabled (running at reduced speed), and account arrears.