Louis Davidson (@drsql) (1/7/2013)
So, I should note that I don't indicate that you should forget everything you know
Just that "we have to forget the pain
of past failures".
If you are a sports fan, you can think of it just like a receiver. They have a difficult job in that they have to concentrate on the ball coming to them and protecting it once they catch it, but "forget" that they are about to be hit by a small freight train sized opponent, and that the last time they did it hurt really so bad they dropped the ball and lost the game.
They still should remember the lesson of that failure (that they have to protect the ball), but not dwell on the failure or they will do everything they can to not be in the position to even catch the ball so they won't get hurt.
Failure is a big part of the educational process (http://www.simple-talk.com/blogs/2011/04/16/what-counts-for-a-dba-failure/) but failure can lead you in two ways and fear will hopefully not be the one you choose.
I'm suggesting two things, Louis. Perhaps we're actually "in step" but just saying it differently.
1) that you never forget the pains that you've experienced lest you experience them again and 2) do not confuse such pain with simple fear. The only thing that a DBA has in common with getting whacked by an incoming ball is that knowledge in both areas will keep you and your data from being hurt again. Forgetting the pain of either "adventure" may cost you dearly. Being fearful means that you have felt pain but haven't yet figured out "why" or "where" the pain came from and certainly not what to do about it. If you don't have the knowledge and practice, the pain should be good incentive to get it. If you don't have the knowledge or the practice and it happens again, then the fear you feel should
act as a "Spider Sense" and you should proceed only with great caution.
Such knowledge, caution, and even fear will appear to be a weakness to outsiders and people who don't truly understand what being a DBA is all about. Patently, it is quite the opposite and people need to stop browbeating DBAs into submission and threatening them with their jobs for doing their jobs correctly instead of the way management wants them to do their jobs.
Also, you spell your name as a properly capitalized entity for a reason. So do I. I'd appreciate the same from you in the future. ;-)
is pronounced ree-bar and is a Modenism for R
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.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs