Third-Party Consumers (DW)---a Technical Reference Guide for Designing Mission-Critical DW Solutions
Want more guides like this one? Go to Technical Reference Guides for Designing Mission-Critical Solutions.
The world is full of products claiming to be in the Business Intelligence business. It is refreshing to note that the primary third-party products in this space include:
This is the order in terms of market-share. Business Objects was acquired by SAP in 2008 and Cognos by IBM in 2009. All three products are enterprise-class technologies and one or more of them exists in every major organization world-wide. All three products have been around since the mid-90’s and have matured accordingly. Their primary architecture requires of a powerful "BI server" where analytical & reporting data are intelligently cached. COGNOS helped to pioneer Multi-dimensional databases and have a long-standing reputation for high-speed cube-based analytics. All three provide very powerful and integrated metadata for reporting, and in the case of Business Objects, even for the ETL components.
Most third-party BI tools provide a metadata layer that insulates the BI Application from the underlying database. More recently the major contenders have developed elaborate metadata layers to simplify changes made to the underlying database. Be sure to understand how any changes to Microsoft SQL Server/PDW database design will be handled by the third-party tools.
Questions and Considerations
This section provides questions and issues to consider when working with your customers.
Determine how embedded the third-party tools are to the customer’s BI infrastructure:
Would they be willing to invest in converting to the Microsoft BI Stack?
If so, determine effort/time involved for conversion.
- Would they be willing to invest in converting to the Microsoft BI Stack?