views:

22

answers:

3

I have a SSIS package I am trying to schedule. I create a new job under SQL Server Agent. On the Command line tab of the jobstep, I choose "Edit the command-line manually".

The changes are retained as I switch from tab to tab within the job step but whenever I exit and save the job, the changes are lost.

Any ideas what's going on?

I'm on SQL Server 2008.

+1  A: 

There is a bug with the Set Values properties in SQL Server Agent for SSIS packages. You need to save the job step while still on the tab I think(?). I'll see if I can remember and reproduce the steps, but you're not going crazy. ;)

You may need to click "OK" for the job step, and "OK" for the job before moving on to any other changes in the job.

Tom H.
I just tried clicking OK while I'm on the tab but it didn't help. Is there another workaround?
Greg
I'm going from memory, but I think that it had something to do with the client SSMS not being the same version as the server. I have some notes on it at home, so I'll try to remember to post back here tonight when I have them in hand.
Tom H.
Thanks. That would be great if you could post your notes. We do have SQL2000 and SQL2008 installed on this machine. I wonder if that's related somehow?
Greg
It looks like invalid command line entries get reverted, although I was able to save successfully with a valid entry. Can you post your before and after command lines?
Tom H.
+1  A: 

try a copy save as on the package and save change the protection level to encrypt sensitive data with password

DForck42
+1  A: 

This is a confirmed bug, but here's a workaround that my team uses:

1) Script the create job statement (without your edits)

2) Delete the job from SQL Agent

3) Perform your edits in the create script

4) Execute the create job

This will allow you to keep your manually modified command line options.

Reagan Williams