Post reply

In SQL Agent Job Step, specify localhost for SSIS Catalog Server

  • February 12, 2019 at 9:35 pm

    #409510

    In a SQL Agent job step, if I specify the server name, all works well. But, if I change to "locahost", I get the error shown, it can't find the package. I have also tried "local" and ".", same result. Is there a way to specify that the SSIS Catalog is under the same server where the job is running?

    Right now I have 3 SQL Agent job creation scripts, one for dev, qa, and prod. If I could make them all use localhost, then I could simplify, and only commit 1 script instead of 3. Or, is there a better way to accomplish this?

  • February 15, 2019 at 10:49 am

    #2022176

    Haven't found anything on my first question of using something like localhost in the server field. But I did find out about SQL Agent Tokens
    https://docs.microsoft.com/en-us/sql/ssms/agent/use-tokens-in-job-steps?view=sql-server-2017

    And in my SQL Agent job creation script, I replaced the server name with $(ESCAPE_NONE(SRVR)), recreated the job, and it worked! Now I can have one script to create a SQL Agent job that will work in multiple environments.

Viewing 2 posts - 1 through 1 (of 1 total)

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