you are absolutely correct. I tend to base my comments on my experiences
and I seem to spend an inordinate amount of time on multi-TB data warehouses
and with lots and lots of concurrent users. I guess its become my
specialty. In that respect, I preferred the IA product (it will never be the
same now that Sterling owns it) for the reasons you mentioned - scalability,
doesn't create temp tables, has its own engine, supports large number of
users. Also, until recently, I spent most of my time on the back end issues
that are so prevalent in VLDB. If I could get a tool to scale, then I would
find a way to get the users to get their info from it. Not the best approach
and certainly not the one I take now.
angus2_at_my-deja.com wrote in message <85g376$js9$1_at_nnrp1.deja.com>...
>My opinion of Eureka is rather different, at least from the ROLAP
>perspective, especially in regards to Strategy being the best high-end
>ROLAP tool. In my opinion, the user interface leaves a lot to be
>desired, metadata management can only effectively be done at the
>database level, and the product doesn't have very good support for some
>simple metrics, such as rankings (yes, it does support rankings, but
>only if you include the rank as a separate metric, and retrieve all of
>the data). I also found creating advanced metrics fairly difficult and
>counter intuitive. I've also discovered some bandwidth issues if the
>server is placed on a separate platform from the database.
>
>I typically would recommend MicroStrategy before Eureka because the
>interface is much more mature for both Agent and Web, metadata
>management is much less database invasive, and I find metric and filter
>creation to be much easier. They also released InfoCenter to compete
>with Eureka:Portal, and it's a very clean implementation in my opinion
>(if you believe in the whole portal hype, which I still think is a
>debatable topic).
>
>Now, just so I don't come off too biased, Eureka does appear to be more
>scalable with regards to users and reports. It also doesn't use up so
>much temp space on the database, which can be a DBA nightmare. I think
>that it's a decent tool, but far from being 'The Best ROLAP tool'.
>
>
Received on Tue Jan 11 2000 - 19:04:34 CST
