It is not a blame game.

Here is a hypothetical situation.  A dba works for ACME Corp.  Due to what ever reason a change has to be made to a user account within Active Directory that should not create any negative issues for the user account.  Sounds typical right?  The change is made (just happens to be the domain user account SQL Server uses) and now Jobs owned by that user start failing.

The hypothetical DBA reports the issue to the network guys and they report that the change wasn’t applied to that server.  What is the DBA to do?  He is told that server wasn’t touched, but yet no other change was made.  Lets just hope the DBA kept a level head and worked with the systems guys to remove the change for that user to validate that in fact, the change that wasn’t supposed to have any impact and was not applied to his production server did in fact get applied to his production server and did in fact cause a production issue.

We all know how things that are not supposed to do xyz sometimes do cause xyz.  When those things happen keep in mind that the person who had to make that change that impacted you is just as frustrated if not more frustrated than you are.  If you all work for the same company, you are ultimately on the same team and are working toward the same goals.

Just my 2cents for the day.