As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at email@example.com and provide your corporate email address, company, and name.
What is the source of your data? SQL Server, Oracle, et cetera.
Do you have joins in the business view? If so, run a request you consider inefficient with SQL Traces on to see how your joins are being generated.
Are you joining different data types? With or without a Business View, if you join two different database tables (eg. sequential to Oracle) you'll end up causing table scans that aren't very efficient.
Business Views don't necessarily give you faster access. They just encapsulate the Joins, Filters and organize your data in folders so report developers don't have to keep recreating them.
I would start with the SQL Trace.
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
While WebFOCUS allows you to create DEFINE based joins, there are some considerations. Specifically, if the defined field can't be translated into the same SQL statement, then you are effectively turning optimization off and potentially creating multiple SELECTS and asking WebFOCUS to join the answer sets. So, you have to look at the joins that use a virtual field and decide if there's a better way to create the join.