{"id":2543,"date":"2020-11-10T15:47:17","date_gmt":"2020-11-10T15:47:17","guid":{"rendered":"https:\/\/www.biconnector.com\/blog\/?p=2543"},"modified":"2021-05-14T11:34:17","modified_gmt":"2021-05-14T11:34:17","slug":"how-to-optimize-query-performance-when-connecting-power-bi-to-obiee","status":"publish","type":"post","link":"https:\/\/www.biconnector.com\/blog\/how-to-optimize-query-performance-when-connecting-power-bi-to-obiee\/","title":{"rendered":"How to Optimize Query Performance When Connecting Power BI to OBIEE?"},"content":{"rendered":"
When connecting Power BI to Oracle Business Intelligence Enterprise Edition (OBIEE), the users could encounter performance issues for certain queries.<\/p>\n
In this blog post, we\u2019ll see how you can optimize the query performance when connecting Power BI to OBIEE<\/a> (or Oracle Analytics Cloud (OAC)<\/a> \/ Oracle Analytics Server (OAS) ) via BI Connector.<\/p>\n Let’s dive into the details!<\/p>\n You can see the following 3 parameters in the Query Limits section of the BI Connector Advanced Settings window:<\/p>\n The query limits section is highlighted in the below image. Now let\u2019s take a quick look at each of these parameters:<\/p>\n <\/b><\/b><\/b><\/b><\/b><\/b> For example, let\u2019s consider an OBIEE report you want to analyze has more than 1,000,000 rows. But you want to analyze just the first 100,000 rows.<\/p>\n In that case, you can set the Maximum number of rows per report as 100,000. So, BI Connector would fetch only the first 100,000 rows for all your queries, and ignore the rest of the rows, if there\u2019s any. <\/b><\/b><\/b><\/b><\/b><\/b> For example, let\u2019s say you want to analyze an OBIEE report with 100,000 rows. In this case, you can set the Maximum number of rows per fetch as 50,000. Therefore, BI Connector will fetch the first 50,000 rows in the first batch, and the remaining in the next batch.<\/p>\n The setting will help you avoid time-out errors as well. But you should ensure that the maximum number of rows per fetch is set to be less than the ResultRowLimit<\/b> specified in your OBIEE instance config file<\/b>. <\/b><\/b><\/b><\/b><\/b><\/b> If the value you set in this parameter is less than the number of columns in your OBIEE report, you\u2019ll see an error message. BI Connector’s recommendation is to reduce the number of columns as much as possible to improve query performance.<\/p>\n With these 3 settings in BI Connector: Advanced Settings window, you can easily optimize your query performance when connecting Power BI to OBIEE or OAC or OAS.<\/p>\n Another simple technique (that\u2019s often overlooked) to improve your query performance is to apply filters! You can easily apply filters, and narrow down to the data that you need for your analysis.<\/p>\n Important Note: From BI Connector v5.3, the Maximum number of rows per report and Maximum number of Columns per query parameters are deprecated. For more info, please refer to this post<\/a>.<\/p>\n In fact, applying filters and the 3 parameters we just saw are a part of the 9 best practices we curated for connecting Power BI to OBIEE<\/b><\/a> (in a recent webinar), after analyzing of 1000s of customer support tickets and 100s of customer interactions.<\/p>\nFine-tune BI Connector Query Limit parameters<\/h1>\n
\n
\n<\/p>\n\n
\nThe parameter, Maximum number of rows per report, help you to restrict the maximum number of rows you want BI Connector to fetch for a query.<\/p>\n
\n<\/b><\/p>\n\n
\nThe parameter, Maximum number of rows per fetch, will help you avoid OBIEE time-out errors smartly.<\/p>\n
\nIf you\u2019re not aware of the limit set in the ResultRowLimit parameter, you can have a chat with your OBIEE administrator, and get that information.
\n<\/b><\/p>\n\n
\nThe parameter, Maximum number of columns per query, will help you restrict the number of columns BI Connector fetches from your OBIEE<\/a> for your analysis.
\nAlways have the Maximum number of columns per query value to be set more than the number of columns you want to analyze<\/b>.<\/p>\n