Wrap T-SQL of your jobs into this code: if ((select primary_replica from sys.dm_hadr_availability_group_states) = @@SERVERNAME and (select primary_recovery_health_desc from sys.dm_hadr_availability_group_states) = 'ONLINE' and (select synchronization_health_desc from sys.dm_hadr_availability_group_states) = 'HEALTHY') begin end This way T-SQL will only run if SQL Server is in primary role, online and synchronization is healthy

Interval should be trunc(sysdate)+1 to mean midnight tomorrow. Your next_date will be evaluated to midnight today (in the past) so the first refresh will happen ASAP. You probably want this to also be tomorrow midnight

It is not possible to be 100% certain that a database is used by looking at the job step level in the msdb system tables for jobs. Some examples: A job can include SQL code that does USE dbname. A job can SELECT from a view, which in turn reads data from your database. A job can execute a stored procedure that has code that references tables in your database. A job can execute an SSIS package that does stuff against your database. This is why it is so important that we educate those that creates jobs to comment each job!

The job is not waiting to "reach a stable point". The key point is: sp_stop_job sends a stop signal to the database. sp_stop_job sends the stop request SQL Server Agent but does not wait for it to complete. The T-SQL script continues while SQL Server Agent processes the stop request asynchronously. The additional rows inserted after sp_stop_job was executed reflect the time between receipt of the stop request until SQL Server Agent got around to cancelling it. This typically takes a few milliseconds or more depending on overall activity. The note about "reach a stable point" in the context of a T-SQL job step is the same as any query cancel request. It includes the time the database engine needs to release resources and rollback the transaction. That time is insignificant with the singleton insert in your example but would be more noticeable had the cancelled script done more work, like inserted millions of rows in a single transaction.

You are using a SSMS maintenance plan. Try to look up for errors in the maintenace plan not in the sql server agent job history. You will find the true error. (written as answer because i can't paste images on the comments)

It fails because you aren't using a language neutral datetime format. You are assuming that SQL Server understands that the day comes first, then the month and finally the year. When you run this interactively using SSMS, you are using a login (as in the CREATE LOGIN command) that has a dateformat the correspond to that order. I.e., your login's dateformat is dmy. Agent is using a different datetime format for its login, evidently. That is why it fails. Perhaps it is mdy (the default for us_english). What you want to do is to use a datetime format that doesn't depend on the datetime setting for the login - what I like to call a "language neutral" datetime format. The YYYYMMDD is one such format. Here's your expression converted to that format: select LEFT(datediff(day,GETDATE(),'20' + '26' + '0831')/365.25,2) AS test Another option is to add SET DATEFORMAT before your expression: set dateformat dmy select LEFT(datediff(day,GETDATE(),'31/08/20'+'26')/365.25,2) AS test Here's an article regarding datetime that I have written: https://karaszi.com/the-ultimate-guide-to-the-datetime-datatypes I wouldn't mess about with Agent's language! You never know what might break. Just use the dateformat command or (preferably) use language neutral datetime format.

you can overcome the problem stopping using native maintenace plans and instead you could use ola hallengren maintenance solution https://ola.hallengren.com/

I would use something like this (concrete example for Stephen Morris's answer although I don't use a cursor). This will generate the command to use in the CMD output for the second query. However, are you not able to use the "Notifications" tab on the job itself? That would be easier. https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-update-jobstep-transact-sql?view=sql-server-ver15 /** Find your JobID here **/ SELECT J.job_id, J.[name] FROM msdb.dbo.sysjobs AS J DECLARE @JobID UNIQUEIDENTIFIER SET @JobID = 'F6F5DBF7-18FD-49D5-B018-81A55010C59D' /** GET LIST OF ALL STEPS HERE **/ SELECT S.step_id , S.step_uid , S.step_name , S.on_fail_action , S.on_fail_step_id , CMD = 'EXEC msdb.dbo.sp_update_jobstep @job_id = ' + QUOTENAME(@JobID, '''') + ', @step_id = ' + CONVERT(NVARCHAR(20), S.step_id) + ', @on_fail_action = 4, @on_fail_step_id = ;' FROM msdb.dbo.sysjobsteps AS S WHERE S.job_id = @JobID --AND <Additional filtering?> ORDER BY S.step_id

This can be achieved using Frequency part of Scheduler. You may create three jobs schedule, For Job1 as below: Same thing will be repeated for Job2 and Job3 however you need to change start date to 16th and 23rd January in this part: You may also use Past dated by changing date from the above calendar. After the job has executed, SQL Server will calculate a Next Execution date and time. So if you simply revert the system clock then it will be waiting for the next scheduled execution, it won't work that way. Better to schedule from current date and onwards. Hope this helps.

All jobs have assigned a schedule that exists in msdb.dbo.sysschedules. You don't need to have an extra board to handle the schedules. To update this system view, it is used sp_update_schedule.So, you could update the frequency using something like this:EXEC sp_update_schedule @name = N'Nombre del Horario', @freq_subday_type = 0x4, --Para definir minutos @freq_subday_interval = 10; More information, you can get it in https://docs.microsoft.com/es-es/sql/relational-databases/system-stored-procedures/sp-update-schedule-transact-sql to know other options.

A possible solution:CREATE PROCEDURE SP_CARGA (@PARAM INT) AS BEGIN -- @param = 2019 DECLARE @fecha datetime = GETDATE(); DECLARE @HORA VARCHAR(2); -- cargamos en la variable hora, el dato en formato 12 horas SELECT @HORA = LEFT(((FORMAT(CAST(getdate() AS DATETIME),'hh:mm tt'))),2); -- anexamos al parametro recibido la hora. DECLARE @CODMES INT = CONCAT((CAST(@PARAM AS varchar(4))),@HORA); EXEC SP_CARGA_REPORT @CODMES END

I understand that what you need is "something" that checks a certain frequency (1 hour, 1 day, ...) the work (or whatever) active for a week that hasn't changed state and passed them to state Completed, making a new insert on a board.The best thing is to perform a stored procedure that executes your query, detecting the existing cases and performing the relevant actions (updates, inserts).This stored procedure should be executed as often as you indicate. You can do it simply by using a job from SQL Server. To do this you must have the SQL Server Agent running and there create a new job (job) defining as the only step the execution of the stored procedure.

The definition of the job is correct (taking into account that the login name, the database and the table were hidden). The code can be simplified with a simple UPDATE that does what you need, you don't need to line up. /*actualizo mi tabla original si es igual*/ UPDATE T SET ACTIVO = 0 FROM TABLEORIGINAL T WHERE ACTIVO = 1 AND CONVERT(DATE,FCH_FIN) = CONVERT(DATE, GETDATE()); Using the following code, I was able to get the job to do whatever it takes.USE [msdb] GO /****** Object: Job [Suplentes] Script Date: 11/08/2019 13:32:54 / BEGIN TRANSACTION DECLARE @ReturnCode INT SELECT @ReturnCode = 0 / Object: JobCategory [[Uncategorized (Local)]]] Script Date: 11/08/2019 13:32:54 ******/ IF NOT EXISTS (SELECT name FROM msdb.dbo.syscategories WHERE name=N'[Uncategorized (Local)]' AND category_class=1) BEGIN EXEC @ReturnCode = msdb.dbo.sp_add_category @class=N'JOB', @type=N'LOCAL', @name=N'[Uncategorized (Local)]' IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback END DECLARE @jobId BINARY(16) EXEC @ReturnCode = msdb.dbo.sp_add_job @job_name=N'Suplentes', @enabled=1, @notify_level_eventlog=0, @notify_level_email=0, @notify_level_netsend=0, @notify_level_page=0, @delete_level=0, @description=N'Habilitar y deshabilitar los suplentes.', @category_name=N'[Uncategorized (Local)]', @owner_login_name=N'NA\user', @job_id = @jobId OUTPUT IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback /****** Object: Step [VerificaTiempos] Script Date: 11/08/2019 13:32:54 ******/ EXEC @ReturnCode = msdb.dbo.sp_add_jobstep @job_id=@jobId, @step_name=N'VerificaTiempos', @step_id=1, @cmdexec_success_code=0, @on_success_action=1, @on_success_step_id=0, @on_fail_action=2, @on_fail_step_id=0, @retry_attempts=0, @retry_interval=0, @os_run_priority=0, @subsystem=N'TSQL', @command=N' UPDATE T SET ACTIVO = 0 FROM TABLEORIGINAL T WHERE ACTIVO = 1 AND CONVERT(DATE,FCH_FIN) = CONVERT(DATE, GETDATE())/actulizo mi tabla original si es igua/', @database_name=N'Database', @flags=0 IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback EXEC @ReturnCode = msdb.dbo.sp_update_job @job_id = @jobId, @start_step_id = 1 IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback DECLARE @schedule_uid uniqueidentifier; EXEC @ReturnCode = msdb.dbo.sp_add_jobschedule @job_id=@jobId, @name=N'JobSche1', @enabled=1, @freq_type=8, @freq_interval=62, @freq_subday_type=1, @freq_subday_interval=1, @freq_relative_interval=0, @freq_recurrence_factor=1, @active_start_date=20191105, @active_end_date=99991231, @active_start_time=154500, @active_end_time=235959, @schedule_uid=@schedule_uid IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback EXEC @ReturnCode = msdb.dbo.sp_add_jobserver @job_id = @jobId, @server_name = N'(local)' IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback COMMIT TRANSACTION GOTO EndSave QuitWithRollback: IF (@@TRANCOUNT > 0) ROLLBACK TRANSACTION EndSave: GO

According to the official documentation of jenkins, you can do as follows:curl -X POST JENKINS_URL/job/JOB_NAME/buildWithParameters \ --user USER:TOKEN \ --data-urlencode json='{"parameter": [{"name":"id", "value":"123"},`{"name":"verbosity", "value":"high"}]}' Where:JENKIS_URL: it is the IP:PORT where you run jenkins.JOB_NAME: is the name of the job you want to run.USER: user to logearse.TOKEN: user-generated token, you generate it in user configurations. See the following link: https://stackoverflow.com/questions/45466090/how-to-get-the-api-token-for-jenkins json: Here you can pass parameters for the job you want to runThe official page where you can find more details is as follows: https://wiki.jenkins.io/display/JENKINS/Remote+access+API

You can do it like this:with sqlcmdsqlcmd -S serveName -i miscript.sql -o salida_a_csv.csv -W -w 1024 -s"," -S = server name on cmd with hostnameYou get it.-i = file name sql-o = file name-W = remove final spaces-w = size; or columns-s = column separatorbcpbcp -i miscript.sql queryout salida_a_csv.csv -S servername -c -t"," -T

You can usephp artisan queue:work --queue=<nombre-cola> And already that should start processing what you need;)

Try to use the helper dispatch. In the second case (the one that fails you), it's supposed to be $event contains contact details, as an object of the engraved model class. These come from the event, if the first example is working as you say.In the listener of the second example put the method handle():public function handle(ContactWasSaved $event) { dispatch(new SendContactMails($event->contact)); } Now let's go to the job. First, remove the following line:use App\Events\ContactWasSaved; You don't need to, and you're using resources you don't need. On the job you must use the contructor. As a whole, you must stay like this:<?php namespace App\Jobs; use Illuminate\Bus\Queueable; use Illuminate\Queue\SerializesModels; use Illuminate\Queue\InteractsWithQueue; use Illuminate\Contracts\Queue\ShouldQueue; use Illuminate\Foundation\Bus\Dispatchable; use App\Mail\ContactMails; use Illuminate\Support\Facades\Mail; class SendContactMail implements ShouldQueue { use Dispatchable, InteractsWithQueue, Queueable, SerializesModels; public $contact public function __construct($contact) { $this-&gt;contact = $contact; } public function handle() { Mail::send(new ContactMails($this-&gt;contact)); } } What the helper does dispatch() He calls the job builder, and it happens to him. $contactwhich is of the kind of object you have persisted in the database. Then, transparently to you, execute the handle() from the job. This puts the task in the table jobsAnd put it right.When you execute php artisan queue:work --tries=3 mails are sent to the first. Check.

These types of questions already have an answer in: https://es.stackoverflow.com/questions/225080/ejecutar-un-comando-cada-24-horas-y-5-minutos-con-crontab/225082#225082 But back up. The program you need is called crontab which creates the "crontab" files of users.These files are read and processed by the devil cron that will execute the tasks specified in each file "crontab". These files are stored according to distribution. Sometimes /var/spool/cron/crontabs in other cases /var/spool/cron. To create your crontab file, you can use the program crontab with the parameter -e, which allows to edit, with the default editor, and then install, the current user's crontab.Once you serve crontab -eYou'll get a file the way.# For more information see the manual pages of crontab(5) and cron(8) # # m h dom mon dow command resto del archivo ... In which you will have to add the periodicity of your task to execute and, optionally, some configuration variables for those scheduled tasks.The periodicity format can be read in man crontab(5)campo valores permitidos ----- -------------- minuto 0-59 hora 0-23 dia del mes 1-31 mes 1-12 (o nombres) dia de la semana 0-7 (0 o 7 es Domingo, o usa nombres) I mean, if you want a scheduled task by 19 a day.00 19 * * * <tu tarea> # Al minuto 0, de la hora 19, cada dia del mes, cada mes, cada dia de la semana can be as simple or complex as you want.It can be from a simple script or even a conditional.For example.00 19 * * * /root/respaldo.sh 00 19 * * * cd /root && ./respaldo.sh 00 19 * * * /bin/bash /root/respaldo.sh 00 19 * * * bash /root/respaldo.sh 00 19 * * * [ $(date -d +2day +\%d) -eq 1 ] && /root/respaldo.sh 00 19 * * * /root/respaldo.sh > /root/respaldo.log 2> /root/respaldo.error If you sometimes put the full route of the program, for example /usr/bin/python or /bin/bash It's because to understand a command as such, cron has preset a basic PATH variable, which is PATH=/usr/bin:/binYou can check it out. man crontab(5), then it is sometimes good to define the entire route to not deal with that the program you run is not found within the directories listed in the variable PATH. Other options are to define a variable PATH in the same crontab or within the script or use absolute routes to your programs within your script.

I in my project am using a plugin called django-cron.Basically this plugin is based on creating a task and you can tell him to run every X minutes or an hour in particular.You can also force the execution of the crons from the manage to check if it is running properly.Examplefrom django_cron import CronJobBase, Schedule class MyCronJob(CronJobBase): RUN_EVERY_MINS = 120 # every 2 hours schedule = Schedule(run_every_mins=RUN_EVERY_MINS) code = 'my_app.my_cron_job' # a unique code def do(self): pass # do your thing here I'll leave you the documentation. https://django-cron.readthedocs.io/en/latest/installation.html

In SQL-Server Jobs can only run one version at a time. It means that if you set it up to launch every 5 minutes, if it takes 4 no problem, when the 5th minute arrives, it will be released again, but if it lasts 5' and 1''', the call that should be a second before stays on hold until the next 5th multiple. Check it out just in case, if... for example, your Job takes 3 minutes to put it every 5 temporarily and you'll see how it is. Then... don't forget to leave 5 as you wanted.