dba-dash VS SQL-Server-First-Responder-Kit

DBA Dash backup collection query for reference. Have you tried running the query in SSMS and timed the execution?

It's still important to have alerts and DBA Dash doesn't have anything built in to do this. It is possible to create alerts based on the data collected in the repository database. There are some sample alerts here that might be worth a look. Hope this helps!

You can almost get everything through SQL with sys.dm_os_volume_stats:https://github.com/trimble-oss/dba-dash/blob/main/DBADash/SQL/SQLDrives.sqlThis won't include volumes that don't have any SQL files on them. e.g. o/s volume, backup volume etc.

I would definitely still recommend sp_whoisactive though - it's a great tool. Also, monitoring tools act like a flight recorder providing valuable information that you can use to diagnose performance issues after the event. I created DBA Dash an open-source monitoring tool that you might want to take a look at if you are interested in using a monitoring tool. Also, enabling query store at the DB level provides useful data to troubleshoot and fix performance issues.

I created a monitoring tool called DBA Dash that's open source if you are interested in a free monitoring tool. https://github.com/trimble-oss/dba-dash When adding a connection to monitor click the checkbox for slow query capture and it will capture all queries that take longer than 1 second to run. This is similar to your profiler trace. It also captures a lot of other data that is useful to troubleshoot performance issues. As mentioned query store is great - enable this and use in combination with dba dash. (Or other monitoring tool)

sp_BlitzFirst, sp_whoisactive. Look at query store if you have this enabled. If its a bad plan query store can help you identify and fix it. Look at cpu, io performance metrics etc. If you can't create procs for some reason you could add ## to the name to make them global temp stored procs. The procs will live as long as the session is left open that created them. Consider a utility database where you can add diagnostic stored procs. Ideally consider a monitoring tool. I created a free open source one called DBA Dash. https://github.com/trimble-oss/dba-dash

I would also check that the server is configured according to best practices - DBA Dash can also help with that. I would also recommend running sp_Blitz. In terms of memory configuration, you should set the max server memory to an appropriate value.

Either sp_WhoIsActive, or you can look into First Responder Kit - https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/tree/main - specifically sp_BlitzCache stored procedure, which, by default, will list out the most CPU expensive query in SQL Server plan cache. This should help you identify the "problematic" query.

Someone mentioned Blitz scripts - these are a series of free, open source stored procedures that are simple to instal and run on your SQL instances. You can find them here (https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit) and at his website (https://www.brentozar.com/blitz). To be honest, I admire the guy and how he presents help and techniques on how to trouble shoot your SQL instance - so I would start with the sp_blitz sp, run it, follow some of the links provided in the results and start learning a few things from that.

then download this and install it on all of your servers (i recommend having your own DBA databases on each server that you stick your tools in): https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit

You could use sp_ineachdb(which just uses a cursor under the hood)

SQL Server First Responder Kit, Ozar et al. The First Responder Kit is a set of stored procedures for "first responder" consultants who want to troubleshoot SQL Server problems. Coupled with the various resources at brentozar.com, the kit gives a great set of tools for performance investigations to gain a strong foothold and then make immediate progress on key issues and low-hanging fruit. The resources at the site develop a strong understanding of SQL Server internals for iterative refinement.