sql-server-agent

I am using SQL Server 2008 and I need to run a SQL Job from SQL Server Agent. I am new to SQL Server Job and I want to execute a stored procedure regularly from a SQL Server Job. But I did not find where to specify the executed stored procedure other than copy & paste SQL commands. Here is my screen snapshot: Any ideas how to assign stored procedure to execute in SQL Server Job? marc_s You just need to add this line to the window there: exec (your stored proc name) (and possibly add parameters) What is your stored proc called, and what parameters does it expect? As Marc says, you run it

I am using SQL Server 2008. I am confused about which account will be used when a SQL Server agent job runs. My confusions are, SQL Server agent as a Windows Service which we could control from Windows Service Management Console, from there we could set the account to run SQL Server Agent (LocalSystem in my computer); Could I set SQL Server agent job level account to run on? Could I set in each step which account SQL Server agent job step will run on? I have above confusions because 3 different account systems may be used and my concern is what is the actual account each step will run on, and

I have just had a scheduled SQL Server job run for longer than normal, and I could really have done with having set a timeout to stop it after a certain length of time. I might be being a bit blind on this, but I can't seem to find a way of setting a timeout for a job. Does anyone know the way to do it? Thanks We do something like the code below as part of a nightly job processing subsystem - it is more complicated than this actually in reality; for example we are processing multiple interdependent sets of jobs, and read in job names and timeout values from configuration tables - but this

If you schedule a SQL Server job to run every X number of minutes, and it does not finish the previous call before the # of minutes is up, will it skip the run since it is already running, or will it run two instances of the job doing the same steps? The SQL Server agent checks whether the job is already running before starting a new iteration. If you have long running job and its schedule comes up, it would be skipped until the next interval. You can try this for yourself. If you try to start a job that's already running, you will get an error to that effect. I'm pretty sure it will skip it

I have a SSIS package running at 8 PM in the evening for the Year 2011. I would like to run the same package at 8:30 PM for the Year 2010. I made a SSIS Package configuration file and accept the "Year" as a parameter. Whenever I run, I need to open a file, change the value and run it. Is it possible to set up the schedule and set the Year value dynamically? Or using 2 different configuration file is the only way to solve it? Thanks all. The challenge with using a configuration file approach is that you would need to constantly modify the file. SSIS wouldn't reload the config file after it