In most cases, IT personnel and data engineers analyze data based on data sources. This topic describes the data sources supported by Quick BI.
Supported data sources
The following table describes the database versions supported by Quick BI and the connection methods of the database.
In the preceding table, indicates that the shortcuts are supported, and indicates that the shortcuts are not supported.
Data Source | Data Source Type | Supported engine version | Connection mode with the database | ||||||
Classic network (internal network) | Internet connection (you need to add a whitelist on the interface) | VPC connection (if the connection is not available, try adding 100.104.0.0/16 whitelist) | Regions that can be supported by VPC | Whether the password is required | Supports SSH | Supports SSL | |||
MySQL | Alibaba Cloud | Version 5.5, 5.6, 5.7, or 8.0 | All regions | ||||||
Tencent Cloud | Version 5.5, 5.6, 5.7, or 8.0 | No | |||||||
Huawei Cloud | Version 5.5, 5.6, 5.7, or 8.0 | No | |||||||
Microsoft Cloud | Version 5.5, 5.6, 5.7, or 8.0 | No | |||||||
AWS | Version 5.5, 5.6, 5.7, or 8.0 | No | |||||||
Self-managed push channel | Version 5.5, 5.6, 5.7, or 8.0 | All regions | |||||||
Alibaba MaxCompute | Alibaba Cloud | 1.0, 2.0 version | No | ||||||
Alibaba AnalyticDB for MySQL | Alibaba Cloud | Version 3.0 | Only central regions are supported. | ||||||
Alibaba Cloud | Version 2.0 | No | |||||||
SQL Server | Alibaba Cloud | 2008 to 2022 version | All regions | ||||||
Tencent Cloud | 2008 to 2022 version | No | |||||||
Huawei Cloud | 2008 to 2022 version | No | |||||||
Microsoft Cloud | 2008 to 2022 version | No | |||||||
AWS | 2008 to 2022 version | No | |||||||
Self-managed push channel | 2008 to 2022 version | All regions | |||||||
PostgreSQL | Alibaba Cloud | 8.2 and later versions | Only central regions are supported. | ||||||
Tencent Cloud | 8.2 and later versions | No | |||||||
Huawei Cloud | 8.2 and later versions | No | |||||||
Microsoft Cloud | 8.2 and later versions | No | |||||||
AWS | 8.2 and later versions | No | |||||||
Self-managed push channel | 8.2 and later versions | All regions | |||||||
Alibaba Hologres | Alibaba Cloud | All regions | |||||||
ClickHouse | Alibaba Cloud | 20.3, 22.8 version | All regions | ||||||
Self-managed push channel | 20.3, 22.8 version | All regions | |||||||
Alibaba AnalyticDB for PostgreSQL | Alibaba Cloud | Version 4.3 or 6.0 | All regions | ||||||
Presto | / | prestoDB 0.219 version, trino 354 or later | All regions | ||||||
Alibaba Data Lake Analytics | Alibaba Cloud | No | |||||||
Alibaba PolarDB for MySQL | Alibaba Cloud | Versions 5.6, 5.7, 8.0.1, and 8.0.2 | Only central regions are supported. | ||||||
Oracle | Alibaba Cloud | 11.0 version | All regions | ||||||
Hive | / | Apache hive 2.0.1 to 2.3.3 | No | ||||||
Alibaba PolarDB Distributed Edition (DRDS and Alibaba PolarDB-X) | Alibaba Cloud | 1.0, 2.0 version | All regions | ||||||
Alibaba PolarDB for PostgreSQL | Alibaba Cloud | 11.0, 14.0 version | Only central regions are supported. | ||||||
SAP HANA | Self-managed push channel | Version 2.0 | All regions | ||||||
Alibaba PolarDB for Oracle (formerly PPAS) | Alibaba Cloud | 1.0, 2.0 version | All regions | ||||||
Alibaba Lindorm wide table | Alibaba Cloud | No | |||||||
IBM DB2 LUW | Self-managed push channel | DB2 v11.1.4.4 | All regions | ||||||
Vertica | Self-managed push channel | Vertic Version Analytic Database v9.2.0-7 | All regions | ||||||
Alibaba LindormTSDB | Alibaba Cloud | No | |||||||
Alibaba OceanBase | Alibaba Cloud | No | |||||||
SAP IQ (Sybase IQ) | Self-managed push channel | SAP IQ/16.1.030.1031/10645 /Version | All regions | ||||||
Kingbase | Self-managed push channel | Version 7.1.2 | All regions | ||||||
Gbase | Self-managed push channel | 8.6, 9.5 version | All regions | ||||||
Impala | Self-managed push channel | V2.10.0 and V3.4.0 | All regions | ||||||
Snowflake | Self-managed push channel | All regions | |||||||
Kylin | Self-managed push channel | Version 3.0 | All regions | ||||||
Spark SQL | Self-managed push channel | Version 3.1.2 | All regions | ||||||
MongoDB | Self-managed push channel | Version 5.7.12 | All regions | ||||||
Apache Doris | Self-managed push channel | Version 1.2.4 | All regions | ||||||
Dameng (DM) | Self-managed push channel | 7.0, 8.0 version | All regions | ||||||
StarRocks | Alibaba Cloud | Version 2.0.1 | All regions | ||||||
Self-managed push channel | Version 2.0.1 | All regions | |||||||
SelectDB | Self-managed push channel | All regions | |||||||
Alibaba SLS | Alibaba Cloud | No | |||||||
Huawei GaussDB | Huawei Cloud | No | |||||||
Huawei GaussDB(DWS) | Huawei Cloud | No | |||||||
Elasticsearch | Alibaba Cloud | 7.8.1 and later versions, and requires X-Pack plug-ins (platinum version) | No | ||||||
Self-managed push channel | 7.8.1 and later versions, and requires X-Pack plug-ins (platinum version) | No | |||||||
TDSQL-H LibraDB | Tencent Cloud | No |
Network requirements
When you add a data source, take note of the following network requirements:
ApsaraDB RDS instances in a VPC can access Quick BI by using a public domain name. However, only ApsaraDB RDS instances that run the MySQL or SQL Server engine in a VPC can access Quick BI by using an internal domain name.
ApsaraDB RDS instances in the classic network can access Quick BI by using either a public domain name or an internal domain name. Before you connect an ApsaraDB RDS instance to Quick BI by using a public domain name, you must configure an IP address whitelist for the ApsaraDB RDS instance. For more information, see Configure a whitelist
Quick BI can be connected over the Internet.
User-created MySQL or SQL Server databases hosted on an ECS instance in a VPC can access Quick BI by using an internal domain name.
More operations
For more operations that can be performed on data sources, see the following topics: