Direct-Connected Data

Version

Application Scenario

The dataset with the direct connection attribute is formed by FineBI directly requesting data from the database. Therefore, data does not need to be extracted to FineBI and updated.

Notes for Direct-Connected Data

• You are not advised to use direct-connected data in large-data-volume scenarios in low-performance databases (such as MySQL with over ten million data).

• The Row to Column, Column to Row, and Self-Looping Column functions are not supported in direct connection datasets.

• Fusion analyses (including Association, Union All, and Join) between two direct connection datasets from different databases are not supported.

Direct-Connected Data Switchover

Choose Public Data and click the setting icon to select Extracted Data or Direct-Connected Data, as shown in the following figure.

Cache Setting

You can set BI Direct Connect Cache Settings for direct connection datasets.

By default, FineBI clears the cache and resends the latest data of the SQL request to the database every 600 seconds. That is, FineBI refreshes data every 600 seconds. You can adjust the refresh time interval. For details, see BI Cache.

The Default Data Volume That Can Be Viewed in the Edit Mode

You can only view the first 10,000 records in the edit mode. Therefore, selecting View All Data may be ineffective for components created through datasets with the direct connection attribute.

Asynchronization Between the Database and BI Data

• If you modify the table structure (for example, added/deleted columns) in the database, the modifications on the table structure will not be immediately updated on the data preparation page. You need to edit the table to select the added fields. If fields that are highlighted in red exist, you need to deselect them.

• FineBI has the default cache setting. Data is refreshed every 600 seconds. Therefore, asynchronization may exist. For details, see section "Cache Setting."