kjmackey


SP2 for SQL Server 2005 x64 has been less than happy for me.

The initial problem, mentioned in another thread, concerned SSIS client which stopped liking Data Flow components. It was solved by a removal and reinstallation of the client tools.

However, there now seems to be a problem with making use of the Teradata oledb provider within SSIS. Prior to the installation of SP2 there was no problem.

I create a new SSIS package
Add a Data Flow component
Within the data flow add an oledb source
Create a new connection - using the Teradata oledb provider
Test the connection (it works!)
Use SQL something like "select * from some_teradata_table_on_the_TD_server"
Click on columns, wait a second, a list of columns is returned
Add a SQL Server destination (with a new SQL Server connection)
Connect the two components
Save the package

Click go
The TD oledb source component turns bright red and the error is "class not registered"

I have uninstalled the TD oledb provider (and underlying TD components) and re-installed (32-bit and 64-bit) - no change

Any ideas

- KjM




Re: SQL Server 2005 x64 SP2 conflict with Teradata oledb? (class not registered)

Bob Bojanic - MSFT


This looks like another 32 bit vs 64 bit issue. Could you try to run your package in 32-bit mode as it looks like you have enough connectivity at the design-time (32-bit)

There is a switch (I am not able to see the name at the moment) under Project/Debug to control which runtime gets invoked.

HTH,

Bob







Re: SQL Server 2005 x64 SP2 conflict with Teradata oledb? (class not registered)

kjmackey

Thanks Bob,

As I understand it, VS2005 (and so the SQL development environment) is 32-bit. I'll check into the Project/Debug settings and find the switch and try that.

Of course, prior to last week this issue didn't arise Sad

- KjM






Re: SQL Server 2005 x64 SP2 conflict with Teradata oledb? (class not registered)

Bob Bojanic - MSFT

Here is how you can quickly try that:

- Go to Properties of your project

- Navigate to Debugging page

- Set Run64BitRuntime flag to False

Bob






Re: SQL Server 2005 x64 SP2 conflict with Teradata oledb? (class not registered)

kjmackey

Thanks again,

The setting of that flag made the problem go away. I still wonder what happened in the interaction between TD's oledb provider and SQL's SP2 - but that's another day's work.

- KjM






Re: SQL Server 2005 x64 SP2 conflict with Teradata oledb? (class not registered)

kjmackey

OK - that's just annoying Smile

On a new box, SQL Server 2005 installed, patched to SP2 and then TD's oledb provider installed (version 01.05.00.00 - the latest I could find) - no problem with SSIS pulling data (without the need to turn off 64-bit runtime).

Same kind of box (64-bit) and 64-bit SQL Server 2005. I suppose the solution could be uninstall everything and reinstall in the order above - but don't have the time for that.

So, develop on the old and run on the new (which was kind of the intent anyway - the new box has twice the memory and was going to be server to the original box's client).

Thanks again for the help.

- KjM






Re: SQL Server 2005 x64 SP2 conflict with Teradata oledb? (class not registered)

Scottye

Bob,
Does this setting only work as you step through your processes in Debug, or does the setting take effect for any runtime scenario (i.e. SQL Agent Job that runs the package(s) within a given project on a scheulde)

I seem to be having a similar issue with a project that has multiple packages with a DB2 source connection. The Connection Manager doesn't seem to want to save the DB2 catalog password. I've typed it into the packages manually and immediately tested the connection with success, but after one run of the packages... the DB2OLEDB provider seems to "lose" the password for the connection.

Is this another 32 bit vx 64 bit problem