Applied Dimensionality

Most of the systems we implement don’t live in vacuum, they have to communicate with lots of neighbours. People often overlook the ability to call stored procedures from Cognos BI reports as a method of running some action, so I’d like to steal your 5 minutes for explaining how to use it to build better systems.

I’ve updated TM1 Stress \ Load Testing Tool over the weekend (vesrion 0.2, probably).

Now it handles memory a lot better and has a new parameter called seconds_between_actions in session configurations. Parameter is quite obvious, it just says how long will the coffee break between reading and writing bursts be within each session. To  make things less determined, the break is not exactly seconds_between_actions, but a random number that is less than seconds_between_actions. My coffee breaks never go for as long as I plan them, for sure.

Are you using Cognos BI seriously? Have you seen IBM SDK utilities? Keep in mind that link changes every now and then, I usually have to regoogle it. Some of them are really very good and I’ve used them a few times already. Slowly but surely, IBM is adding a few missing bits to the puzzle.

My working process these includes tossing around lots of virtual machines, so I’ve gathered a couple of tricks. Let’s talk about getting your back better (this post) and lightening your CapEx (next one).

Continuing our weekly, monthly, quarterly instalments, let’s talk about Cognos log files management.

I’m really puzzled by the fact that whenever I walk in on a clustered Cognos install, error logging is always set up just wrong!  Meaning not the way I like it :)

I was decribing the 4-year old trick of using Cognos server cluster to build powercubes and got a new idea.

Really, PowerPlay cubes building via scripts is a so 1990s, 21st century is for enterprise scale, failover, monitoring and you-know-the-pitch.

I’m playing around with some TM1 ideas and all of them require some sort of sparsity analysis. And since TM1 supports MDX (to some extent, to say it mildly) and I like MDX and used it a lot with Essbase, I thought it’d be wonderful to use MDX.

Ever found yourself wondering what users are really there in your BI Consumers or any other group? Sure, you’ve got a few of them explicitly listed there (bad practice) but mostly you’ve got just a list of other groups like “Western Division”, “Marketing” and all those (good practice). And they’re, most likely, nested into each other a few times (like Western Division OpEx and Marketing Asia).  Or, looking at it from totally other point of view — what groups Jack Smith is really in (again, with all these nesting ones)? Is he a member of Western Division or what?