Category Archives: Information Delivery

Technical articles on query, reporting analysis using Web Intelligence, Crystal Reports and other information delivery products

SAP Business Objects Data Services, SQL Server Express and Java 6

This articles looks at configuring the following components,

  • SAP Business Objects Data Services XI3.2
  • SQL Server Express 2005
  • Tomcat 5.5
  • JDK 1.6

The JDK 1.6 is not supported and indeed when trying to configure the Management Console to connect to a repository created in SQL Server Express 2005 we get the following error,

Java Runtime Environment (JRE) version 1.6 is not supported by this driver. Please use the JDBC 4 driver (sqljdbc4.jar) instead.

Solution

As the error suggests we need to upgrade the SQL Server JDBC driver to use a Type 4 JDBC driver.  The instructions below assume you have already setup a Data Integrator repository in SQL Server and also you are not using windows authentication to connect to this repository.
Continue reading

This article was published on February 19, 2010 by Al Gulland.

Limitations with using System Date part 1

Often in a reporting or data analysis scenario the analyst or business user wants to view data that is current, for example, sales for the current week or employee turnover for the current month etc. The analyst could create the report and then just enter whatever the current date is or in a operational report the user could enter today’s date when the report however this is obviously not ideal. Furthermore if we are creating a report that is scheduled to run daily then it would need to automatically choose the current date. This issue is easily and we create these reports using functions that return the system date for example SYSDATE in Oracle, getDate() in SQL Server or CurrentDate() in a Web Intelligence report. However although this at first seems an adequate solution there are limitations of using system date functions during the development and testing phases of a BI project.

Typically the development and test systems won’t have current data in their databases. Normally a sample data set is taken from the production or backup database that is, for example, a two month range of data taken from last year. Now any report created in dev or test that uses the system date to filter the data won’t return any data as there is no ‘current’ data in the underlying database.

This article looks at what we can do to allow proper development and testing of reports that will still use the correct system date when released to production. Although the article will use BusinessObjects as the BI application with a SQL Server data mart the techniques described here can apply to other BI Applications and database types.
Continue reading

This article was published on January 27, 2009 by Al Gulland.