August 8, 2009 at 6:06 pm
I wrote a sql 2008 SSIS pakcage the runs fine on our server. I was told that and end user also needs to run the package as needed (i.e. not on a scheduled basis; exact time of run unkown to me).
I want to give the end user a batch file like this:
dtexec /Server "(local)" /File "\\UNCpathToDTSx Package"
but I suspect the package wil load on the end user's computer and fail (the end user box does not have sql or BIDS installed on it). Is my suspicion correct? If so, what are the standard workarounds to this issue?
TIA,
barkingdog
August 8, 2009 at 9:56 pm
To run an SSIS package - you have to have Integration Services installed. Doesn't matter about BIDS or SQL Server, but you do need to have Integration Services - and, of course - it must be licensed appropriately.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 10, 2009 at 9:05 am
One way we do this is create a SQL Agent job that calls the SSIS package. The the client application executes "sp_start_job". The client would require execute permission on that procedure in the msdb. If you're using Windows Auth in your SSIS package connections, the job would run in the context of the SQL Agent service account.
August 10, 2009 at 11:15 pm
Ed,
That seems like a good idea to me. I'll use it.
Barkingdog
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply