What is the future of Web Intelligence and Java?
Tag: Web Intelligence
Desktop Intelligence Compatibility Pack
Deski is not back… but Eric has a few thoughts.
End of the Road for Dashboards?
@ca_nicholls threw out an interesting tweet on August 1:
In memory capability will make dashboards obsolete, statement just made by SAP CEO Aus & NZ. Do you agree? I don’t.
This tweet has certainly piqued the interest of more than just a few at this point. It’s a pretty bold statement. Could it be a misquote? It’s possible. I definitely do not mean to discredit or disrespect @ca_nicholls in any way by that question, but let’s consider that he got it spot on…
For the record…I don’t think dashboards are going anywhere, but let’s talk about it.
Troubleshooting Long Running Reports
I caught a tweetstream the other day that Diversified Semantic Layer’s friend and past guest, Michael Welter, had a question on diagnosing and solving for long running queries in Web Intelligence (Webi)…at least I think it was Webi. I saw it fly by and really wanted to weigh in, but it got away from me. I did not necessarily see answers to Michael’s question in that time frame, so I wanted to take some things that occurred to me and that I use in my debugging process.
I may be overly sensitive to this topic, now that I think of it. My first employer had a very very large data warehouse (at the time, largest in the world every other month). While full of rich data, it was painfully slow and as a result BusinessObjects was the perceived as slow by the business. Let’s work on that. I’m going to keep this post within the confines of Webi. There may be similar settings and techniques that can apply to Crystal Reports, Xcelsius, Explorer, etc. (even Deski…sorry Jamie).
Xcelsius with BI Services and BW Variables
Over the last few weeks I’ve been working full steam on a project to lay Xcelsius on top of BW (Accelerated no less). One of the cool capabilities of BW to significantly improve performance over standard parameters is to use variables. Variables pass straight through from the BW query and look like a prompt in Webi. The variable is a parameter that gets passed to the BW query before it actually runs vs. being applied to the result set. This can net a significant performance gain.
The Program Job Server – Unappreciated at Best
Eric really loves the Program Job Server.
Drinking the Web Intelligence Kool-Aid
Moving from Desktop Intelligence to Web Intelligence
Optional Prompts with Default Values in Designer
Updated 4/12/2010 – I feel like a blockhead. I went to reference my own blog and found a copy and paste issue in my formula below. It’s fixed (I hope). Sorry!
Truth be told, today I felt like a total rookie. I got a requirement that screamed “don’t dare duplicate that report just so you can have a version to schedule and version to run on demand”. The requirement was to run a Web Intelligence report monthly through the job server (always running for the prior month when executed) but to also allow the user to open, refresh, and be prompted for a list of values. I spent a few minutes tinkering with some SQL that ultimately lead me to a simple pre-defined condition for my reports. I’m certain this has been blogged and forum posted to death by now, but I’m going to throw it out there for fun.