Activity overview
Latest activity by TamusJRoyce
Talking to someone prominent in the SQL World a few days ago. They suggested something to do instead of using "EXEC msdb.dbo.sp_stop_job @job_id = @CurrentJobId".
To actually throw an exception. And then. When the job is set to succeed on failure. The job will succeed. / comments
Talking to someone prominent in the SQL World a few days ago. They suggested something to do instead of using "EXEC msdb.dbo.sp_stop_job @job_id = @CurrentJobId".
To actually throw an exceptio...
Or if this is an issue coming from sql server, and filtering will not be possible in Redgate Monitor, could someone elude to what RedGate Monitoring is queuing off of that generates notifications? So I can submit a issue request to Microsoft? / comments
Or if this is an issue coming from sql server, and filtering will not be possible in Redgate Monitor, could someone elude to what RedGate Monitoring is queuing off of that generates notifications? ...
This is causing as many as 40 emails a day. And 80 or more logged events. That is quite a bit of clutter. And the unnecessary communication causes actual errors to occasionally be lost or ignored. / comments
This is causing as many as 40 emails a day. And 80 or more logged events. That is quite a bit of clutter. And the unnecessary communication causes actual errors to occasionally be lost or ignored.
Why when Cancelling a job, on a step set to send success on failure, does it log notifications?
I have a job as step 1 that cancels itself if a certain condition exists where I don't want the job to run.IF NOT
(EXISTS(SELECT 1
FROM sys.dm_hadr_availability_replica_states AS ars
...