we have a very wide order line table. are there any best practices for dealing with this. like
1 break up the table into tables
2. use large block sizes
I don't see any performance issues with v5.1 Zabo,2.7.3. We are running 500 users globaly, Oracle db, and a 2 box cluster. Both boxes are small, 2 and 1 cpus respectivly.
How many rows is your query bringing back. How many data providers. I hope you are not trying etl. If doing etl use full...
I guess I meant that businessObjects takes the results of a query a loads a local database. Aggregrations are then performed against the local database.
I belived Cystal stores summaries in separate lists. BusinessObject is limited to the number of rows that can be displayed becuase it has to...
Thanks for the info. You are right sql is a better approach. However, some times with large data volumes or if the dimension data is in a spread sheet having this capabiltiy is powerful.
You can use the mangero Universe to compare universes. I have a report that can compare joins and contexts. I don't think it would be hard to compare objects and classes. Send me you email addresses and I can send you the report.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.