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 12»»

What Counts for a DBA: Amnesia Expand / Collapse
Author
Message
Posted Saturday, January 5, 2013 12:41 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, July 7, 2014 12:54 PM
Points: 71, Visits: 74
Comments posted to this topic are about the item What Counts for a DBA: Amnesia


Post #1403200
Posted Sunday, January 6, 2013 9:41 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Saturday, June 7, 2014 7:51 PM
Points: 42, Visits: 351
Bravo Louis!

I will share this with my team. I currently practice a valuable piece of information you gave me years ago. You said don't design based on how much work its going to take to complete the solution. This post is an excellent approach to that philosophy. Focusing on the original problem and selectively ignoring things that don't work is the way to maintaining sanity.

So many of the problems that exist are the result of improvisation that didn't really solve the original problem on a long term basis. Thanks for your leadership!



Post #1403336
Posted Sunday, January 6, 2013 10:26 AM


SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, July 7, 2014 8:21 AM
Points: 33, Visits: 325
Good article. The DBA job is significantly easier in the long run , if discipline and sound priniples are applied.
Many DBAs are pragmatic - i.e they work in a resource constrained environment - with the number one priority being to keep Production systems alive.
This leads to short cuts and sometime pain the future


Jack Vamvas
sqlserver-dba.com
Post #1403339
Posted Sunday, January 6, 2013 2:16 PM


SSC-Dedicated

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

Group: General Forum Members
Last Login: Today @ 7:30 PM
Points: 36,766, Visits: 31,222
Jack Vamvas (1/6/2013)
Good article. The DBA job is significantly easier in the long run , if discipline and sound priniples are applied.
Many DBAs are pragmatic - i.e they work in a resource constrained environment - with the number one priority being to keep Production systems alive.
This leads to short cuts and sometime pain the future


How do you figure that trying to keep Production systems alive "leads to short cuts"?


--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."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1403354
Posted Sunday, January 6, 2013 2:41 PM


SSC-Dedicated

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

Group: General Forum Members
Last Login: Today @ 7:30 PM
Points: 36,766, Visits: 31,222
What I've found is that a DBA is usually the voice-of-one against many and that the DBA is usually the only one with a mind out for silly little things like performance, scalability, useablility, archivability, and ease of modification. I certainly can't speak for all DBAs but thank goodness I don't actually have amnesia so that I can remember all of the seemingly little stupid things that have caused huge pains in the future. You know... little things we've suggested like "No. Loan Number from a bank isn't good enough to be a Primary Key" or "No. No permutation of first and last name is good enough to be a Primary Key" or "No. Storing multiple addresses and phone numbers on a single row in the Customer table is a really bad idea".

I think that any DBA that has developed a sense of amnesia has yet another hard lesson to learn.


--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."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1403361
Posted Sunday, January 6, 2013 11:45 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Friday, August 16, 2013 2:26 AM
Points: 424, Visits: 119
Nice article Louis
Post #1403423
Posted Sunday, January 6, 2013 11:52 PM


SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, July 7, 2014 8:21 AM
Points: 33, Visits: 325
@Jeff - "short cuts" , in this context means : a) Increasing time pressure on the Production DBA with limited time to plan and apply principles adequately. b) Many DBAs I know , are frustrated by increased responsibilities but with insufficient increased resources to tackle these responsibilities.

Maintaining Production environments in a complex , constantly changing environment , with SAN , network, VM - upgrades, fixpacks - creates extra workload for the DBA - regarding troubleshooting , capacity planning etc. As a result , developers in lower environments don't receive the necessary attention from the DBAs.



Jack Vamvas
sqlserver-dba.com
Post #1403426
Posted Monday, January 7, 2013 7:31 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, March 6, 2014 1:05 PM
Points: 1,334, Visits: 3,068
Jeff Moden (1/6/2013)
What I've found is that a DBA is usually the voice-of-one against many and that the DBA is usually the only one with a mind out for silly little things like performance, scalability, useablility, archivability, and ease of modification.


I can definitely agree with this. Many times, we are the only voice of reason that protects the integrity of the production databases which we are the caretakers of. Managers, developers, BI folks, etc tend to want what they want when they want it. I have a big sign over my desk for all to see that states: "This is NOT Burger King. You can't always get it your way."


"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ..."
Post #1403601
Posted Monday, January 7, 2013 8:32 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, July 7, 2014 12:54 PM
Points: 71, Visits: 74
@jeff moden,

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.



Post #1403655
Posted Monday, January 7, 2013 10:17 AM


SSC-Insane

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

Group: General Forum Members
Last Login: Today @ 10:48 PM
Points: 21,229, Visits: 14,939
Jeff Moden (1/6/2013)
What I've found is that a DBA is usually the voice-of-one against many and that the DBA is usually the only one with a mind out for silly little things like performance, scalability, useablility, archivability, and ease of modification.


+1




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 #1403735
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse