Data Warehouse Types
Product Type Overview
- Standard Data Warehouse (DWS 2.0): Oriented to data analysis scenarios, DWS 2.0 provides enterprise-level data warehouse services with high performance, high scalability, high reliability, high security, and easy O&M. It is capable of data analysis at a scale of 2,048 nodes and 20 petabytes of data.
- Standard data warehouse (DWS 3.0): DWS 3.0 is designed with a cloud native architecture that separates storage and compute. It also features hierarchical auto scaling for computing and storage, as well as multi-logical cluster shared storage technology (Virtual Warehouse or VW). These capabilities allow for computing isolation and concurrent expansion to handle varying loads, making it an ideal choice for OLAP analysis scenarios.
- Hybrid data warehouse: a cost-effective solution that goes beyond large-scale data query and analysis. It also offers high-concurrency, high-performance, and low-latency transaction processing capabilities. The data warehouse can be used to process HTAP hybrid loads, and can be deployed in standalone or cluster mode.
- GaussDB(DWS) data warehouses cannot access each other. You can create an OBS foreign table to associate two databases in the same data directory for data query.
Features
Module |
Function |
Standard Data Warehouse (DWS 2.0) |
Standard Data Warehouse (DWS 3.0) |
Hybrid (Cluster) |
Hybrid (Standalone) |
---|---|---|---|---|---|
Dashboard |
Resources |
Yes |
Yes |
Yes |
Yes |
Alarms |
Yes |
Yes |
Yes |
Yes |
|
Recent events |
Yes |
Yes |
Yes |
Yes |
|
Cluster monitoring metrics (DMS) |
Yes |
Yes |
Yes |
No |
|
Data |
- |
Yes |
Yes |
Yes |
Yes |
Cluster management |
SQL editor |
Yes |
Yes |
Yes |
Yes |
Monitoring panel (DMS) |
Yes |
Yes |
Yes |
No |
|
Monitoring metrics (Cloud Eye) |
Yes |
Yes |
Yes |
No |
|
Restart |
Yes |
Yes |
Yes |
Yes |
|
Start |
No |
No |
No |
No |
|
Stop |
No |
No |
No |
No |
|
Scaling |
Yes |
Yes |
Yes |
No |
|
Scale-in |
Yes |
Yes |
Yes |
No |
|
Redistributing data |
Yes |
Yes (Note 1) |
Yes |
No |
|
Viewing redistribution details |
Yes |
Yes |
Yes |
No |
|
Changing the node flavor |
Yes |
Yes |
Yes |
Yes |
|
Changing all specifications |
Yes |
No |
Yes |
No |
|
Resetting passwords |
Yes |
Yes |
Yes |
Yes |
|
Creating snapshots |
Yes |
Yes |
Yes |
No |
|
Canceling read-only status |
Yes |
Yes |
Yes |
Yes |
|
Deletion |
Yes |
Yes |
Yes |
Yes |
|
Managing CNs |
Yes |
Yes |
Yes |
No |
|
Storage space scaling |
Yes |
Yes |
Yes |
Yes |
|
Basic Information |
Basic information |
Yes |
Yes |
Yes |
Yes |
ELB |
Yes |
Yes |
Yes |
N |
|
Resource Management |
Yes |
Yes |
Yes |
N |
|
Intelligent O&M |
Yes |
Yes |
Yes |
No |
|
Logical cluster |
Yes |
Yes |
Yes |
N |
|
Snapshot |
Yes |
Yes |
Yes |
No |
|
Parameter modifications |
Yes |
Yes |
Yes |
Yes |
|
Security settings |
Yes |
Yes |
Yes |
Yes |
|
MRS data sources |
Yes |
Yes |
Yes |
No |
|
Tags |
Yes |
Yes |
Yes |
Yes |
|
Node management |
Yes |
Yes |
Yes |
No |
|
Upgrade management |
Yes |
Yes |
Yes |
No |
|
Logging |
Yes |
Yes |
Yes |
No |
|
User management |
Yes |
Yes |
Yes |
No |
|
Integration |
Data migration |
Yes |
Yes |
Yes |
No |
DR management |
DR management |
Yes |
No |
Yes |
No |
Snapshot management |
Restoration |
Yes |
Yes |
Yes |
No |
Deletion |
Yes |
Yes |
Yes |
No |
|
Copy |
Yes |
Yes |
Yes |
No |
|
Incident management |
Event management (general) |
Yes |
Yes |
Yes |
Yes |
Alarm management |
Alarm management |
Yes |
Yes |
Yes |
Yes |
Client connections |
Client connections |
Yes |
Yes |
Yes |
Yes |
Others |
Inspection |
Yes |
Yes |
Yes |
No |
Intelligent O&M |
Yes |
Yes |
Yes |
No |
|
Node restoration |
Yes |
Yes |
Yes |
No |
|
Warm backup on the tenant side |
Yes |
Yes |
Yes |
No |
- Note 1: The storage-compute separated table stores data on OBS, eliminating the need for redistribution. However, metadata and indexes are stored locally and must still be redistributed. Redistributing a table with separated storage and compute nodes only allows for read operations, and metadata redistribution is fast. However, creating an index on the table can affect redistribution performance, with completion time increasing with index data volume. During this period, the table is read-only and cannot be modified.
- A hybrid data warehouse deployed in standalone mode cannot be changed to the distributed mode. Scaling, logical cluster operations, and resource management are not supported.
- A hybrid data warehouse deployed in standalone mode does not support snapshots, DMS monitoring, or MRS data sources.
- In a hybrid data warehouse deployed in standalone mode, the original syntax for specifying distribution columns will be ignored. Scheduled jobs, the sequence type, HDFS/OBS foreign table import and export, multi-temperature storage, and auto-increment partitioned tables are not supported. OBS foreign table import and export are supported in 8.2.0 and later versions.
- Only DWS 3.0 clusters of 9.0.2 and later versions support the snapshot function.
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