You know why i’ve started this blog in the first place? To get advice, of course. And today DesiCresnet shared a wonderfull piece of information concerning memory troubles in BI 8.3.
You know why i’ve started this blog in the first place? To get advice, of course. And today DesiCresnet shared a wonderfull piece of information concerning memory troubles in BI 8.3.
Tip of the day: Having common metadata layer for BI and Enterprise Planning is really cool, especially with the ability to load data from BI packages to EP via links. Just that it sometimes doesn’t work. But there are always some workarounds.
Just a quick hint and a reminder: there is a configuration option forcing Cognos to store temporary report results in memory rather than dropping them on disk. It’s especially usefull for DMR’s they are frequently cached on disk.
This post will be some extracts from a recent PoC, where we made a complex planning system including a rich scenario modeling part. So it was our first big TM1 + EP integration experience.
Yay, another post on Essbase )
Internal ASO storage structure is a block box, so unlike BSO. So while Roske haven’t writen a book on ASO option, we have to wonder in the dark.
Hm, I guess it’s the time for a first big essbase-related post. Today we’ll talk about data loading in ASO cube.
Those who’ve listened to our recent Oracle events presentations (russian TechForum 2008, BI Forum 2009), know that we’ve made a nice PoC project with SportMaster, consisting of loading their year’s worth of daily stock and sales data (around billion fact cells with over a million elements in products dimension). All in all, I’ve decided to post a write-up about how to achieve acceptable load speed on such volumes and tell a scary-story, with a detective twist and a happy ending.
Finally got my hands to installing and trying it.
Well, it looks nice, allows flash-based chart formating and turns Cognos portal pages into more dynamic “dashboards”.
But it’s strangely slow (tried on a couple of computers) and all in all looks kinda “alpha” and plugged in at last moment. Installation is not that easy too, it requires war building and deployement, procedures that not every BI consultant is aware off.
Correcting myself. I was ranting about MS SQL and Cognos interaction. I was totally wrong.
The problem, described shortly is:
The answer is simple: there’s no way Cognos can find out that these two databases are on the same physical server. But we can help old fella a bit, setting a datasource property (Content Manager Datasource) the same for both datasources. Therefore, the same datasource prefix will be generated for both tables and they’ll be regarded as residing on the same server. Query speed will increase dramatically.
Just a quick tip : this setting is stored in lastPublishCM property of fm.ini file
Gave me some trouble recently, when language changes led to unappropriate publish folder name. Moreover, we were not able to publish anything at all )
Okay, it has been almost half-a-year (oh, dears) since the last decent post on this blog. Russian one has suffered as well, I must note.
Reasons vary, but mostly it’s that I’ve been, you know, busy-busy. As I now start to reflect on it, it’s always a point of view thing and a question of self-control and ability to say no )