Fourth is using SQL Profiler. Often an SQL DBA has to act like a detective looking for the reasons an SQL dataset isn't performing as expected.

One of the dreaded error codes we get in the SQL log is the “1205”. It represents the infamous deadlock where two transactions are locking each other out. No way ...

Then I would select a Profiler template to use and select events that I wish to trace such as Logins, Logouts, Stored Procedures starting, finishing, T-SQL Batches starting etc.