GaussDB Common Practices
After buying and connecting to a GaussDB instance, you can use GaussDB as required by referring to the common practices provided in this section.
Practice |
Description |
|
---|---|---|
Development and design proposal |
This practice describes the restrictions on naming database objects. |
|
This practice describes the principles for designing databases, schemas, tables, fields, constraints, views, and joined tables. |
||
This practice describes notes about configuring tools. |
||
This practice describes the principles for performing DDL operations, loading and unloading data, converting types, and performing queries. |
||
Database usage |
This practice describes how to use CREATE USER and ALTER USER to create and manage database users, respectively. Data is not shared between users. |
|
This practice describes how to use CREATE DATABASE and ALTER DATABASE to create and manage database users, respectively. |
||
The administrator can use tablespaces to control the layout of disks where a database is installed. This practice describes how to use SQL syntax to create and manage tablespaces. |
||
A table is created in a database and can be stored in different databases. Tables under different schemas in a database can have the same name. This practice describes how to use SQL syntax to create tables. |
||
In addition to the created tables, GaussDB contains many system catalogs. These system catalogs contain information about instance installation as well as the queries and processes running in GaussDB. This practice describes how to collect information about the databases by querying system catalogs. |
||
Data migration |
This practice describes how to use DRS to migrate data from Oracle databases to GaussDB. |
|
Data backup |
This practice describes how to enable the system to automatically create backups for a DB instance during a backup window and save the backups based on the configured retention period. |
|
This practice describes how to create manual backups for a DB instance. These backups can be used to restore data for improved reliability. |
||
You can delete manual backups for instances and tables to release storage space. This practice describes how to delete manual backups of an instance. |
||
Data restoration |
This practice describes how to use an automated or manual backup to restore a DB instance to how it was when the backup was created. The restoration is at the instance level. |
|
This practice describes how to use an automated backup to restore instance data to a specified point in time. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot