Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ GaussDB/ Getting Started/ Buying a GaussDB Instance and Connecting to It Through the DAS Console(Recommended)

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

Updated on 2025-01-08 GMT+08:00

Data Admin Service (DAS) enables you to manage instances on a web-based console, simplifying database management and improving working efficiency. You can connect to and manage instances through DAS.

This section describes how to use DAS to connect to a GaussDB instance you have bought on the GaussDB management console. For more methods of connecting to an instance, see Connecting to a GaussDB Instance.

Video Tutorial

Operation Process

Step

Description

Preparations

Sign up for a HUAWEI ID, enable Huawei Cloud services, make sure you have a valid payment method configured, create IAM users, and grant them specific GaussDB permissions.

Step 1: Buy an Instance

Configure basic information about a GaussDB instance and submit the purchase request.

Step 2: Log In to a GaussDB Instance Through DAS

Connect to the GaussDB instance using Data Admin Service (DAS).

Preparations

  1. Sign up for a HUAWEI ID and enable Huawei Cloud services.
  2. Before purchasing DB instances, ensure that your account balance is sufficient. Top up your account if required.
  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. 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, click Buy DB Instance.
  5. On the displayed page, set Billing Mode, enter DB Instance Name, select Edition Type, DB Engine Version, DB Instance Type, and Deployment Model, and complete other configurations.

    Figure 1 Billing mode and basic information

    Table 1 Description

    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.
    • 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.

    NOTE:

    Products in different regions cannot communicate with each other over a private network. After the DB instance is created, you cannot change its region.

    DB Instance Name

    gauss-d0a7

    The instance name must start with a letter and can contain 4 to 64 characters. Only letters (case-sensitive), 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.

    DB Engine Version

    V2.0-8.103

    GaussDB database version.

    DB Instance Type

    centralized

    • Distributed: You can add nodes for distributed instances as needed to handle large volumes of concurrent requests.
    • Centralized: Centralized instances are suitable for scenarios with small and stable volumes of data, where data reliability and service availability are extremely important.

    Deployment Model

    1 primary + 2 standby

    • Distributed instances
      • Independent: Database components are deployed on different nodes. This model is suitable for where high availability and stability are required and the instance scale is large.
      • Combined: Different database components are deployed on the same node. This option is available only when Edition Type is Basic edition.
    • centralized
      • HA (1 primary + 2 standby): 3-node deployment where there is a 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. To create a single-replica instance, ensure that the instance version is V2.0-2.2 or later.
      • 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. This model is available only for instances of version V2.0-3.200 or later.

    AZ

    AZ1

    An AZ is a physical region where resources have their own independent power supply and networks. AZs are physically isolated but interconnected through an internal network.

    Time Zone

    (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi

    You need to select a time zone for your instance based on the region it is hosted in.

  6. Configure instance specifications.

    Figure 2 Specifications and storage

    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 operation.

    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.

  7. Retain the default settings for the network information.

    Figure 3 Network configuration

  8. Configure the instance password and enterprise project.

    Figure 4 Database configuration

    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.

  9. Click Next, confirm the instance information, and click Submit.
  10. 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 5 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 connect to. 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 6 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 7 Creating a database

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

    Figure 8 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 9 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:

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.

Usamos cookies para aprimorar nosso site e sua experiência. Ao continuar a navegar em nosso site, você aceita nossa política de cookies. Saiba mais

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback