Search results for query: *

Indeed, the more tables the better. Users will inevitably decide to try and link the data if any possible link exists. If they do this between universes you cannot see how it is being done, and trust me the first you'll hear of it is when the phone rings and someon starts telling you your Data...

I believe the actual overhead on varchar over char is 2 bytes per row, so if your field has a range of lengths of less than 2 you're better off using char - as MDXer said abbreviations, country codes etc... are about all it's good for.

Materialised views are essentially a simple SQL version of an aggregate table. For relatively simple straight aggregate tables you can save time & effort with materialised views. If you table requires more complex criteria resulting in a SQL statement involving mulitple sub-queries (which will...

I can probably make light of them... ;-) I did a v4 Implementation Path course many years ago - a the time that was the full (BO sanctioned) training scheme and was largely not worth the paper it was printed on - from a development perspective. Resonably solid grounding in basic user report...

You could use a subquery in the where clause - either create a condition in the universe: WHERE: ah.seq_num = (select max(maxresults.seq_num) from action_hist maxresults where ah.case_id = maxresults.case_id group by maxresults.case_id) Add it to your query (containing the ah.case_id...

I'm a little confused as to wha you're trying to do here. Which default values?

Ah, the dreaded context's issue... You can Sum it (on a different sheet) but you'll need to use Calculation Contexts - there's a very helpful, clear and concise chapter on them in the BO User Guide...;-) To give an example - =Sum((If <Time Between IC and End of IS> < 2 Then 1 Else 0) In...

This is a problem with your OBDC set-up. The following solution may vary slightly depending on which dB you are using, for WebI you'll need to check your server config, for Full Client your local config... Under the BO install directory (usually c:\program files\business objects - on windows)...

Does anyone have any idea whether there is a performance difference in DB2 between coding 2 separate joins (>= & <=) or just using a BETWEEN join? If so which is faster?