SQL Server Shutdown

  • I was not planning to shutdown the sql server but it was accidently got shutdown by me and cause the system to go down for approx. 10 - 15 mins outage. How to handle this with the team and management. Please advise?

  • Not sure what the question is.

    Is it about a checklist what to do if there is an outage? Work it out with the team / management / stakeholders.

    Is it about preventing accidental shutdowns? Not sure if you can to that without taking away rights.

  • Tell them.

    Don't beat around the bush. Don't try to cover up. Just say it. "I messed up. I took the server down. Here's what I did by accident. I'm going to go research ways to prevent that from happening again."

    That's your best bet.

    ----------------------------------------------------
    The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
    Theodore Roosevelt

    The Scary DBA
    Author of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd Edition
    Product Evangelist for Red Gate Software

  • Grant Fritchey wrote:

    Tell them.

    Don't beat around the bush. Don't try to cover up. Just say it. "I messed up. I took the server down. Here's what I did by accident. I'm going to go research ways to prevent that from happening again."

    That's your best bet.

    100% agree.  "The cover up is worse than the crime."  That's been proven true so many times, even for very powerful people.

    SQL DBA,SQL Server MVP(07, 08, 09) Prosecutor James Blackburn, in closing argument in the Fatal Vision murders trial: "If in the future, you should cry a tear, cry one for them [the murder victims]. If in the future, you should say a prayer, say one for them. And if in the future, you should light a candle, light one for them."

  • I totally agree with the others.  One of the things I value the most in working with people is "absolute honesty".   One of the keys to is identify how you accidentally took it down to help others keep from doing the same thing and another is explaining any of the steps you've taken to make it less likely for you to do it again.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
    "Change is inevitable... change for the better is not".
    "Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Thanks! Do I need to mention the reason or did by accident would be suffice along with explanation like you said I will research and prevent that from happening again.

  • I'd just say "by accident".  If they want more details, they'll ask.

    SQL DBA,SQL Server MVP(07, 08, 09) Prosecutor James Blackburn, in closing argument in the Fatal Vision murders trial: "If in the future, you should cry a tear, cry one for them [the murder victims]. If in the future, you should say a prayer, say one for them. And if in the future, you should light a candle, light one for them."

  • Be good to know how/why you shut this down. Wrong instance? Accidental click, etc.

  • If it was an oopsie, just say it was an oopsie. You don't have to go into lots of detail on a thing like this. That is, unless they want to have meetings to "ensure this never happens again." In which case, have the details at hand. Again, don't try to hide anything. Honesty and clarity are your friends here.

    ----------------------------------------------------
    The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
    Theodore Roosevelt

    The Scary DBA
    Author of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd Edition
    Product Evangelist for Red Gate Software

  • Agreed Own up to it.. Your human and we all make mistakes.   I've done it and everyone will eventually do it too.

    If you boss doesn't value honesty. Consider a new job.

     

     

    JZ

    • This reply was modified 2 weeks, 4 days ago by  Joe Zonum.
  • Thanks a lot guys.

  • I totally agree with the others.  One of the things I value the most in working with people is "absolute honesty".

  • This was removed by the editor as SPAM

  • Jeff Moden wrote:

    sauvewilfrhy71 wrote:

    I totally agree with the others.  One of the things I value the most in working with people is "absolute honesty".

    That also includes people that copy exactly what others have said with no reference or attribution. 😉

    LOL !

    • This reply was modified 2 days, 13 hours ago by  homebrew01.
  • I have not managed to inadvertently shutdown a server but I have accidentally shutdown, instead of restarting, my work PC twice when tired over the last 16 months. I now have the following on the Desktop of any Windows machine, including servers, which I RDP into:

    1. A shortcut to logout.exe
    2. A Restart folder containing two batch files:

    a) Restart.bat - shutdown /r /c "Manual Restart" /f /d p:4:2

    b) StopRestart.bat - shutdown /a

    ie I do not go near the Windows Power menu when interactively using RDP.

     

     

Viewing 15 posts - 1 through 15 (of 16 total)

You must be logged in to reply to this topic. Login to reply