set up a SQL agent job to run a SSIS package remotely

hi, all

did set sql agent job run ssis package without rdp onto target sql box?

to clarify:

basically, have 2 environments:

1.  1 environment in client's boxes, have limitted permission.

    ssis 2008 development on machine a, , sql database engine , ssis service on machine b. can log sql engine and ssis  through ssms, using domain user account ssisltduser, sqlagentuserrol.

    given network share unc (\\machinename\sharefoldername), , proxy account packages run as.  no sql login, no local path.

2. feeling dificult troubleshoot, created environment in local machine, have everything.

what want is, try or confirm whether can set sql job:

1. use domain user account, or proxy account

2. use unc store ssis packages

3. can import ssis packages sql msdb or file system. guess still have use unc checkpoint file.

maybe why words seems inconsistent sometimes.

---

thanks lot

you seem understand protection level issue - yes, you're combo.

i think understand you're having problem creating job.  that's shortcoming of ssis tools in ssms hate well.  if aren't permitted rdp server use ssms on server, there's no way use ssms @ server drives.  - still have choices make work if want store packages on server local filesystem. 

you can (or have admins) create share on server that's accessible , proxy you're using run agent jobs.  need read access set agent jobs.  you'd use ssms create jobs, , use unc - not local drive letter - config job.  (that's why you'd need read access - i'm assuming deployment location controlled.)

if don't want (or can't) shares made, can't use ssms.  can make agent jobs using t-sql: sp_add_job, sp_add_job_step, etc... that can reference server-local drives.

---

talk me on

SQL Server  >  SQL Server Integration Services