I don't know about you, but I'm on my lunch break! ;)Quote:
Originally posted by lgaorcl
Sometimes, I am really wondering why the company paying us so much to sit here browsing website.
Printable View
I don't know about you, but I'm on my lunch break! ;)Quote:
Originally posted by lgaorcl
Sometimes, I am really wondering why the company paying us so much to sit here browsing website.
well I have seen so many programmers who really live in misery as programmers
ndisang,
Thank you for the response you posted in this thread.
Interesting thread. I enjoyed reading the SEVEN pages.
I don't think anything needs to be added, but I agree with most everything stated (except anything Jeff said ...)
- magnus
ps: Just kidding Jeff.
This was an interesting thread unfortunately I do not have the time to read it all. I think this person makes a valid point(s) however. The point is that "Arm Chair DBA" does exist and there is a common misconception of our role.
The fact of the matter is there is always something to do with the database for disaster prevention or performance that should keep a DBA at the top of his/her game. Our system is 24 X 7 we have over 1,000,000 users and over a 1.5 million views a day with an average of 10 calls a page. The performance indications alone keeps me sprinting. Would you know the implications of managing such a system? I don't expect you to :). However if I was working on a smaller system I could still keep extremely busy maintaining the server based on the business needs and my knowledge of how to make the system run more efficient. Keeping the system tuned alone saves company money on extremly expensive equipment. The next step up for us is an E10000K that's a million bucks, certainly less expensive then my salary. Tuning is just one aspect. It is easy for me to point out cause I deal with it day to day.
Someone who is an armchair DBA will eventually hang themselves and if not the limited support that developers receive from them should be indication enough for employers to fire them.
It is up to all of us to manage the perception of ourselves as DBAs in the working environment. To educate the developers on the complexities of our systems so that they can fully appreciate our roles.
I would suggest you sit down and talk to your DBA, give him the benefit of the doubt before coming here. I would hope this is not a personal matter cause if so your wasting my time!! I do think the perception of the DBA role needs work.
Do you know how to tune a SQL call or what this even means? If not talk to your DBA it will help you appreciate us a little better. :)
All the best to you!
[Edited by wmccormick on 04-04-2002 at 03:38 PM]
But, of course,I have 20 minutes to comment on the whole thread! http://www.dbasupport.com/forums/Quote:
Originally posted by wmccormick
This was an interesting thread unfortunately I do not have the time to read it all.
[Edited by wmccormick on 04-04-2002 at 03:38 PM]
Of course!!! LOL!!! I probably touched on what others have posted!! Is a touchy subject because of the way it was presented and felt it was worth my two cents. :) I really hate this misconception especially being the only DBA where I work. It can be tough to manage this perception!!!
Cheers,
This thread is really becoming interesting. !!!
Its gone in 6 pages. Probably first of this kind in this forum i think !!
I donot remember any single thread going into 6 pages .
All great people and active members have jumped into this thread except jurij (Jmodic).
i am sure jeff would also agree with me in this . I am eager to read jurij views/ opinion on DBA role.
-- Pravin
oh cmon admit it DBAs are slackers.
--------------------------------------------------------------------------------
Originally posted by julian
I personally enjoy programming with PL/SQL, Forms and Reports. Some business programming with PL/SQL could be more challenging that the DBA tasks.
--------------------------------------------------------------------------------
Some of DBAs may have other views also. They hate writing programs or even develop forms or other user interfaces.
Few years ago, my colleague, another DBA refused to develop simple reports using Discoverer. She told the management very clearly that she was there to manage the database not developing reports.
The role of DBA differs from company to company.
But responsibilities like installing, configuring database, monitoring objects grwoth, maintaining security, user creation, primary object creation, performance tuning, backup and recovery, planning for future growth are primary. Rest of the works one does are secondary.