SQL server job agent?

Question

SQL server job agent?

Charmer

SSChampion

Points: 14903
More actions
January 24, 2012 at 9:53 am

#254224

Hi ,
i have created a package having some variables(for dynamic purpose)...i am going to execute the package through job agent, every day...
here since i use variables, do i need to pass variables for every time? or SQL job agent will work every day once we passed the variables for one time?
i am not sure with variables when we are going to execute through SQL Server job agent
Help me friends...
Thanks,
Charmer

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

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

herladygeekedness SSCertifiable Points: 5878 More actions · Answer 1

Your package will need to send the variables with each run, if that's the question?

mine are set as configurations and they are on the SetValues tab of the job step. I have server name and database name as two such vars. This will make it easy if a server or db changes to just make the value change to the variable at the package level.

Most of my "internal" variables are used in the package so I don't need to send in a value to the job.

Steve Jones - SSC Editor SSC Guru Points: 738612 More actions · Answer 2

Where are the variables? How are you setting them? You many or may not need to pass them in, depends on what you've done in the code.

Charmer SSChampion Points: 14903 More actions · Answer 3

Steve Jones - SSC Editor (1/24/2012)
Where are the variables? How are you setting them? You many or may not need to pass them in, depends on what you've done in the code.

select * from table name where jurisid = variable...

only one variable..and

this is how i used...

when we execute this through job agent, do we need to pass every time ?

when ever we talk about dynamic package, we cant run through job agent right? since variable needs to be changed every time

Thanks,
Charmer

Steve Jones - SSC Editor SSC Guru Points: 738612 More actions · Answer 4

what's the variable supposed to be? Or how does it change? you're leaving out lots of details.

For example, if this is a date, you can configure the script to pull a date automatically.

If this is from a user, then it won't run through agent, unless the person is editing the job, or the value is pulled from a table somewhere and the user can edit that.