Forum Discussion
Power BI Direct Connection to SAP HANA Production Database
Hello,
I would like to ask about best practices and licensing considerations when connecting Power BI directly to an SAP HANA production database.
Currently, we are using a copy of our SAP HANA database as the source for our Power BI reports. This creates delays because the copied database must be refreshed regularly, meaning our reports do not contain live data.
Since Power BI has native SAP HANA integration, I would like to understand whether it is technically supported and considered best practice to connect Power BI directly to an SAP HANA production database for reporting purposes.
I would also like to know whether this could potentially breach SAP licensing agreements or usage policies, and whether Microsoft and SAP recommend a specific architecture for near real-time or live reporting.
Any guidance or experiences with similar setups would be greatly appreciated.
Thank you.
Hi SantaT
Connecting Power BI directly to a live production SAP HANA database is fully supported by Microsoft via its native database connector, but doing so carries severe operational risks and potential licensing violations that make it a discouraged practice.
From a performance standpoint, querying a live transactional production environment directly for real-time reporting is highly risky; Power BI's DirectQuery mode translates user dashboard interactions into massive, unoptimized SQL statements that strike the underlying database engine simultaneously. This can quickly exhaust CPU and thread resources on your production HANA node, leading to severe concurrency bottlenecks and lagging out the core transactional operations of your business.
From a compliance perspective, you run a very high risk of breaching your SAP contractual agreements due to SAP’s Indirect Access (Digital Access) policies. If your enterprise operates under a Runtime License for SAP HANA (where the database is strictly bundled to only power the core SAP ERP application), connecting a third-party front-end tool like Power BI to pull raw data directly from the underlying tables is explicitly prohibited. Even if you have a Full-Use Database License, exposing this direct backdoor connection to dashboard users who do not possess a matching, active SAP Named User license can trigger massive financial penalties during an audit, as SAP classifies automated external data retrieval as actionable platform consumption.
To achieve near real-time reporting without crashing your production environment or failing a compliance audit, Microsoft and SAP recommend routing your data through an application-driven semantic layer rather than a direct database connection. The industry best practice is to build ABAP Core Data Services (CDS) views or HANA Calculation Views inside the SAP layer, expose them securely as OData Services, and connect Power BI using the native OData or SAP Business Warehouse (BW) connectors. This framework allows you to implement Single Sign-On (SSO) via Kerberos Constrained Delegation, meaning Power BI handles data requests by impersonating the individual user’s authenticated SAP profile—which completely eliminates indirect access compliance risks, preserves SAP’s internal application-level security roles, and allows the SAP engine to safely throttle and cache incoming query traffic.
5 Replies
Hi SantaT
Connecting Power BI directly to a live production SAP HANA database is fully supported by Microsoft via its native database connector, but doing so carries severe operational risks and potential licensing violations that make it a discouraged practice.
From a performance standpoint, querying a live transactional production environment directly for real-time reporting is highly risky; Power BI's DirectQuery mode translates user dashboard interactions into massive, unoptimized SQL statements that strike the underlying database engine simultaneously. This can quickly exhaust CPU and thread resources on your production HANA node, leading to severe concurrency bottlenecks and lagging out the core transactional operations of your business.
From a compliance perspective, you run a very high risk of breaching your SAP contractual agreements due to SAP’s Indirect Access (Digital Access) policies. If your enterprise operates under a Runtime License for SAP HANA (where the database is strictly bundled to only power the core SAP ERP application), connecting a third-party front-end tool like Power BI to pull raw data directly from the underlying tables is explicitly prohibited. Even if you have a Full-Use Database License, exposing this direct backdoor connection to dashboard users who do not possess a matching, active SAP Named User license can trigger massive financial penalties during an audit, as SAP classifies automated external data retrieval as actionable platform consumption.
To achieve near real-time reporting without crashing your production environment or failing a compliance audit, Microsoft and SAP recommend routing your data through an application-driven semantic layer rather than a direct database connection. The industry best practice is to build ABAP Core Data Services (CDS) views or HANA Calculation Views inside the SAP layer, expose them securely as OData Services, and connect Power BI using the native OData or SAP Business Warehouse (BW) connectors. This framework allows you to implement Single Sign-On (SSO) via Kerberos Constrained Delegation, meaning Power BI handles data requests by impersonating the individual user’s authenticated SAP profile—which completely eliminates indirect access compliance risks, preserves SAP’s internal application-level security roles, and allows the SAP engine to safely throttle and cache incoming query traffic.
It is not best practice, not by a long shot. Your reporting tool should never have direct access to the OLTP production database.
Keep your current setup.
Hi SantaT,
Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to lbendlin, for those inputs on this thread.Has your issue been resolved? If the response provided by the community member lbendlin, addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.
Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.
Thank you for using the Microsoft Community Forum.Hi SantaT,
Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.Thank you.
Hi SantaT
DirectQuery to SAP HANA is technically supported, but for S/4HANA reporting you may not need direct database access.
You may also evaluate Power BI Connector for SAP:
It reads S/4HANA data through SAP OData services and provides Power BI with an OData endpoint, with source-side filtering and support for Power BI scheduled and incremental refresh.
This can remove the need for a separate HANA reporting copy for this Power BI workload. It is an Import/refresh approach rather than live DirectQuery, so data freshness depends on the refresh cadence.
For direct HANA access, licensing implications should still be confirmed against your SAP contract with your SAP account team.
Documentation:
https://metricasoftware.com/docs/sap/Cheers,
Metrica Team
