我对 Microstrategy 了解不多，但一位曾使用过两者的朋友说，它的前端很棒，后端却很弱。 他相当喜欢 OBIEE，尽管他偏向于开发人员。 在该工具中构建物理、逻辑和表示元数据确实非常容易。 与所有仓库一样，辛苦的工作主要是在 ETL 中，其次是良好的 BA 工作和 DB 中良好的性能调优。
I've been involved in 20 OBIEE projects for the past 6 years. It's a good ROLAP product. It has a flexible, mostly intuitive UI that end users typically like. HTML, Javascript, and some Flash (charts) is used for presentation. There is a presentation server that runs under a web server (or app server) and the core of the tool, the analytics engine runs separately. Generally speaking the tool generates efficient SQL. Performance overall is generally good, but is dependent on the source data structures and the types of reporting being attempted.
The metadata layer is well designed and extremely (almost to a fault) flexible, though it could stand to be much better documented. The tool expects to work with traditional star schemas. It works well with all the major RDBMSs. It has multi-level caching and is very flexible with authentication, functionality access, and data security. It doesn't do everything I'd like it to do, but taken as a whole, it's a first class application. Most of it's flaws are little things, there really isn't anything major. I'd say from a presentation perspective it's prompting is far weaker than it could be.
It's not a cube tool (though it can source data from cubes) and it's not meant to be a tool for generating massive reports (long lists and massive data sets presented to end users) though it does get used that way. If anything its biggest flaw is probably the cost, but it's probably comparable to all the other enterprise players.
I don't know a lot about Microstrategy, but a friend who has worked with both says it has a great front end and a weak back end. He prefers OBIEE considerably, though he's developer biased. It really is quite easy to build physical, logical, and presentation metadata in the tool. As with all warehouses, the hard work is mostly in the ETL, followed by good BA work and good performance tuning in the DB.
If you are Going for OBIEE, Go for the 11g version, It has Lot many Advantages, Advanced Features over the 10g. The 10g version is based on the OC4J, where as the 11g is based on the weblogic server. I haave worked on both the Administration part and BI Answers part, The Tools seems Quite easy in both. Building the Repository in Admin Part or Creating Dashboards and Reports on the Answers Part.
Well to speak on the Flaws, We faced a lot of Problem while installing, with very minimalistic knowledge, Ofcourse both on Weblogic server and OBIEE. But that should not be a problem if you have good enough Resource to do it. Again a major Requirement is the Hardware, For the OBIEE 11g, Experts say 8gb RAM is minimum requirement. Well we have worked with 2GB RAM's as well but it was really very Slow. So if you have an excellent hardware and trained staff, Its a great tool.
I have used it in the past. I really like the architecture, but you could have a look around this link to see some more detailed descriptions on how people work with it: http://www.rittmanmead.com/blog/
发布评论
评论（3）
过去 6 年我参与了 20 个 OBIEE 项目。 这是一个很好的ROLAP产品。 它具有最终用户通常喜欢的灵活、直观的用户界面。 HTML、Javascript 和一些 Flash（图表）用于演示。 有一个在 Web 服务器（或应用程序服务器）下运行的演示服务器和该工具的核心，即分析引擎单独运行。 一般来说，该工具会生成高效的 SQL。 总体性能总体不错，但取决于源数据结构和尝试的报告类型。
元数据层设计良好，并且极其（几乎是错误的）灵活，尽管它可以有更好的文档记录。 该工具预计可以与传统的星型模式一起使用。 它与所有主要的 RDBMS 都能很好地配合。 它具有多级缓存，并且在身份验证、功能访问和数据安全方面非常灵活。 它并没有完成我想要它做的所有事情，但作为一个整体，它是一个一流的应用程序。 大部分的缺陷都是小问题，确实没有什么大问题。 我想说，从演示的角度来看，它的提示比应有的要弱得多。
它不是一个多维数据集工具（尽管它可以从多维数据集获取数据），并且它并不是用于生成大量报告（向最终用户呈现的长列表和大量数据集）的工具，尽管它确实以这种方式使用。 如果说它最大的缺陷的话，可能就是成本，但它可能与所有其他企业参与者相当。
我对 Microstrategy 了解不多，但一位曾使用过两者的朋友说，它的前端很棒，后端却很弱。 他相当喜欢 OBIEE，尽管他偏向于开发人员。 在该工具中构建物理、逻辑和表示元数据确实非常容易。 与所有仓库一样，辛苦的工作主要是在 ETL 中，其次是良好的 BA 工作和 DB 中良好的性能调优。
I've been involved in 20 OBIEE projects for the past 6 years. It's a good ROLAP product. It has a flexible, mostly intuitive UI that end users typically like. HTML, Javascript, and some Flash (charts) is used for presentation. There is a presentation server that runs under a web server (or app server) and the core of the tool, the analytics engine runs separately. Generally speaking the tool generates efficient SQL. Performance overall is generally good, but is dependent on the source data structures and the types of reporting being attempted.
The metadata layer is well designed and extremely (almost to a fault) flexible, though it could stand to be much better documented. The tool expects to work with traditional star schemas. It works well with all the major RDBMSs. It has multi-level caching and is very flexible with authentication, functionality access, and data security. It doesn't do everything I'd like it to do, but taken as a whole, it's a first class application. Most of it's flaws are little things, there really isn't anything major. I'd say from a presentation perspective it's prompting is far weaker than it could be.
It's not a cube tool (though it can source data from cubes) and it's not meant to be a tool for generating massive reports (long lists and massive data sets presented to end users) though it does get used that way. If anything its biggest flaw is probably the cost, but it's probably comparable to all the other enterprise players.
I don't know a lot about Microstrategy, but a friend who has worked with both says it has a great front end and a weak back end. He prefers OBIEE considerably, though he's developer biased. It really is quite easy to build physical, logical, and presentation metadata in the tool. As with all warehouses, the hard work is mostly in the ETL, followed by good BA work and good performance tuning in the DB.
如果您要使用 OBIEE，请选择 11g 版本，它比 10g 有很多优势和高级功能。
10g 版本基于 OC4J，而 11g 版本基于 weblogic 服务器。 我曾从事过管理部分和 BI 答案部分的工作，这两个部分的工具似乎都很简单。
在管理部分构建存储库或在答案部分创建仪表板和报告。
好吧，谈谈缺陷，我们在安装时遇到了很多问题，而且知识非常简单，当然在 Weblogic 服务器和 OBIEE 上都是如此。 但如果您有足够的资源来做到这一点，那应该不是问题。 同样，一个主要要求是硬件，对于 OBIEE 11g，专家表示 8GB RAM 是最低要求。 我们也使用过 2GB RAM，但速度确实非常慢。
因此，如果您拥有出色的硬件和训练有素的员工，那么它是一个很棒的工具。
If you are Going for OBIEE, Go for the 11g version, It has Lot many Advantages, Advanced Features over the 10g.
The 10g version is based on the OC4J, where as the 11g is based on the weblogic server. I haave worked on both the Administration part and BI Answers part, The Tools seems Quite easy in both.
Building the Repository in Admin Part or Creating Dashboards and Reports on the Answers Part.
Well to speak on the Flaws, We faced a lot of Problem while installing, with very minimalistic knowledge, Ofcourse both on Weblogic server and OBIEE. But that should not be a problem if you have good enough Resource to do it. Again a major Requirement is the Hardware, For the OBIEE 11g, Experts say 8gb RAM is minimum requirement. Well we have worked with 2GB RAM's as well but it was really very Slow.
So if you have an excellent hardware and trained staff, Its a great tool.
我过去用过它。 我真的很喜欢这个架构，但是您可以查看此链接，了解人们如何使用它的一些更详细的描述：http://www.rittmanmead.com/blog/
I have used it in the past. I really like the architecture, but you could have a look around this link to see some more detailed descriptions on how people work with it: http://www.rittmanmead.com/blog/