SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


The Value of Experience


The Value of Experience

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (248K reputation)SSC Guru (248K reputation)SSC Guru (248K reputation)SSC Guru (248K reputation)SSC Guru (248K reputation)SSC Guru (248K reputation)SSC Guru (248K reputation)SSC Guru (248K reputation)

Group: Administrators
Points: 248794 Visits: 19807
Comments posted to this topic are about the item The Value of Experience

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
dbo.benyos
dbo.benyos
Right there with Babe
Right there with Babe (768 reputation)Right there with Babe (768 reputation)Right there with Babe (768 reputation)Right there with Babe (768 reputation)Right there with Babe (768 reputation)Right there with Babe (768 reputation)Right there with Babe (768 reputation)Right there with Babe (768 reputation)

Group: General Forum Members
Points: 768 Visits: 1019
Yay or Nay?
I'll say definitely Yay!!!

In my experience (15 yr) of recruiting, I've interviewed somewhere between 500-600 people and went over thousands of CVs to pick those top 500. Not all of them were as good as I hoped in day 1, but the only ones that lasted long and did well on their jobs were the ones with vast experience in OTHER fields. We're talking about C# programmers that were computer technicians before, business analysts that were programmers before, etc.

The reason is that today, almost anything can be done by any tool: You can calculate tables in MS Word and design good looking text in Excel. The issue is choosing the right tool for the right job. You need to know your tool's capabilities, but more over,have a true knowledge of its LIMITATIONS.

DBA is no different than that: If you're really good you might know HOW to do that using SQL; But If you have experience, you will know IF you should do that in SQL in the first place.

Yay it is!!!

Tal Ben Yosef
www.TalBenYosef.com
(visit my LinkedIn profile)
Elliott Whitlow
Elliott Whitlow
SSC-Forever
SSC-Forever (43K reputation)SSC-Forever (43K reputation)SSC-Forever (43K reputation)SSC-Forever (43K reputation)SSC-Forever (43K reputation)SSC-Forever (43K reputation)SSC-Forever (43K reputation)SSC-Forever (43K reputation)

Group: General Forum Members
Points: 43780 Visits: 5314
I have to agree. I call it the hammer and nail principle.. When all you have knowledge of is SQL you think every problem should be solved with SQL. You need to have experience in other tools to be able to evaluate whether a problem should be solved by a particular tool..

CEWII
skelly-806234
skelly-806234
Valued Member
Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)

Group: General Forum Members
Points: 53 Visits: 91
I'd have to vote yes on this one. Other experience in some other area of IT is an absolute must. But there's 2 basic types of DBA - those that work in development environments, providing information and guidance to development teams, and those who work in production environments, keeping systems up, available and responding well.

Development DBA's do best if they come from a programming background because they have the experience of understanding the requirements of application development and using database resources from the other side. Production DBA's that come from a systems administration / networks / OS background are more suited to the job of keeping systems up, understanding the need for reliable and tested backups, capacity planning and security.

I've never met a DBA that just did a short course and then got a job... probably because they wouldn't keep that job for long...
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (379K reputation)SSC Guru (379K reputation)SSC Guru (379K reputation)SSC Guru (379K reputation)SSC Guru (379K reputation)SSC Guru (379K reputation)SSC Guru (379K reputation)SSC Guru (379K reputation)

Group: General Forum Members
Points: 379467 Visits: 42943
I'm going to take the opposite stance from a lot of other folks. Sure, I believe that you have to know other "stuff" to be a good DBA or even Developer... but too many people are using things like CLRs, NHibernate, Hibernate, and a wad of other hooie because they don't know T-SQL or what it can and should do. Everyone keeps ragging about DBA's that need to know something else... how about GUI and other types of programmers? They should learn T-SQL! ;-)

Just like folks say that not everything should be done in T-SQL, not everything has to be done in something other than T-SQL. :-P

--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.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
S Hodkinson
S Hodkinson
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3119 Visits: 1023
I am going to say Yes and No. Yes because you need experience of other areas but No because I think you need to have experience of other areas of business not just computing

If you do not understand the operational reasons/needs of the organisation, you cannot be effective. Your databases may be backed up, optimised, performance tuned etc etc but the information within them is useless to the front line forces. DBAs should be proactive not reactive

Madame Artois
Silverfox
Silverfox
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10270 Visits: 1161
S Hodkinson (10/23/2009)
I am going to say Yes and No. Yes because you need experience of other areas but No because I think you need to have experience of other areas of business not just computing

If you do not understand the operational reasons/needs of the organisation, you cannot be effective. Your databases may be backed up, optimised, performance tuned etc etc but the information within them is useless to the front line forces. DBAs should be proactive not reactive


Your comments dont make sense, A dba is responsible for integrity and security of data, the content is irrelevant. Your responsibilities to the business could be non-existent depending on the company. Knowing how the business operates does not help as much as people make out.

Having a broad IT knowledge/experience/background can help you as you have a lot of experiences to draw from. Having business experience is only helpful, if you are engaged in assisting directly with the business.

--------------------------------------------------------------------------------------
Recommended Articles on How to help us help you and
solve commonly asked questions

Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden
Managing Transaction Logs by Gail Shaw
How to post Performance problems by Gail Shaw
Help, my database is corrupt. Now what? by Gail Shaw
IceDread
IceDread
SSCommitted
SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)

Group: General Forum Members
Points: 1521 Visits: 1145
Too be a good DBA you do need understanding for other things than just the database. I'd say you should have some AD experience, OS experience. If you also have programming experience of setting up and distributing programs and building programs you'd be a even better DBA because then you are of higher value to the company because you can help the developers in a better fashion. Limiting experience to only one thing without no understanding of what the sql server is running in for a type of environment is a bit ignorant I'd say because having the bigger picture always provides a greater understanding.
dbo.benyos
dbo.benyos
Right there with Babe
Right there with Babe (768 reputation)Right there with Babe (768 reputation)Right there with Babe (768 reputation)Right there with Babe (768 reputation)Right there with Babe (768 reputation)Right there with Babe (768 reputation)Right there with Babe (768 reputation)Right there with Babe (768 reputation)

Group: General Forum Members
Points: 768 Visits: 1019
Just like folks say that not everything should be done in T-SQL, not everything has to be done in something other than T-SQL. (Jeff)


True, but in order to be able to choose among two or more options - you need to have the other option (other than TSQL)....

For instance, a guy with some UNIX knowledge will never write a script to replace strings in a text file. He'll use SED command instead. If you only know Windows, you'll never know that it ever existed...

Tal Ben Yosef
www.TalBenYosef.com
(visit my LinkedIn profile)
Richard Gardner-291039
Richard Gardner-291039
Ten Centuries
Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)

Group: General Forum Members
Points: 1419 Visits: 421
From my perspective I'd say understanding the context of the data you're manipulating allows you to see the bigger picture. However I'm a bit of a mongrel.

Choosing the right tool for the job is possibly not as important as reducing the complexity of the environment though. Tacking yet another "best in class" solution on every time you want to do something new is surely not the way forward (for a start how do you know it is best in class if it hasn't been around for 10 years, it's probably just another piece of cutting edge buggy crap). For me - there isn't much of anything you can't do with your business logic in TSQL, I'm with Jeff.

As to knowing bits about other aspects of the architecture - of course you need to understand a bit about the OS you're sitting on and the authentication systems surrounding it.

Perhaps how puritanical you are about this questions depends more on your environment than anything else - if you're looking after 50 databases for a company you're going to be spending an awful lot of time examining log files and query execution plans and doing not a lot else, if you're looking after 5 you need to spread out a little...
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum







































































































































































SQLServerCentral


Search