Buying a GaussDB Instance and Connecting to It Through the DAS Console (Recommended)

Procedure

Preparations

1. Sign up for a HUAWEI ID and enable Huawei Cloud services.
2. Before purchasing an instance, ensure that there is a valid payment method configured.
3. For fine-grained permissions management on Huawei Cloud resources, use Identity and Access Management (IAM) to create a user or user group and grant it specific operation permissions. For details, see Creating a User and Granting Permissions.

Buying an Instance

1. Go to the Buy DB Instance page.
2. On the Buy DB Instance page, click the Custom Config tab, select a billing mode, enter an instance name, and set basic instance parameters such as the edition type, DB engine version, DB instance type, and deployment model.
   Figure 1 Basic Settings
   
   Figure 2 Instance Configuration
   

   Table 1 Parameters

   Parameter	Example Value	Description
   Billing Mode	Pay-per-use	GaussDB provides yearly/monthly billing and pay-per-use billing. Yearly/Monthly: You pay upfront for the amount of time you expect to use the DB instance for. You will need to make sure you have a top-up account with a sufficient balance or have a valid payment method configured first. For distributed instances using the combined deployment model, yearly/monthly billing is only available to authorized users. To apply for the permissions needed, submit a service ticket. Pay-per-use: You can start using the DB instance first and then pay as you go. Pricing is listed on a per-hour basis, but bills are calculated based on the actual usage duration.
   Region and Project	CN-Hong Kong	Region where the tenant is located. Products in different regions cannot communicate with each other over a private network. After the instance is created, you cannot change its region.
   DB Instance Name	gauss-d0a7	The instance name is case-sensitive, must start with a letter, and can contain 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
   Edition Type	Enterprise edition	GaussDB provides Basic edition and Enterprise edition. The basic edition lacks certain advanced features that are available in the enterprise edition. The basic edition delivers the same level of performance as the enterprise edition at a more affordable price. This edition is ideal for users who prioritize cost and do not need advanced features. For more details about the differences between the two editions, see Differences Between the Basic and Enterprise Editions of GaussDB Instances.
   DB Engine Version	V2.0-8.218	GaussDB database version.
   DB Instance Type	Centralized	Distributed: Distributed instances allow you to add nodes as needed to handle large volumes of concurrent requests. Centralized: Centralized instances are good for small stable volumes of data, where data reliability and service availability are important.
   Deployment Model	1 primary + 2 standby	Distributed instances Independent: Database components are deployed on different nodes. This model is good when high availability and stability are required and the instance scale is large. Combined: Different database components are deployed on the same node. This model is only available for basic edition instances of V2.0-3.223 or later. Storage autoscaling is not supported by this model. Centralized instances HA (1 primary + 2 standby): 3-node deployment where there is one shard. The shard contains one primary DN and two standby DNs. Single: single-node deployment where there is only one CMS component and one DN. This model is only available for instances of V2.0-2.2 or later. This single-node deployment cannot guarantee service availability (SLA) and is not suitable for production environments. It is only recommended for R&D and testing purposes. 1 primary + 1 standby + 1 log: 3-node deployment where there is one shard with three replicas. The shard contains one primary DN, one standby DN, and one log-dedicated DN (also known as the log node). This model is only available for instances of V2.0-3.200 or later. This option is available only when Resource Type is set to Elastic Cloud Server (ECS).
   AZ	AZ1	An AZ is a physical region where resources have independent power supply and networks. AZs are physically isolated but interconnected through an internal network.

3. Configure instance specifications.
   Figure 3 Resource Configuration
   

   Table 2 Parameters

   Parameter	Example Value	Description
   Instance Specifications	Dedicated(1:4), 4 vCPUs | 16 GB	The vCPUs and memory of an instance.
   Storage Type	Ultra-high I/O	The storage type determines the read/write speed of an instance. The higher the maximum throughput is, the higher the instance read/write speed can be.
   Storage Space	40 GB	The storage space contains the file system overhead required for inodes, reserved blocks, and database operations.
   Disk Encryption	Disable	Enabling disk encryption improves data security, but slightly affects the read and write performance of the database. If a shared KMS key is used, the corresponding CTS event is createGrant. Only the key owner can receive this event.
   Transparent Data Encryption	Disable	Disable: Encryption is disabled. Enable: Encryption is enabled, which improves data security but affects system performance. If you select Enable, the Key Name parameter is displayed. You can select an existing key or create a new one as the tenant key.

4. Retain the default settings for the network information.
   Figure 4 Network Configuration
   

5. Configure the instance password and enterprise project.
   Figure 5 Instance Management
   
   Figure 6 Additional Options
   

   Table 3 Parameters

   Parameter	Example Value	Description
   Administrator Password	-	Enter a strong password and periodically change it to improve security, preventing security risks such as brute force cracking.
   Confirm Password	-	Enter the administrator password again.
   Enterprise Project	default	If the instance has been associated with an enterprise project, select the target project from the Enterprise Project drop-down list. You can also go to the Enterprise Project Management console to create a project. For details, see Enterprise Management User Guide.
   Time Zone	(UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi	Select a time zone according to the region hosting your DB instance when you buy the instance.
   Table Names in M-compatible Databases	-	This parameter controls the case sensitivity of table names in an M-compatible database. The table names here also include table aliases and the names of user views, schemas (internal databases), as well as the names of columns related to these objects in the information_schema system view. NOTICE: The case sensitivity of M-compatible table names can only be configured during the creation of an instance and cannot be changed afterward. The default value is Case-sensitive. To prevent operation failures, keep this setting consistent for both instances involved in the following operations: setting up a DR relationship, restoring data from a backup, importing and exporting data, and logical decoding. This parameter is only available for centralized instances of version V2.0-8.203 or later.

6. Click Next, confirm the instance information, and click Submit.
7. Go to the instance list.

   If status of the instance becomes Available, the instance has been created.

Logging In to a GaussDB Instance Through DAS

1. Log in to the management console.
2. Click in the upper left corner and select a region and project.
3. Click in the upper left corner of the page and choose Databases > GaussDB.
4. On the Instances page, locate the DB instance you want to log in to and click Log In in the Operation column.

   Alternatively, click the DB instance name on the Instances page. On the displayed Basic Information page, click Log In in the upper right corner of the page.

5. On the Custom Login page, select the node to be logged in to. Enter the correct database username and password, and click Test Connection. After the connection test is successful, click Log In.
   Figure 7 Login page
   

   Table 4 Parameters

   Parameter	Example Value	Description
   Login Username	root	Username of the GaussDB database account. The default administrator is root.
   Database Name	postgres	Name of the database to be connected. The default management database is postgres.
   Password	-	Password of the database user.
   Show Executed SQL Statements	Enabled	You are advised to enable Show Executed SQL Statements. With it enabled, you can view the executed SQL statements under SQL Operations > SQL History and execute them again without entering the SQL statements.

Getting Started with SQL

After logging in to an instance, you can create database users, databases, and tables through DAS.

1. Create a database user.

   Only administrators that are created during the instance installation can access the initial database by default. You can also create other database users.

   CREATE USER joe WITH PASSWORD "xxxxxxxxx";

   If information similar to the following is displayed, the creation is successful.

   Figure 8 Creating a database user
   

   In this case, you have created a user named joe, and the user password is xxxxxxx.

   For more information about database users, see Users and Permissions.

2. Create a database.

   CREATE DATABASE db_tpcds;

   If information similar to the following is displayed, the creation is successful.

   Figure 9 Creating a database
   

   Switch to the newly created database in the upper left corner.

   Figure 10 Switching to the new database
   

3. Create a table.
   • Run the following command to create a schema:

     CREATE SCHEMA myschema;

   • Create a table named mytable that has only one column. The column name is firstcol and the column type is integer.

     CREATE TABLE myschema.mytable (firstcol int);

   • Insert data to the table.

     INSERT INTO myschema.mytable values (100);

   • View data in the table.

     SELECT * FROM myschema.mytable;

   Note:

   • By default, new database objects, such as the mytable table, are created in the $user schema. For more information about schemas, see Creating and Managing Schemas.
   • For details about how to create a table, see Creating and Managing Tables.
   • In addition to the created tables, a database contains many system catalogs. These system catalogs contain information about instance installation as well as the queries and processes running in GaussDB. You can collect information about the database by querying the system catalogs. For details about querying system catalogs, see Querying a System Catalog.

4. In the db_tpcds database, run the following statement as user root to grant all permissions of the db_tpcds database to user joe:

   GRANT ALL ON DATABASE db_tpcds TO joe;

   GRANT USAGE ON schema myschema TO joe;

   GRANT ALL ON TABLE myschema.mytable TO joe;

5. Log in to the db_tpcds database as user joe.

6. After login, insert data into the table and verify the data.

   INSERT INTO myschema.mytable values (200);

   SELECT * FROM myschema.mytable;

   Figure 11 Inserting and verifying data
   

Follow-up Operations

After logging in to the instance, you can create alarm rules, set automated backup policies, create databases, and migrate data. For details, see:

• Creating an Alarm Rule
• Setting an Automated Backup Policy
• Creating a Database Using SQL
• Creating a Database Through an API
• Managing GaussDB Databases Through DAS
• Migrating Data to GaussDB

FAQ

Question: What can I do if the DAS console is not displayed after I click Log In in the Operation column of an instance on the Instances page?

Solution: Set your browser to allow pop-ups and try again.