The SSIS and Oracle Story Continued…

In one of my previous blogs I tried to summarize the roadblocks and the ways to address them when a SSIS Package talks with Oracle Database. Apart from the Oracle Network Bug (Fixed in Oracle Client Tools version 10.0.0.3 and above), I faced another roadblock while trying to use a configuration file for the Oracle…

5

SSIS 2008 now talks to SAP BI Database..

Microsoft now offers a connector for SAP BI in Sql 2008 Integration Services (Enterprise and Developer Editions only). The Microsoft Connector for SAP BI is a set of managed components for transferring data to or from SAP NetWeaver BI version 7.0 systems. This connector comes as a part of the Microsoft Sql Server 2008 Feature…

2

SSIS 2008 now talks to Teradata Server as well!!

I was trying out the high speed connectors offered by Attunity which enables SSIS Packages to talk to the Teradata Server (version 12.0 and above, this blog post applies to version 12.0). After developing a sample SSIS Package I was quite happy to observe the following: Connectivity to Teradata is fine, in SSIS designer we…

3

How to log ODBC DSN changes

There is often a challenge to determine the last user who changed the ODBC DSN and when these changes were made. It is even more challenging in the environment where multiple users have remote access to the machine. In many cases unauthorized changes could cause a system malfunction or even a crash. In most cases…

0

You get error code “DTS_E_PRODUCTLEVELTOLOW” while running package outside Business Intelligence Development Studio

Error:  “Product level is insufficient” Or “The task ……cannot run on this edition of Integration Services. It requires a higher level edition.” Symbolic Name: DTS_E_PRODUCTLEVELTOLOW The hexadecimal value for this error number = 0xC00470FE. Cause: The error tells you that you have not installed SSIS on the machine where the package is running, probably you’ve…

1