This topic provides a summary of frequently asked questions regarding the creation of data sources.
Data source connection error
If you encounter a connection error with a data source, please check for the following common issues:
1. The whitelist is not added to the database
Access to the database is permitted only for devices listed in the whitelist, if such a feature is enabled. If the Quick BI whitelist is not configured in the database, the connection request will be rejected, leading to a data source connection error.
You must add the IP address segments of Quick BI for different network environments to your database's whitelist. A complete whitelist is available at the bottom of each data source connection page. Click Copy whitelist to copy it in full.
For ApsaraDB databases, you can click How to add followed by Set whitelist to learn how to add a whitelist. For self-managed databases, please refer to the respective database's help documentation to configure the whitelist.
2. VPC data source is not enabled when using an internal network address
If your "database address" is an external network address and a whitelist is configured, the network can connect and access the database directly without the need to enable "VPC data source".
However, if your "database address" is an internal network address, Quick BI must establish a connection through the Alibaba Cloud VPC network. In this case, you need to enable "VPC data source" and complete the necessary configuration. Instructions for each configuration item are available on the right side. Click Learn more for detailed help on the specific configuration items, assisting you in quickly finding the information required for setup.
3. Database account or AccessKey ID does not have the required permissions
A lack of necessary permissions for the database account or AccessKey ID used with Quick BI can lead to data source connection errors due to network connectivity issues or restrict access to certain features. For instance:
An AccessKey ID without Read permission for the destination instance may prevent access to the database instance, causing a connection error.
A database username lacking Create permission may prevent file uploads to the data source.
A database username without List permission may prevent the display of the data table list.
The permissions required may vary depending on the data source. When connecting, you can check the necessary account permissions from the connection prompts on the right side.
If you've ruled out the above reasons and still cannot connect to the data source, click the [Copy] button next to the error message to copy the error details. Then, contact us through the online consultation portal at the bottom right corner for professional service support and technical assistance in resolving the issue.
When directly connecting to a database, does each dashboard chart query the database every time it is refreshed? Does it support data caching?
When directly connected to a database, each dashboard chart query benefits from a default cache latency of one minute.
This means that unless the Enable real-time query button is activated, the chart query will utilize the default one-minute cache latency.
You can also configure query result caching at the dataset layer. For detailed instructions, see Query Caching.
After a local file uploaded to the data source is deleted, does the database table still exist?
Once a file uploaded to the data source is deleted, the corresponding automatically generated database table will be deleted as well.
After connecting a local MySQL to the data source, can Excel or CSV files still be imported as data sources?
Yes, you can import Excel or CSV files as data sources even after connecting a local MySQL database.
If the primary database address of the connected MySQL data source is changed to a secondary database address, what impact does it have on the dataset and dashboard?
If the table structure remains the same, there will be no impact on the dataset and dashboard.
