Post reply

SQL Server Shutdown

  • July 6, 2021 at 3:10 am

    #3903725

    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?

  • July 6, 2021 at 7:45 am

    #3903799

    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.

  • July 6, 2021 at 11:02 am

    #3903859

    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

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • July 6, 2021 at 3:15 pm

    #3903967

    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) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".

  • July 6, 2021 at 3:23 pm

    #3903969

    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.

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

  • July 6, 2021 at 4:13 pm

    #3904000

    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.

  • July 6, 2021 at 4:33 pm

    #3904004

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

    SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".

  • July 6, 2021 at 5:30 pm

    #3904028

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

  • July 6, 2021 at 5:38 pm

    #3904043

    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

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • July 6, 2021 at 5:45 pm

    #3904046

    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 3 years, 5 months ago by  Joe Zonum.

  • July 6, 2021 at 8:39 pm

    #3904134

    Thanks a lot guys.

  • July 21, 2021 at 1:17 pm

    This was removed by the editor as SPAM

  • July 21, 2021 at 1:57 pm

    This was removed by the editor as SPAM

  • July 21, 2021 at 6:29 pm

    #3912553

    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 3 years, 5 months ago by  homebrew01.

  • July 21, 2021 at 8:01 pm

    #3912584

    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 17 total)

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