Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums  SQL Server 2005 Forums  SSIS and Import/Export (2005)  SSIS Distribution advice sought

Author  Topic  slaws Starting Member 9 Posts Posted - 2007-03-13 : 11:36:39 Hey Everyone, I've been coming here for a long time but this is my first post. I'm looking for some adivce. Im having to move my application databases from SQL 2000 to 2005 and I'm looking for some advice. I have a couple of apps that utilize DTS packages for importing and exporting to DBF's and text files. I've rewritten my DTS packages to SSIS packages and it all works great....on my development machine. After doing some research on deployment of SSIS packages I've found that users cannot run the packages unless they have SSIS running on their machine...which is now not redistributable without a license. So I tried to launch my SSIS packages from a stored procedure with DTEXEC which would probably work but the SQL Server is 64 bit. There isn't a 64 bit driver for OLE Jet 4 (the dbf files). So does anyone run SSIS packages in a way that I haven't thought of? Here are some ideas that I've been tossing around: 1> Building an app/service and installing on the SQL Server that can be invoked (somehow) by the application on the user's machine. This app will pull the path to the dts and the variable info from the DB and run the package. I just don't know how to trigger it from the user's computer or if it's even possible. 2> Running the package from a stored procedure but specifying the 32bit version of the DTEXEC in the procedure. I can't seem to get that to work. 3> Maybe I can get the procedure to launch the app mentioned in option 1? 4> Convince Microsoft to allow SSIS to be distributed. Any input anyone can give would be greatly appreciated. Thanks in advance. Scott