I think this script will do it:

USE [msdb];
GO

SELECT
[name]
, [step_id]
, [step_name]
, [message]
, [run_status]
, [run_date]
, [run_time]
, [run_duration]
 FROM[dbo].[sysjobhistory]
 JOIN[dbo].[sysjobs]
 ON [sysjobs].[job_id] = [sysjobhistory].[job_id]
 WHERE[step_id] > 0;

Just add an extra...

My advice - check the dump.  Chances are it was not a specific query that caused the dump but something else.  Could be a driver issue, could be hardware failure,...

The issue is that NULL is an unknown value.  @x=NULL and NOT(@x=NULL) both give a result of FALSE.  Technically, they give NULL which gets evaluated to FALSE in a CASE...

You can read it from another location, but you may be missing the symbol libraries.  If possible, it is best to do it on the server that had the problem...

As a thought, it may not hurt to reach out to the creators of "Relativity" to see what they recommend.  Often the creators of the tool will have some good...

That is a fun one with NULLs.  The problem is that @x=@tempX can be true or false when either of those is NULL.  Doing a comparison on if @x=NULL or...

Pretty sure SQL has no built in way to monitor and alert for stack dumps.

This link has a powershell script for it though:

https://www.sqltechnet.com/2014/04/monitor-and-alert-sql-stack-dumps.html

UPDATE needs to look through the table to find the row(s) that needs updating.  INSERT can just put a new row in the proper place (heap or index) without needing...

I would monitor the logs in that case.  Or long running queries.  If most queries complete in under 5 seconds, but I start seeing a large number of transactions being...

generally, when a stack dump happens, the process that caused the stack dump shuts down.  In this case, SQL Server service is likely no longer running after the stack dump...

My approach - dig into the facts before digging into possible symptoms.  Spikes in CPU don't mean there is a SQL issue.  Monitoring for spikes MAY help or may not...

I'd check in your logs to see what happened.  both windows and SQL Server logs.

A good write up on latch timeout can be found here:

https://mssqlwiki.com/2012/09/07/latch-timeout-and-sql-server-latch/

It includes some steps to troubleshoot...

There is a lot in this question.

First, a "heap" with a "clustered index" is no longer a heap.  A heap is an unordered set of data.  A clustered index orders...

Another thing to add in to what Jeff said is if you are a contractor working on this, make sure to include your support costs for if/when the application fails. ...

I started with CVS then SVN and finally to Git (via GitLab).  My opinion though, terminology needs to be standardized.  GitHub has  "Pull Request" to get the source branch pulled...