Hi Ekram,
We generally do not recommend using a direct database connection for third-party reporting tools, as the Blue Prism database is utilized for operational purposes, is transactional in nature, and not designed for live/direct reporting by external tools.
Runtime Resources communicate to the database server via the BP Server with moderate to high volume. Notably, the transactional records are inserted into the database along with the updates being performed within the workflow table. Also, the logging information such as session logs, working queue logs, audit logs, schedule logs, and alerts are updated and stored frequently within the database.
Direct Database communication from an external application to the BPE Database will cause an additional burden over the operational performance in the database. This burden may lead to higher network latency between the Application Server and the database. Such network latency would impact the regular performance of the Runtime Resources and automations may be affected (as you describe).
We would recommend the following alternatives to a direct DB connection to a reporting tool:
- Utilize the in-built Data Gateways functionality to export reporting data to a separate system
- Utilize a tool that can be used to receive Session log data from Runtime Resources via an HTTP endpoint
- Create a reporting database/"mirror" environment which mimics your Production environment that can be used to retrieve reporting data
Edit: It looks like there's a few Power BI connectors available on the Digital Exchange that can make use of its available REST API endpoints. If you have a requirement to use Power BI, one of these may help with your stated purposes here:
https://digitalexchange.blueprism.com/dx/entry/3439/solution/power-bi-integration-2
https://digitalexchange.blueprism.com/dx/entry/3595/solution/power-bi-via-rpa-asset
https://digitalexchange.blueprism.com/dx/entry/3439/solution/microsoft-power-platform-connector-2
