Skip to main content

Troubleshooting requires...

In my humble opinion, troubleshooting requires fundamental knowledge, persistence, patience, attention to detail, and a willingness to learn continuously.

My Father-in-Law passed away this past week.  After the funeral, we came back to the house to spend time together. That evening, everything in the Family Room connected to electricity started acting very weird. Lights flickering, TV going on and off, etc.  Honestly, my first thought was his ghost had come back to haunt us. 

Then, we began to smell the odor of something electrical going bad.

Let the troubleshooting begin!  

After unplugging everything, I inspected each outlet.

The last outlet I checked behind a bookcase and one that we never use looked liked this...

The discoloration on the face of the outlet is what caught my eye. 
The picture above is after I removed the cover plate and pulled it from the wall. Don't forget to switch off the correct circuit breaker before doing any of this type of work! 

After fully removing it, I found the full extent of the damage.

Somehow, one black wire came loose on this outlet and it started arcing.

It only cost a $1.15 to repair but it took a couple of iterations of rewiring and re-installing before it started working again.  I broke one of the black wires after the first attempt while pushing it back into the box in the wall. So, that is when the patience and persistence came into play.

Attention to detail and my fundamental knowledge of electricity is the main reason I found the problem. (Thank you, United States Air Force.)

While doing the repair, I learned how multiple outlets are wired together.

The point of this post is that troubleshooting skills are transferable across many situations. I've used my skills to do database administration, aircraft maintenance and fix things at home.

My troubleshooting skills saved a call to an electrician and the TV in the Family Room is ready for the Super Bowl. They've also helped avoid much grief at the day job. ;-)


Popular posts from this blog

Modifying Endpoint URLs on Availability Group Replicas

I recently had to modify the Endpoint URLs on our SQL Server Availability Group replicas.  The reason for this blog post is that I could not answer the following questions: Do I need to suspend data movement prior to making this change?  Would this change require a restart of the database instance? I spent enough time searching on my own to no avail that I tossed the question to the #sqlhelp hashtag on Twitter and Slack but didn't get an answer prior to executing the change request. After reading the relevant documentation, I think it's probably a good idea to suspend data movement for this change. The T-SQL is straightforward.  USE MASTER GO ALTER AVAILABILITY GROUP [AG1]  MODIFY REPLICA ON 'SQL2012-1' WITH (ENDPOINT_URL = 'TCP://'); ALTER AVAILABILITY GROUP [AG1]  MODIFY REPLICA ON 'SQL2012-2' WITH (ENDPOINT_URL = 'TCP://'); ALTER AVAILABILITY GROUP [AG2]  MODIFY REPLICA ON 'SQL2012-1

PowerShell: Quick SQL Server Version Check

I have to keep track of our SQL Server version inventory.  The goal is to reduce the SQL Server 2000 population as fast as possible. The following PowerShell script will produce a csv file containing the database server name and the version of SQL Server it's running. 1: ## Get SQL Version installed on multiple servers ## 2: ## ./sqlver.ps1 3: $start = get-date 4: write-host "Start: " $start 5:   6: [reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo") | out-null 7:   8: $FilePath = "C:\Output" 9: $OutFile = Join-Path -path $FilePath -childPath ("SQLVersions_" + (get-date).toString('yyyyMMdd_hhmmtt') + ".log") 10:   11: # Version inventory 12: @(foreach ($svr in get-content "C:\Input\AllLOBServers.txt") 13: { 14: $s = New-Object "Microsoft.SqlServer.Management.Smo.Server" $svr 15: $s | select Name, Version 16:   17: }) | export-csv -noType $OutFile 18:   1

PASS Summit 2012 - Gone to the mountain and returned wiser I began my conference schedule by attending Allen White's pre-con "Automating SQL Server with PowerShell". Allen starts by telling everyone in attendance “We all can learn something from each other.  We all know something that someone else doesn't.” I thought this was a great intro and inspiration to the attendees to participate in the PASS Community. Later in the day while answering a question, Allen tells us he is not a PowerShell expert.  Which kind of surprises me.  He says he’s just figured out how to use PowerShell with SQL Server. I think he is being a bit too humble.   Afterwards, I talk to Allen about a script I’m working on and he points me in a direction that hopefully will help me finish it. All in all, it was e xcellent day of training on using PowerShell with SQL Server. As the main conference began, I tweeted about how tight the seating was in some of the rooms on the first day of the main conference.   After the Sum