Tag: Monitoring

  • DBA Scripts: Get Job Schedules and Duration Trends

    Part of the DBA-Tools Project. When Jobs Run, and Whether They’re Taking Longer to Do It SQL Agent Job Failure Summary tells you what broke. These two scripts answer two quieter but just as important questions: Get-JobScheduleSummary shows exactly when every enabled job is scheduled to run next, useful for spotting overlapping windows or confirming…

  • DBA Scripts: Get Trace Flags and Resource Governor Configuration

    Part of the DBA-Tools Project. Two Things a Previous DBA Might Have Set and Never Told You Trace flags and Resource Governor are both instance-wide behavior changes that don’t show up in sp_configure at a glance, don’t appear in the database, and can sit silently in place for years, inherited from whoever configured the server…

  • DBA Scripts: Get CPU Topology and OS Configuration Checks

    Part of the DBA-Tools Project. What CPU and OS Settings Are Actually Doing to SQL Server OS and Hardware Info tells you what hardware exists. These two scripts go one level deeper: how SQL Server is actually scheduling work across that hardware, and whether a handful of OS-level settings invisible from Task Manager, Lock Pages…

  • DBA Scripts: Get Log Reuse Waits

    Part of the DBA-Tools Project. The One Question That Actually Matters A transaction log that won’t stop growing, or a log backup job that suddenly can’t keep up, always comes back to the same underlying question: what is this database’s log actually waiting on before it can reuse space? SQL Server tracks the answer directly,…

  • DBA Scripts: Get TempDB Configuration

    Part of the DBA-Tools Project. TempDB is shared by every database on the instance, and it’s usually the first thing to show contention under load, long before any user database does. Unlike a user database’s files, TempDB’s default configuration out of the box (a single data file) is wrong for almost any real workload, and…

  • DBA Scripts: Get Temp DB Hotspots

    Part of the DBA-Tools Project. Temp DB is shared by every database and every session on the instance: temp tables, table variables, sort and hash spills, version store for snapshot isolation, all of it lands in the same handful of files. When Temp DB is under pressure, contention or growth events, the first question is…

  • DBA Scripts: Get SQL Agent Job Failure Summary

    Part of the DBA-Tools Project. Get SQL Agent Job Overview answers “what’s the current state of every job.” This script answers a narrower, more urgent question: “what actually failed recently, and why.” Job history in msdb holds the error message for every failed step, but it’s not somewhere anyone looks unless they already suspect a…

  • DBA Scripts: Get Instance Configuration Score

    Part of the DBA-Tools Project. Get Instance Configuration Snapshot gives you every raw sp_configure setting; useful, but it doesn’t tell you which of those hundred-plus rows actually matter. This script is the graded version: roughly 20 checks spanning memory, security, backups, integrity, and database settings, each scored PASS, WARN, or FAIL against practical best-practice thresholds,…

  • DBA Scripts: Get Agent Alerts and Operators

    Part of the DBA-Tools Project. A SQL Server can raise a severity 19-25 error, the fatal, “something is genuinely broken” tier, corruption, out-of-resource conditions, hardware faults, and if there’s no alert configured for that severity, nothing happens. No email, no page, no ticket. The error sits in the error log where it will be found…

  • DBA Scripts: Get Query Store Status

    Part of the DBA-Tools Project. Query Store is the single most useful diagnostic feature SQL Server has shipped in the last decade, a built-in, per-database history of every query’s plans and runtime stats, no third-party tooling required. And it fails in one of the quietest ways possible: it either isn’t turned on at all, or…