Unable to scheule packages

  • Hello,

    I have some SSIS packages which connects to SQL Server databases using SQL authentication.

    This is working if I save the passwords in the package.

    But when I try to schedule it from SQL Agent it is unable to schedule as the passwords are saved in encrypted mode. I I don't save in encrypted mode the package is unable to connect the database.

    Please help.

    Thanks

  • Please let me know need if you need any other information to help me to solve the problem.

  • I guess my question would be, why can't you do this with Windows Authentication and trusted connections?

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • I agree with Jeff here. Don't use that method, and give the SQLAgent running the job the necessary permissions, and save with no encrypted data.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • Knowledge Hunter (1/26/2014)


    Hello,

    I have some SSIS packages which connects to SQL Server databases using SQL authentication.

    This is working if I save the passwords in the package.

    But when I try to schedule it from SQL Agent it is unable to schedule as the passwords are saved in encrypted mode. I I don't save in encrypted mode the package is unable to connect the database.

    Please help.

    Thanks

    If you really have to work with SQL Server authentication (due to different domains maybe?), you need to use configurations (if SSIS 2005/08).

    If you're using SSIS 2012, you can use parameters instead.

    Save the username and password in a configuration and put that on the server. Set the package to DontSaveSensitive. When the package runs, it will pick up the configuration and apply it.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Or, if it is 2012, you can deploy to the catalog and have the connections set up there. It will change the protection level when you deploy.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply