Sql Server Agent last run duration in minutes

Hello Forum Members,
Can you please advise me on this:
There are 5 sqlagent jobs and they run many times in a day ranging from 10 seconds to 1 hour. I would like to know the duration of run in minutes during their last run.
Kind Regards,
Sqlquery9

Hi
This isn't as easy as it should be due to the job duration in sysjobhistory being stored as an INT, so you need to extract the hours,mins,seconds and add them together. 
Here's an example:
SELECT rec_job.job_name,
run_duration/10000 hrs, --hrs
run_duration/100%100 mins, --mins
run_duration%100 secs, --secs,
((run_duration/10000) * 60 ) +
(run_duration/100%100) +
(CASE when run_duration%100 > 29
THEN 1
ELSE 0
end) Total_mins ---total mins
FROM msdb.dbo.sysjobhistory jh
INNER JOIN ( select j.job_id, MAX(h.instance_id) instance_id, MAX(j.name) job_name
FROM msdb.dbo.sysjobhistory h
INNER JOIN msdb.dbo.sysjobs j on h.job_id = j.job_id
WHERE step_id = 0 --overall outcome
AND j.name IN
( 'Job Name 1',
'Job Name 2',
'Job Name 3',
'Job Name 4',
'Job Name 5')
GROUP BY j.job_id
) rec_job ON rec_job.instance_id = jh.instance_id
The code above assume that any duration of 30secs or over will be counted as one minute, you can fill in the job names that you're interested in.

Similar Messages

  • Unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1

    I am unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1. Log message is as follows:
    Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
    Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\xplog70.dll'.
    Error: 17750, Severity: 16, State: 0.
    Could not load the DLL xplog70.dll, or one of the DLLs it references. Reason: (null).

    Hi JFriedley,
    According to your error message, there might three reasons for this issue.
    xplog70.dll is corrupt, you need to check if you have any SQL Server running on same file version and same production
     edition. If xplog70.dll is corrupt, you can copy it from the new server where agent is running fine to your problematic server.
    Native client not installed properly. If you try applying any latest Service Pack or Cumulative Update then check if the SQL Server Agent can start, if that also doesn’t solve issue then try to reinstalling SQL Server Native client from SQL Server setup
    files.
    There is a similar issue about error 17750, you can review the following article.
    http://blogs.lostincreativity.com/sqldba/sqlserver-error-17750-could-not-load-the-dll-xpstar90-dll/
    Regards,
    Sofiya Li
    If you have any feedback on our support, please click here.
    Sofiya Li
    TechNet Community Support

  • JOB in Sql Server Agent should run multiple times.

    Hi Guys,
    I have a ETL SSIS job in Sql Server Agent, Which should run multiple times.
     1. For Example : I scheduled a job at 10:00 PM, If the job fails at 10:00 PM it should run automatically again at 10:10 PM, if the job fails again at 10:10 PM then the job should run at 10:40 PM.
    If the job gets success at first attempt i.e 10:00 PM, then it should not run at 10:10 PM.
    Note : The time difference between jobs is 10 minutes and 30 minutes. And i know that we can run the job at regular intervals.
    Thanks in advance

    Just add retry attempts to whatever number you want (2 as per your original explanation) in Job step properties as below
    Have a logic to include a delay of 10 mins . You can make use of WAITFOR function for that
    see
    http://www.mssqltips.com/sqlservertip/1423/create-delays-in-sql-server-processes-to-mimic-user-input/
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • SQL server agent job running as Agent Service Account whose service account does not have r/w access but is still able to write?

    Hi. I am newer to SQL server security and am reviewing some of our SQL server's configuration to make sure the services are running under accounts with least privilege.  I have a SQL server 2012 instance whose Agent service is configured to run
    under an AD user account named 'SQLServices'.  The jobs on this server are configured to run as 'SQL server agent service account', which means they should execute as user 'SQLServices'.  The jobs are set up to execute SSIS packages which read and
    write to a database on the same server where the agent job is scheduled and SSIS package installed (all on same server).  The jobs are currently executing without error and are reading writing data correctly.  Upon close examination, it turns out the
    SQLServices account is not assigned to the 'sysadmin' role and had no users mapped to any databases on this server.  How are these jobs working?  I verified in profiler that the login name indeed is 'SqlServices'.  I also verified
    that SQLServices login has no database access by remote-ing onto the server and trying to log into the DB, and access was denied as expected.  According to the literature, the Agent service needs to be a member of 'sysadmin role' but I am reading
    some cases where that is not necessarily the case.  So this is not so concerning.  What is concerning is that the login 'SQLServices' had no access to the databases on that server yet it is reading and writing to the databases as if it does. 
    The only thing I can think of is maybe jobs run as 'SQL server agent service account' on the same server as the databases it r/w to somehow has some kind of default access.  What am I missing here?  Any input would be helpful.

    After 2 days on this forum I found the answer to my own question.  In retrospect, I should have posted this under 'SQL Server Security', but I didn't know it existed.
    The 2 threads below explain that Sql agent actually runs using SID (service) NT SERVICE\SQLSERVERAGENT if you chose that when you installed.  This will automatically create an associated login NT SERVICE\SQLSERVERAGENT in SQL server with sqladmin
    role.  This is the login that Agent uses to connect to the local instance of SQL server.  If you changed to domain account to run the service during install or after using config manager, basically NT SERVICE\SQLSERVERAGENT is still
    used to connect to your local instance behind the scenes (even though you will still see your domain user as account), and the domain account is used to reach outside the server. 
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9e6bb2de-8fd0-45de-ab02-d59bbe05f72e/servicedatabase-accounts-nt-servicemssqlserver-nt-servicesqlserveragent-what-are-they-for
    https://social.technet.microsoft.com/Forums/sqlserver/en-US/b83a52fd-fe11-4c28-a27b-88be8ae79f2a/how-do-i-change-sql-server-agent-service-account-to-nt-servicesqlserveragent?forum=sqlsecurity

  • Sql Server agent Jobs running

    Hi All,
    We have a scenario where we have to run 30 pkgs at same second. Each pkg is designed to fetch 60 lakh per day records and load it into Oracle/OLEDB destination.
    For which we have created 30 SQL agent jobs for each pkg running every 5 mins 24/7. We want to test running with option(1) these 30 jobs on single sql server instance and option(2) 10 jobs each on 3 sql server instances. Can someone please help me out to understand
    which would give me the better results.
    a) The main advantage of multiple sql server instance scenario when compared with single sql server instance?
    b) How much does the hardware configurations impact on the performance?
    Thanks in Advance....

    1. Exposed to race conditions means ?
    2. What you mean distributing computing? Can't the SQL Server handle this much load ?
    3. Yes, 60 lakh records per day.
    4. Multiple Instances on the same machine. The jobs might scale up to 300 jobs.
    So, please suggest whether multiple instances would help the approach in scaling up ? Or the Single instance can handle all the 300 jobs at same second?
    Please advice which approach would be best and why?
    Re #1: means it will step on each other
    #2: is when you take a chunk of data and process each separately at the same time. SQL Server or not will use the resources available on the machine. And they are not elastic.
    #3: So thanks @Vaibhav it is 600K records to process so per 5 min it is 300 records which not too many for even one SSIS package on a commodity server. Question though is how long is the record. And what needs to be done to "process", if it takes
    longer than 5 min - boom you are trouble with your approach (#1 happens)
    Lastly, how do you know it will scale?
    To answer you need
    1) Provide with technical specs of your prod machine
    2) Do a proof of concept
    3) Profile a load to see where improvements can be done because in ETL it is common to get more and more data as the time goes by. I also fail to understand how the concurrently running packages will understand what data not to process because another package
    grabbed it.
    Arthur
    MyBlog
    Twitter

  • How to Troubleshoot why data is not moving over into the Data Warehouse after Sql Server Agent Job Run

    Hello,
    Here is my problem:
    Data was imported into the staging area. After resolving some errors and running the job, I got the data to move over to the next area. From there, data should be moving over into the DW.  I have been troubleshooting for hours and cannot reslove this
    issue. I have restarted the sql service services, I have ran a couple packages manually, and the job is running successfully. 
    What are some reasons why data is not getting into the data warehouse? Where should I be looking? 
    Your help is greatly appreciated!!

    Anything is possible.
    So, just to reiterate, running the job manually works, running the scheduled job does not result in errors neither data arriving to the DW, right? And it used to, correct?
    If so, the 1st step would be to examine the configuration(s). But not before you inspect the package. Do you have an ability to export it to a file system and open in BIDS?
    Arthur My Blog

  • SQL Server Agent Job intermittently running for packages on SSISDB

    I created an SSIS package to pull data from OLAP Cube and push it into SQL Server using SSIS 2o12. I deployed the same on the SQL Server SSIS DB and created a SQL Server Agent Job to run the package. I have an account configured to run the job (not by
    creating proxy in the job, but SQL Server Agent is running under that account), that has access to the OLAP Cube. The job is running sometimes and failing sometimes. Why the job behaving weirdly. Any help on the issue will help me a lot. I am using SQL Server
    2012 SP1 enterprise edition (11.0.3000.0) (if it helps). The error message which pops up when it fails is :
    OLE DB Source failed the pre-execute phase and returned error code 0xC0202009
    SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E05.
    An OLE DB record is available.  Source: ""Microsoft OLE DB Provider for SQL Server 2012 Analysis Services.""  Hresult: 0x00000001  Description: ""Error Code = 0x80040E05, External Code = 0x00000000:."".
    "

    Hi,
    You are using Execute SQL Task to run a MDX query, right?  If so, here is an approach/workaround for your reference. If the MDX query doesn’t have parameters, you can create a view in SQL running the MDX query and make the Execute SQL Task to get data
    from that view. If the MDX query has parameters, you can try a Function and create a stored procedure, and then set the Execute SQL Task to execute that stored procedure.
    Regards,
    Mike Yin
    TechNet Community Support

  • SQL Server Agent Failed to decrypt protected XML node

    I'm getting the below error when trying to run sql server agent to run an SSIS package. I've updated folder security to allow sql server agent access, but cannot get the package to execute within SQL Management Studio. The package runs find in SSIS. 
    11.0.2100.60 for 64-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  12:12:00 PM  Error: 2014-11-30 12:12:02.65     Code: 0xC0016016     Source: LoadStgProspects      Description:
    Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that
    the correct key is available.  End Error  Error: 2014-11-30 12:12:03.88     Code: 0xC0016016     Source: LoadStgProspects      Description: Failed to decrypt protected XML node "DTS:Password" with error
    0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.  End Error  Error: 2014-11-30
    12:12:04.74     Code: 0xC0209303     Source: LoadStgProspects Connection manager "Excel Connection Manager"     Description: The requested OLE DB provider Microsoft.Jet.OLEDB.4.0 is not registered. If the 64-bit driver
    is not installed<c/> run the package in 32-bit mode. Error code: 0x00000000.  An OLE DB record is available.  Source: "Microsoft OLE DB Service Components"  Hresult: 0x80040154  Description: "Class not registered".
     End Error  Error: 2014-11-30 12:12:04.74     Code: 0xC020801C     Source: Load prospect files Prospect xls [231]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection
    method call to the connection manager "Excel Connection Manager" failed with error code 0xC0209303.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.  End Error  Error:
    2014-11-30 12:12:04.74     Code: 0xC0047017     Source: Load prospect files SSIS.Pipeline     Description: Prospect xls failed validation and returned error code 0xC020801C.  End Error  Error: 2014-11-30 12:12:04.74
        Code: 0xC004700C     Source: Load prospect files SSIS.Pipeline     Description: One or more component failed validation.  End Error  Error: 2014-11-30 12:12:04.74     Code: 0xC0024107     Source:
    Load prospect files      Description: There were errors during task validation.  End Error  Error: 2014-11-30 12:12:04.74     Code: 0xC00220DE     Source: LoadStgProspects      Description: Error
    0xC0012050 while loading package file "C:\Users\Jim\Documents\Visual Studio 2010\Projects\SSISTraining\SSISTraining\LoadStgProspects.dtsx". Package failed validation from the ExecutePackage task. The package cannot run.  .  End Error  DTExec:
    The package execution returned DTSER_FAILURE (1).  Started:  12:12:00 PM  Finished: 12:12:04 PM  Elapsed:  4.337 seconds.  The package execution failed.  The step failed.,00:00:04,0,0,,,,0

    Hi selfdestruct80,
    According to your description, you created SSIS package and it works fine. But you got the error message when the SSIS package was called from a SQL Server Agent job.
    According to my knowledge, the package may not run in the following scenarios:
    The current user cannot decrypt secrets from the package.
    A SQL Server connection that uses integrated security fails because the current user does not have the required permissions.
    File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses.
    A registry-based SSIS package configuration uses the HKEY_CURRENT_USER registry keys. The HKEY_CURRENT_USER registry keys are user-specific.
    A task or a connection manager requires that the current user account has correct permissions.
    According to the error message, the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword as ArthurZ mentioned. To solve the problem, you need to go to Command Line tab, manually specify the paassword in SQL Agent Job with the command like below:
    /FILE "\"C:\Users\xxxx\Documents\SQL Server Management Studio\SSIS\Package.dtsx\"" /DECRYPT somepassword /CHECKPOINTING OFF /REPORTING E
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu
    Wendy Fu
    TechNet Community Support

  • SQL Server Agent Jobs error for Slowly changing dimension

    Hi,
    I have implemented Slowly changing dimension in 5 of my packages for lookup insert/update.
    All the packages are running good in SSDT. And when i deployed the project to SSISDB and run the packages all are running successfully. But when i created a job out of that and run the packages, then 3 packages ran successfully and 2 packages failed. 
    When i opened All Execution Report. I found the following error:
    Message
    Message Source Name
    Subcomponent Name
    Process Provider:Error: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005  Description:
    "Login timeout expired". An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005  Description: "A network-related or instance-specific error has occurred while establishing
    a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". An OLE DB record is available. 
    Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005  Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ".
    Process Provider
    Slowly Changing Dimension [212]
    Then i opened Provider package in SSDT and changed the source reading record limit from 4,00,000 to 15,000 in source query and deployed again and run, then the job succeeded. more than 15,000 failed.
    And in the 2nd experiment, I removed slowly changing dimension task and implemented normal lookup for insert/update, and set the source reading limit again to 4,00,000 and deployed again and run, then the job succeeded.
    Now i am not able to figure out, what exactly is the problem with Slowly changing dimension task for more than 15,00 records in SQL Server  Agent Job run?
    Can anybody pls help me out.
    Thanks
    Bikram

    Hi Vikash,
    As i have mentioned in the above post, below 2 scenarios: 
    "Then i opened Provider package in SSDT and changed the source reading record limit from 4,00,000 to 15,000 in source
    query and deployed again and run, then the job succeeded. more than 15,000 failed.
    And in the 2nd experiment, I removed slowly changing dimension task and implemented normal lookup for insert/update, and set the source reading limit again to 4,00,000 and deployed again and run, then the job succeeded."
    That means i am able to connect to sql server.
    But if i change the 1st scenario and read 4,00,000 records, the job fails and shows the above mentioned error.
    Similarly in the 2nd scenario, if i implement SCD look up,  the job fails and shows the above mentioned error.
    And i am consistently reproducing this.
    Thanks
    Bikram

  • SQL Server Agent Job Failing on Job Step

    Hi,
    Firstly, apologies if this post has been made in the wrong group.  Running SQL Server 2012.  I'm attempting to add a SQL Server Agent Job which calls a stored procedure that sends a Database Mail message.  The SQL Server and SQL Server Agent
    both run under the NT AUTHORITY\NETWORK SERVICE account.  The Database Mail service has been enabled, and a public profile created.  When running the stored procedure manually, I receive no errors - everything runs as expected and I do receive an
    email containing the expected information.
    I've created the job, job step, job schedule, attached the schedule to the job, and assigned the job to server, all using T-SQL without error.  I've also enabled the mail profile on the SQL Server Agent, and I know that part is working because when
    the job fails, I get an email notification of the failure.
    I've checked the command text in the job step and parsed it within the SQL Job Step Edit window to confirm, it shows as parsing correctly.  However, when I manually run the job itself, I get the following:
    Execution of job failed.  See the history log for details.
    I check the history log and it shows:
    [474] Unable to refresh Database Mail profile Database Mail Profile. (reason: ) (Not a typo, the history log shows no reason)
    [260] Unable to start mail session.
    [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
    The command text on the failing job step is as follows:
    DECLARE @date [varchar](10)
    SET @date = CAST(GETDATE() AS [varchar](10))
    EXEC [dbo].[GetExceptions]
    @company = 'MyCompany',
    @checkDate = @date
    With regard to the date value being passed as varchar: This stored procedure is used to check for exceptions against multiple databases on this server (hence the company parameter) via dynamic SQL.  I'd much prefer to use proper data typing but this
    is the only way I could get it to work.
    Does anyone have any suggestions on anything else I could check, or insights into why this is failing?  Any help is greatly appreciated!
    Best Regards
    Brad

    I am not sure if this really helps but I would do follow the below steps:
    1. make sure sql server agent has database mail enabled(rigt click on server agent--properties--alert system--enable database mail and choose right profile.) and RESTART THE SQL SERVER AGENT.(i know you said it i working, but sometimes,  restart the
    sql server agent might fix)
    2. check agent error log and check if any error messages.
    3. run the command text you mentioned in sql server and see if it is working.(i know you said it is working but just to make sure).
    4. make sure sql server agent service user has permissions to run database mail in msdb. check this https://msdn.microsoft.com/en-us/library/ms186358.aspx
    5. Check the output from select * from msdb.dbo.sysmail_log and if it says anything
    6.it does not look like the job log is getting truncated but to make sure, get the job step output to a text file.to do this, edit the job step and on the job step properties click on advanced,  enter path to the output file. this will give the complete
    output for the step.
    Hope it Helps!!

  • One sql server agent job suspend

    One sql server agent job--run full backup of one database is suspended from activity monitor.
    How to find why it is suspended and troubleshoot?

    "Suspended" is a common status for a thread.  It indicates the thread is waiting on an external resource, which backups often are
    Check few things:
    1. Database size, how much backup is completed from below command and location where backup files are being placed
    select session_id,command, percent_complete
    from sys.dm_exec_requests
    If that on network than might be due to slow netword backup take some time.
    2. Check job history, expected
    completion time of backup job and also if any change in the I/O and CPU time for the SPID
    3.Check wait type of suspended spid, SQL server and event viewer logs. If any I/O issue on the server. Like disk responding slowly that might be a cause of delay.
    Please click the Mark as answer button and vote as helpful if this reply solves your problem

  • SQL Server Agent ... Relation with BizTalk.

    Hi All,
    I know that there are jobs in SQL Server Agent which are used to perform some activity on scheduled basis like Purging,backup etc...
    what happens if SQL server agent service is in Stop mode(is it mandatory to have it started) and does it have any relation with BizTalk BAM.
    Praj Dixit

    Yes, you have to make sure the SQL Server Agent is running on the SQL Server. When the SQL Server
    Agent is stopped, the built-in BizTalk SQL Server Agent jobs that are responsible for database maintenance cannot run. This behaviour causes database growth, and this growth may cause performance issues. 
    SQL Server Agent jobs except the MessageBox_Message_Cleanup_BizTalkMsgBoxDb job should be enabled and running successfully. 
    You can learn about the SQL Server Agent jobs at Description of the SQL
    Server Agent jobs in BizTalk Server
    Regarding BizTalk BAM,
    Yes Backup BizTalk Server Job takes the backup of BAM Primary Import, SQL NS as
    well as other BizTalk databases. The BAM Analysis database, BAM Star Schema Database and Tracking Analysis Server database store content in SQL Server Analysis Services cubes. The Backup BizTalk Server job does not back up these databases. Instead, to
    backup these databases, it uses SQL Server Analysis Manager.
    I found this utility (BizTalk Monitoring
    Automation Utility) very useful to automate the monitoring of
    your BizTalk environment. If you have liberty to go with a paid tool,
    BizTalk360 a monitoring and support tool is the one for you.
    Rachit

  • Sql Server Agent: job hasn't run once today. Scheduling problem?

    I created this job yesterday at about 4PM; the view history shows that it last ran successfully at 11:53PM. These are the settings I put:
    Schedule Type: Recurring
    Occurs: Daily
    Recurs every: 1 days(s)
    Occurs every: 5 minute(s)
    Starting at: 05:00:00 PM
    Ending at: 11:59:59 PM
    Start Date: 10/30/2014
    No End Day (selected)
    The job is enabled, but it hasn't run once yet today. I don't want to start it manually because it should've started already. It is currently not running.
    What can the problem be?
    Thanks.
    VM

    The output is:
    Microsoft SQL Server 2008 R2 (RTM) - 10.50.1617.0 (X64)
    The length varies, but it's usually a bit over an hour to finish. It's set at 5 minutes so that, as soon as it completes, it runs the job again. The job history yesterday was: 5:48P, 7:03P, 7:43P, 8:58P, 9:53P, 10:58P, 11:53P. The job downloads some files,
    and that's why the job varies in length.
    VM
    I would say there is no point in scheduling a job which runs for 1 hr to run at every 5 mins although as per SQL Server agent logic if job is currently running and it misses schedule it will only start when job is finished. I would say to change logic to
    run every 1 hr.
    Plus I cannot find the support article but I know there was bug where Agent job could miss schedule can you please apply
    SQL Server 2008 R2 SP3. There are 2 reason
    1. it might fix your schedule skipping issue
    2 You would come under purview of extended support. Which I guess is very important.
    You can easily open job activity monitor and look for column Next run date
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • How to run a SQL Server Agent job step on certain days/frequency

    I've a SQL Server Agent job. One of the requirement is that a particular step should only run on certain frequency i.e. Certain Date and time. Any suggestions how can that be done?
    GBM

    yes
    1. Make first step as a Transact SQL step. Keep command as below
    IF DAY(GETDATE()) = <Your date value>
    AND DATEPART(hh,GETDATE()) = <your time hour)
    AND DATEPART(minute,GETDATE()) = <your time minute)
    SELECT 1
    ELSE
    RAISERROR 'Job cant be run at this time'
    Then for job step properties set the following properties in advanced tab
    This would make sure it will quit the job without executing other core steps untill it reaches the required day and time
    You can add more conditions in IF based on requirement like if you want time to be on certain second or month to be particular value etc
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Will Sql Server Agent start job when previous instance is running?

    Just as an example, I have a job that is set to run every 5 minutes. The job takes 30 minutes to complete. So sql server agent executes the job at 9:30AM. Will the job run again at 9:35AM even though the previous instance hasn't completed?
    In my case, I would like to reproduce what Task Scheduler already has, which is to
    not begin a new instance until the previous instance has completed. When the previous instance completes, then 5 minutes later, the job will be run again.
    Thanks.
    VM

    Apparently, it will skip it until the job is completed: http://stackoverflow.com/questions/865042/will-a-sql-server-job-skip-a-scheduled-run-if-it-is-already-running
    VM

Maybe you are looking for