The basic things to remember when configuring OBIEE 11G on Microsoft SQL Server:
When installed with a Microsoft SQL Server 2005/2008 database, the Oracle Business Intelligence installer configures Oracle BI Scheduler with a SQL Server 2005/2008 driver. If multibyte data is used, scheduled jobs might fail. To avoid this issue, use Oracle Enterprise Manager to configure the Oracle Business Intelligence system to use a SQL Server 7.0/2000 driver instead.
To configure Oracle BI Scheduler to use the SQL Server 7.0/2000 driver with Microsoft SQL Server 2005/2008:
Prerequisite: Ensure that the Microsoft SQL Server is set up with mixed mode authentication. Also ensure that the user that you enter to configure the scheduler has the “db_owner” role.
The below table describes the fields for the DataDirect driver to connect to a Microsoft SQL Server 2000 or 2005 database.
DataDirect Driver Fields for SQL Server Databases
Field | Entry |
Database Type: | Select Microsoft SQL Server 2000 or Microsoft SQL Server 2005 from the list. |
Connection String: | Enter the following connection string parameters: jdbc:hyperion:sqlserver://<hostname>:<port>;DatabaseName=<DATABASENAME> For example: jdbc:hyperion:sqlserver:// mydatabaseserver.com:1433;DatabaseName=bipscheduler |
Database Driver Class: | hyperion.jdbc.sqlserver.SQLServerDriver |
The following guidelines pertain to performance tuning parameters for Microsoft SQL Server databases. For more information about these parameters, see your Microsoft SQL Server documentation.
perfmon
shows an increase in I/O.
Shiva Molabanti is a Manager and Senior Architect at KPI Partners. He is a business intelligence enthusiast who likes blogging about acquisitions in the BI space, technical workings of BI tools, and Oracle Business Intelligence. Visit Shiva at his personal blog: http://shivabizint.wordpress.com/ |