November 26, 2008 at 1:29 pm
I'm deploying an SSIS package that was developed by someone else. For some reason they have two destination connections pointing to the same database - one is an OLEDB connection and the other an ADO.NET connection. The OLEDB connection is used to truncate a table and then execute a dataflow task to insert data back into it. The ADO.NET connection is used in Execute SQL Tasks to update the data after it's been inserted.
On one SQL Server 2005 server, everything works fine. On another, the OLEDB connection works fine, but the ADO.NET connection doesn't. It doesn't generate any errors - it just doesn't update the data. I've verified that permissions aren't the issue and I've verified that the update script is valid.
Is there a configuration option on SQL Server 2005 that would prevent ADO.NET connections from working properly? Any other suggestions on what the problem may be would be appreciated.
Thanks,
Sheila
November 26, 2008 at 8:13 pm
I'd check the version of .NET installed on the 2 machines. I think that might be the issue.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply