June 4, 2009 at 9:04 am
I have an application which was written specifically for SSIS on SQL Server 2005.
This application is used to move data (in bulk) from one database to another. The application references the following DLL's.
Microsoft.SqlServer.DTSPipelineWrap – (v9.0.242.0)
Microsoft.SQLServer.DTSRuntimeWrap – (v9.0.242.0)
Microsoft.SQLServer.ManagedDTS – (v9.0.242.0)
Recently, when trying this out on SQL Server 2008, the application failed because it could not find these assemblies (more specifically v9.0, the assemblies were in the GAC but they were v10.0). SQL Server 2005 had not been installed on the machine therfore they were not present in the GAC.
I have tried to reference both assembly versions in my code but that doesn't work when I try to add the reference via VS2008.
My applications now requires to work with both versions of SQL Server. Obviously I would like to avoid running into this situation in the future. I think if I distribute the above DLL's with my application this should work, however I am not sure if this is allowed under the licensing agreement.
Does anyone know if you are allowed to distribute these with your software or can anyone propose another solution or point me in the right direction? Any help would be appreciated.
Thanks,
Liam
June 7, 2009 at 8:28 am
Bump.
Anyone got even the slightest clue? Can't find anything on this anywhere.
June 7, 2009 at 8:41 am
Does anyone know if you are allowed to distribute these with your software or can anyone propose another solution or point me in the right direction? Any help would be appreciated.
Actually I have more than a clue unlike DTS which comes with Redist there is no Redist for SSIS you need an instance of SSIS running before your code can run. And that means your customer must be running either standard edition if your ETL code is simple or better Enterprise or your SSIS related code will not run.
The reason is ETL code in applications runs in the context of the Agent so there is very limited extra cost even in the current setup. So you need to make sure your code can run in both 2005 and 2008 before sending it to your customers.
Kind regards,
Gift Peddie
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply