Operations

One question I often get from DBAs and developers is: “Why do I see NT AUTHORITY\SYSTEM or LOCAL SERVICE in my SQL logs making schema or metadata changes?”At first glance, this can look suspicious. Did the operating system just change my database? Is this a security risk? Let’s break it down. What’s Actually Happening When

What trace flags are (quickly) Trace flags are switches that alter SQL Server engine behavior. Some are documented/supported by Microsoft; many are undocumented (internal, historical, or fix-gated). Use them carefully, test in lower environments first, and document who turned them on, why, when, and how to roll back. How to see / enable / disable

If you manage SQL Server today, chances are you touch on-prem instances, cloud databases, and maybe a few containers. The toolbelt you pick matters for performance, reliability, and day-to-day sanity. Here’s a clean, opinionated rundown of what to use (and when), with pros/cons, gotchas, and credible references. 1) Microsoft-native tools SQL Server Management Studio (SSMS)

This builds on Part 2. Instead of only emailing what happened in the last 24 hours, we will: Everything below is copy-paste ready. Replace placeholders like YourUtilityDB, YourDatabaseMailProfile, ops@example.com, and linked server names as needed. Schedule it Create a SQL Agent job that runs: Run it once daily. On critical systems, run it every hour

Group counts, suppress noise, and email a clean daily report This follow-up builds on Part 1. Instead of reading the entire error log by hand, we’ll scan the last N hours, classify messages as Errors or Warnings, suppress known noise, group duplicates with counts, and email a compact HTML report. There’s also a section for

The SQL Server Error Log is your first stop when something looks off. It records startup messages, configuration changes, critical errors, I/O problems, login failures, backup issues, and more. A fast daily review catches trouble before it becomes an outage. Where to find the Error Log In SSMS On disk (default paths) Tip: Keep several

Building an SSIS Multi-Server Health Sweep with Automated Email Reports – SQLYARD Leave a Comment / Articles, SQL Server Features / By SQLYARD Building an SSIS Multi-Server Health Sweep with Automated Email Reports By SQLYARD · SQLYARD.com · May 2026 · Estimated read: 25–30 min If you are responsible for multiple SQL Server instances, one

SQL Server Severity Alerts: How to Set Up Proactive Error Notifications – SQLYARD Leave a Comment / Articles, Scripts / By SQLYARD SQL Server Severity Alerts: How to Set Up Proactive Error Notifications By SQLYARD · SQLYARD.com · Updated June 2026 · Estimated read: 18–22 min SQL Server 2005 and later · All editions Most