Snippet Name: SQL_Server_Daily_Issues
Tags:
Created Date: 2025-06-16 13:12:49
Last Modified Date: 2025-05-31 10:32:18
Dependencies:
DBA Notes:
Sample Output:
Title: SQL Server Daily Issues
Author: user
For me, SQL Server Daily operational Issues seem to fall into some categories. help me identify or list the categories. For example, I might see locking/blocking/long running transactions, Jobs that failed or did nto fail, long running queries or jobs, and statistics problems that lead to poor performance for procedures or statements
Author: ChatGPT
You're spot on in noticing that daily operational issues in SQL Server can often be grouped into consistent categories. Here???s a structured list of common **SQL Server daily operational issue categories**, broken down in a practical way for a DBA like yourself:
---
### ???? **Concurrency & Workload Issues**
- **Locking and Blocking**
- **Deadlocks**
- **Long-running transactions**
- **Query timeouts**
- **TempDB contention**
---
### ???? **Query & Procedure Performance**
- **Long-running queries or stored procedures**
- **Missing or outdated statistics**
- **Suboptimal query plans / plan regression**
- **High compile or recompile rates**
- **Query plan cache bloat**
---
### ??? **SQL Agent Jobs & Automation**
- **Job failures**
- **Job duration anomalies (too fast/too slow)**
- **Missed or skipped schedules**
- **Job step logic errors (e.g., missing conditions)**
---
### ???? **Indexing & Storage**
- **Missing indexes**
- **Unused or duplicate indexes**
- **Fragmented indexes**
- **File growths / autogrowth events**
- **Full data/log files**
---
### ???? **Connectivity & Availability**
- **Login failures or connection issues**
- **AlwaysOn AG failovers or sync issues**
- **Replication latency or errors**
- **Linked server failures**
- **Service restarts or outages**
---
### ???? **Resource Bottlenecks**
- **High CPU usage**
- **Memory pressure**
- **Disk I/O bottlenecks**
- **Network latency**
- **Resource Governor throttling (if configured)**
---
### ???? **Error Monitoring & Logging**
- **SQL Server errors in the error log (severity 16+)**
- **Dump files**
- **Suspect databases or corruption**
- **Agent log errors**
- **Extended Events or Profiler traces**
---
### ???? **Data Integrity & Validation**
- **Constraint violations**
- **Failed ETL processes**
- **Data type mismatches or implicit conversions**
- **CDC/Change Tracking anomalies**
- **Corrupted pages (checkdb alerts)**
---
### ???? **Maintenance Gaps**
- **Missed index/statistics maintenance**
- **Backups not running or failing**
- **Restore tests not done**
- **CheckDB not run recently**
---
### ???? **Security & Access**
- **Orphaned users / login mismatches**
- **Unauthorized access attempts**
- **Permission drift**
- **Failed audits**
---
### ???? **Change Management & Deployment**
- **Schema drift**
- **Deployment errors**
- **Post-deployment performance issues**
- **Untracked object changes**
---
Would you like to expand this into a spreadsheet or checklist format to help formalize your daily checks? Or tailor it to cloud environments (like RDS or Managed Instance)?
Author: user
lets shorten the list to be the more common issues,a nd not all possible categories. for exampel, lets have categories of "The Right Now Emergency Bucket","The Performance is Slow Bucket", and "The Stuff is not working as expected bucket"
Author: ChatGPT
Perfect ??? here's a **refined and pragmatic version** of the list, using your three core buckets that reflect how most DBAs think and triage:
---
## ???? **"The Right Now Emergency Bucket"**
> These are issues that **require immediate attention**, typically page-you-at-midnight type problems.
- **Blocking or deadlocks** causing widespread query failures
- **SQL Server Agent job failures** (especially backups or critical ETL)
- **Database offline or suspect**
- **TempDB full or out of space**
- **Transaction log full and growing**
- **Failed logins or authentication issues**
- **Unexpected SQL Server restarts or crash dumps**
---
## ???? **"The Performance is Slow Bucket"**
> These are **degradation issues** that users notice over time ??? "It worked yesterday!"
- **Long-running queries or jobs**
- **Outdated or missing statistics**
- **Bad query plans / plan cache bloating**
- **Missing or fragmented indexes**
- **High CPU usage or memory pressure**
- **Blocking that???s not yet critical but slowing things down**
- **Implicit conversions leading to slow scans**
---
## ???? **"The Stuff is Not Working as Expected Bucket"**
> These are **weird behaviors or functional problems** ??? things didn???t outright fail, but something???s off.
- **Jobs that succeeded but didn???t do what they were supposed to**
- **SSRS reports not rendering or returning no data**
- **Stored procedures giving different results or performance**
- **Login works, but permissions seem wrong (e.g., orphaned users)**
- **Linked server queries timing out**
- **Scheduled jobs skipped a run**
- **Change data capture / replication not syncing as expected**
---
Would you like a version of this list in a markdown doc, PowerPoint for internal reporting, or perhaps a daily triage checklist in Excel?