We’ve gathered together the top Microsoft Support solutions to the most common issues experienced using Microsoft SQL Server.
1. Solutions related to performance:
- Deadlock Troubleshooting, Part 1
- Pssdiag and Sqldiag Manager
- Working with tempdb in SQL Server 2005
- Troubleshooting Performance Problems in SQL Server 2008
- SQL Nexus Tool
- Recommendations and guidelines for the "max degree of parallelism" configuration option in SQL Server
- Description of the Replay Markup Language (RML) Utilities for SQL Server
- SQL Server I/O Basics, Chapter 2
- Microsoft® SQL Server® 2012 Performance Dashboard Reports
2. Solutions related to cluster failover:
- DBA 101: Collecting and Interpreting Failover Cluster Logs
- Why is my SQL Clustered Instance changing authentication modes?
- SQL Server Cluster Failover Root Cause Analysis–the what, where and how
- Sql Server Resource Fails to come online on Cluster with Error Error Locating Server/Instance Specified [xFFFFFFFF]
- SQL Server 2005 cluster resources fail after a side by side installation of SQL Server 2008 on a Windows Server 2008
- You get "Failover instance 'MSSQLSERVER' cluster group not found" when you try to add a new node to a single node SQL Server Failover cluster.
- A SQL Server cluster resource goes to a "failed" state when you try to bring the resource online in SQL Server
- How to change SQL Server parameters in a clustered environment when SQL Server is not online
- How to clean up the cluster resource group and the databases on a shared disk after a failed failover Cluster Complete operation in SQL Server 2008
- "Object must be a root directory" message after a SQL Server 2008 failover cluster upgrade fails
- SQL Server failover cluster rolling patch and service pack process
- A SQL Server Agent resource cannot be brought online in a Windows Server 2008-based failover cluster
3. Solutions related to crashes and exceptions:
- SQL Server reports errors for exceptions, assertions, and hang conditions
- How to troubleshoot SQL Server database consistency errors
- How to choose antivirus software to run on computers that are running SQL Server
- The use of third- party detours or similar techniques is not supported in SQL Server
4. Solutions related to SQL Server backup or restore:
- SQL Backup Simulator
- Is SQLVDI.DLL functioning properly?
- How to fix permission issues when moving MSDB database between different instances
- INF: Space requirements for backup devices in SQL Server
- How to schedule and automate backups of SQL Server databases in SQL Server Express
- Best Practice recommendations for SQL Server Database Backups
- SQL Server records the date/time of the most recent database consistency check with no errors
- Behavior of compressed backups when appending backups to an existing media set
- Restoring Full- text Catalog in SQL Server 2005 removes SQLServer2005MSFTEUser ACL
- Troubleshooting SQL Server Backup/Restore Problems
5. Solutions related to network errors:
- Using Network trace to troubleshoot intermittent connectivity issues
- A case study on System.InvalidOperationException due to SQLConnection leak
- How to prepare for a SQL Developer / Connectivity case
- Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
- A special GNE (General Network Error) messages when running SQL Server after installing service pack 1 for Windows Server 2003 and TCP registry key SynAttackProtect
- Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
- SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified
- Steps to troubleshoot SQL connectivity issues
- Connectivity troubleshooting in SQL Server 2008 with the Connectivity Ring Buffer
- Sql Server Resource Fails to come online on Cluster with Error Error Locating Server/Instance Specified [xFFFFFFFF]
- How to enable remote connections in SQL Server 2008?
- FIX: Errors when a client application sends an attention signal to SQL Server 2008 or SQL Server 2008 R2
- Potential causes of the "SQL Server does not exist or access denied" error message
- "General Network error," "Communication link failure," or "A transport-level error" message when an application connects to SQL Server