It's from the snapshot created by the DBCC CHECKDB process. Try restarting the SQL Server service - it should clean up itself on a restart.

Sue

Sorry...posted at the same time. But all of it goes to show how stupid it was to use the term truncate.

That's exactly what Jeff is saying, it's really an issue about poor word usage. Microsoft's use of "truncate" for the transaction logs means marking the inactive portions of the log...

Some of it is undocumented. The job activity monitory executes several things, collects data into temp tables to eventually get the view you see in SSMS.

Ways to get currently executing...

Nope all worked, meant exactly what I wrote.

There have been problems with other QoDs with broken links, incorrect explanations and just poor questions. In comparison to some of those, yours...

This is an interesting blog post on the subject:

How is @@DBTS expected to behave on an Always On Availability Group secondary replica, a Database Mirroring mirror, or a database...

You would just filter on run_date to work in your scenario or possibly include run_time if you are doing last 24 hours.

Sue

I thought it was a fun question. I think the thorough explanation, links (that worked) are great!

Thanks for doing such a good job with QoD where it ends up being...

You can try playing with something like the following to grab jobs that were successful and just look at the duration of the job (instead of each job step):

            
May 15, 2019 at 7:23 pm
            
#3644005

            
            
                                                
        

You can connect with Windows Authentication or SQL login. You can use different processes or whatever but for the login itself, there really aren't other alternatives. Windows or SQL.

Sue

No, it's not a DDL operation so a DDL trigger won't fire. You have to pick from several not too clear cut options if you want to get notified about...

Usually there is more to the error message...additional error numbers,  messages. You may also want to check for any additional error log files in the the directory: Program Files\Microsoft SQL...

You can get that error when renaming a computer but not updating the server name using sp_dropserver, sp_addserver. Check the server names with: select @@servername.

Sue

No you can't put a trigger on it but I don't think would need an insert trigger. That's why you would poll the view. If nothing else and you aren't...

There isn't a specific error number for stack dumps. Have you considered doing something like monitoring sys.dm_server_memory_dumps? There is a row in the view every stack dump that is generated...