October 12, 2008 at 8:49 pm
I wrote an SSIS package that our mid-range (non sql) developer needs to run from his local workstation. He will run the job as needed and does NOT have sql 2005 instaled on his box. What is the easiest way (for me, the dba) to setup the package so he can run it when he pleases?
TIA,
barkingdog
October 13, 2008 at 8:35 am
I guess it all depends on how often he'll need to run it and if this is a production process or just something that needs to be done during a development cycle.
If this is a temporary process, can he have Management Studio so that he can trigger the job? Running a package with an Agent job on the server will definitely be the fastest way to process it as you will eliminate any data movement over the network to his workstation. If SSMS isn't an option, can he just have Visual Studio with the BI project templates installed? Visual Studio contains enough of the SSIS runtime to allow him to execute the package there without needing a full SQL install on his workstation.
If you're looking for a more permanent/production method, you'll need to give him a way to get the job triggered to run on the server. Maybe a flag that could be set on a table that some application watches or a web service that he can call that fires it off on the server. Service Broker might be another option but I confess I'm not an expert there so it might take a little reading. Obviously, any of these will require some coding.
October 13, 2008 at 7:50 pm
Good answer.
Thanks,
Bilkingdog
October 14, 2008 at 7:56 am
One remote option could be using psexec.exe on the client to call a batch file on the server.
Make sure you have some method of checking for failure in the event log. If you have an error in your package, the window on the client just closes.
Greg E
http://technet.microsoft.com/en-us/sysinternals/default.aspx
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply