Thursday, January 12, 2012

Basic Troubleshooting

I have been a DBA for a long time and I guess that there are just some things that have become second nature for me and I forget that when people are new to SQL Server they often are overwhelmed, when there is an outage and waste time troubleshooting the wrong issue.  


Recently, I was called about a SQL Server outage.  Here were the facts:
  • 3 servers were impacted
  • The servers could not be pinged
  • The servers would not allow users to login with domain credentials directly via the console.
  • All the servers were on the same subnet in the same rack behind a firewall
  • Other servers in the same rack were up and responding to requests
  • No changes have been made for months to any of these servers
An hour of time was was spent trying to troubleshoot this as a SQL Server issue, when it was clearly not.   Do you know what the issue was?  The answer is in the comments.


2 comments:

Sarah said...

The firewall had locked up and was not letting traffic flow through it. The redundant firewall was not configured correctly thus it did not take over for the primary causing downtime.

Teddy Lawhead said...

Sarah Barela certified DBA and CCNA!