Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 1234»»»

Stop, Don't Panic Expand / Collapse
Author
Message
Posted Monday, March 15, 2010 9:15 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 4:39 PM
Points: 33,155, Visits: 15,291
Comments posted to this topic are about the item Stop, Don't Panic






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #883509
Posted Monday, March 15, 2010 10:27 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, September 14, 2012 12:47 PM
Points: 7, Visits: 63
Very much been there, done that. Since I work in a manufacturing environment (7X24). I can add my own rule to "don't panic" - sleep on it. Between midnight and 6AM, when production wakes you up. Your monitor processes are e-mailing, texting, sounding the sirens, you've got a radical idea on how to fix the whole mess... stop, just patch enough to limp through until morning, get some sleep, go in and go over your ideas with somebody more sane (or at least more rested). I have more than once realized that what I would have done at 3AM, would have only added fuel to the fire.
Tired people make really stupid decisions. Be aware of this
Post #883542
Posted Tuesday, March 16, 2010 5:22 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, August 13, 2014 2:35 PM
Points: 186, Visits: 371
Have a plan, at least a generic outline of what you will do under given circumstances. It's a subset of what management should have in place for their business continuity plan. Management has one right? So should you.
Consider in advance the steps you would run through, the checks you would make and why you would make them. The plan may help yourself and others really understand the purpose of the data housed on server A and who consumes it. Having a list of data consumers is the starting point for that notification list of business people who need to be in the loop when disaster strikes.



Post #883660
Posted Tuesday, March 16, 2010 6:46 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Friday, June 27, 2014 12:43 PM
Points: 15,444, Visits: 9,596
Yep.

Or, to put more explictly: I agree with the editorial. Far too often, I've seen people react to stress by doing stupid things.

On the other hand, after you've had to reach inside someone's body to clamp a bleeding artery shut with your fingers, nothing IT-related seems all that panic-inducing. That may have something to do with my ability to remain calm in emergencies.


- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #883717
Posted Tuesday, March 16, 2010 8:44 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 4:39 PM
Points: 33,155, Visits: 15,291
You hope management has thought things through, but often I've found they haven't. It's only the people that have been through things that tend to have plans in place, or a general idea ahead of time.

Pushing back on management to make sure things are fixed properly is hard, but hopefully you feel empowered enough to do it.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #883849
Posted Tuesday, March 16, 2010 8:59 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, December 20, 2012 1:03 PM
Points: 265, Visits: 589
Reminds me of the line, make haste and repent at leisure.
Post #883863
Posted Tuesday, March 16, 2010 10:06 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, August 18, 2014 3:37 PM
Points: 360, Visits: 1,956
These are the situations where having set procedures in place help tremendously. If there is a document outlining the steps to take when something bad happens, the chances of rash action are reduced. A proper change management process, where any change to production has to be tested in acceptance and approved prior to being placed in production, also helps prevent disasters from getting worse.
Post #883950
Posted Tuesday, March 16, 2010 10:11 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Yesterday @ 10:59 AM
Points: 21,619, Visits: 15,275
I agree with the editorial. It is important to remain cool under pressure. That task is much more difficult when you have 30 managers watching over your back. However, it is at that time that remaining cool is much more necessary.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #883955
Posted Tuesday, March 16, 2010 10:25 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, May 15, 2014 5:11 PM
Points: 6,067, Visits: 5,283
I too agree with the editorial..

It is far too often WAY MORE damaging to jump into a fix without proper consideration than it is to stop and think about it.

Case in point, a recent discussion here about a database that was suspect and some questionable advice on how to fix it. That advice failed to cover WHY the database was suspect and that a little bit of research BEFORE action was REQUIRED.

And when management is squealing about how bad they need this fixed remaining calm and getting it fixed RIGHT THE FIRST TIME helps give them the confidence to let you do your job, not always but it helps.

And I've had a stack of people in my cubie before just watching me type, to the point I turned around and said, "listen, I'm going as fast as I can, you standing there isn't going to make this go any faster. I will let you know when I know something." Which was the subtlest way I could say SCRAM, I'M WORKING HERE..

CEWII
Post #883973
Posted Tuesday, March 16, 2010 10:39 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 4:39 PM
Points: 33,155, Visits: 15,291
I've actually had to tell a VP to "go away" when I was managing. It was bad enough that I would go in to check on DBAs. Having him walk in was like asking for trouble.






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #883981
« Prev Topic | Next Topic »

Add to briefcase 1234»»»

Permissions Expand / Collapse