MATRIX UAB - SAP Crystal Reports, Business Objects software

Business Objects Crystal Enterprise version 10 architecture
versus
Microsoft SQL Server 2000 Reporting Services architecture

Some conclusions of comparison

Our original goal is that every reader builds their own conclusions from the data we include here. However, due to the length and structure of the current document; we agree that this isn't a quick task. Also, our first draft reviewers suggest having some executive summary or conclusions section. This is specially the case in more subtle issues, may be closer to the approach than to the features itself. So, we've done the following summary. However we cannot emphasize enough that this is solely our current opinion at the moment of finishing the report, and that, by their own nature, an opinion is mutable and probably not enough objective.

Business Objects Crystal Decisions solution:

Business Objects Crystal product line offers a very powerful and mature platform to build reporting and business intelligence solutions. It is well connected to most popular customer enterprise solutions in several platforms, and has end user, developer and administration focused modules.
Strengths
- Being at version 10, that maturity arises in the comprehensiveness of the product line, giving answers to almost any requirement a customer can have. Against that, having an history reverts on a clumsy/mixed architecture in some areas
- Connectivity kits with ERP/CRM popular products
- Multiplatform support for web servers, e-mail servers, development environments and database engines
- End user suitability, both for power and entry users
- If needed, can be used as a standalone product, without requiring a server
- It is bundled with many, many products, including Microsoft ones
- Future directions, due to prominent role Crystal Decisions products will play in Business Objects product family architecture
Weaknesses
- Extensibility is not easy enough, not for the masses
- Too many versions on the street affect product awareness and reputation. Because Crystal Reports is bundled with so many products, users "know" Crystal according to the version they're currently using, that is, sometimes, 3 versions old, actually.
- Note: Some writers will include "being proprietary" here. However, we must state that, by no means, Crystal solution is, currently, more proprietary than Microsoft one. Having an XML report format definition isn't enough until it is an official standard. Also, Reporting Services has an object model exactly as Crystal has their own, both are build with current technologies and equally suitable for a modern development environment.

Microsoft SQL Server Reporting Services solution:

Microsoft offers a very good starting platform to build reporting solutions. It is clear that Microsoft relies on third parties to extend the platform on different areas like ERP/CRM support or end user friendly report designers and viewers. As anyone can expect, it relies on the rest of Microsoft product line for complementary tasks, this will be good for some customers and a barrier for others.
Strengths
- "Microsoft-way" extensibility. We expect to have alternatives for all weaknesses, and to have options for any data, render and delivery extension with a potential market in the short term - Licensing for current SQL Server customers
- Flexibility at report design. However, this strength must be tested against further real world customer experiences
Weaknesses
- As a version 1, youngness arises in the form of lack of options in some areas. Opposing to that, being young or recent, allows for an up to date, modern, architecture, that may be easier to grow and evolve
- Depends on SQL Server when accessing other vendor sources (Oracle, DB2...). Some customers will not like to put another database engine in their catalog not to use it actually. This is similar to what happens with DTS (Data Transformation Services) functionality.
- Dependability on Visual Studio .Net IDE for report design, not suitable for end users. This can be a barrier for IT departments to delegate report creation and editing to end users. However, we expect having third party offerings in the short term, maybe coming from Business Objects itself.
- Not suitable for ISVs that doesn't rely on SQL Server for smaller installations. This is one of the most valued/requested/upgraded Crystal Reports feature. That's the reason why Crystal Reports for .Net is included in the current version of Visual Studio .Net and will be included, as announced, in the next one, code named Whidbey.