What these guys said ^^^^^^
and get somewhat familiar with the hardware architecture...
If you will be working with enterprise systems, learn the differences of SAS and SATA, what an SAS Expander is and does, backup strategies and schedules, practice actually restoring data (you won't believe how many people religiously backup data, only to find, after a crash when they go to restore, that NOTHING was ever backed u), hot spares and how to use them, fault tolerances of the various RAID protocols, why S/W RAID is a poor performer, other systems than RAID (ex. Just A Bunch of Disks JBOD), their tradeoffs with RAID (speed/fault tolerance/storage-to-media ratios), what are volumes/spanned volumes, how to increase a volume by adding more disks, etc. ,
Enterprise is all about spending extra $$$ for
1) Preventing downtime
2) Not/Never losing data...at all...even if a user deletes it, you need to be able to recover it (within a reasonable time frame...ymmv)
3) How to get back up as quickly as possible after a crash
__________________________________________________ ______________________________________
The fattest knight at King Arthur’s round table was Sir Cumference. He acquired his size from too much π.
Define "enterprise"... In my experience it's 2500+ seats. Which makes everything you said correct and applicable. But no 2500+ seat company is going to hire someone for a DBA that doesn't know anything about RAID configurations. For the jobs he could get (without the knowledge) none of those are applicable. Because they can't afford it.
Yeah, I won't have more than a single beer at work for that very reason. We have people who have kegerators in their cubes.
Not true at all. We only have around 200 employees and we have two DBA's, five systems engineers (these guys do our Windows, Linux, backup and VMware), two network engineers (that's what I do), two systems administrators, and two automation engineers. We're currently taking applications for a storage engineer that also has heavy Linux experience as our last one was promoted to be our manager. We have far more terabytes of data than we do people (over 500 if I recall correctly, 3 NetApp systems, two BlueArc NAS/iSCSI systems, and a smaller Hitachi system for disk backup). Our DBA's don't touch our system builds nor our storage appliances.
Do we get to work on RAC after the beers? I'm working for the wrong company !![]()
Last edited by scratchy; 01-27-2013 at 09:45.
My EDC: Handcuffs, Bandana, and Ball Gag.
If I'm ever at a party and the cops come to arrest people. Ill blindfold myself, throw the ball gag in, handcuff my hands, and hide in a closet. Police never arrest hostages!
Are you looking to be a DBA or a database developer? There is a big difference in what they do, even though most folks think the two jobs are the same.
Shot Works Pro... It's better than scrap paper!!!
You can use the discount code 'Take5' for 5 bucks off.
I would like to expand my knowledge in both areas. I am currently working on my MCTS70-432 and 70-433 which would be (DBA 70-432 and Developer 70-433) My company currently doesnt have anyone who is either. We have people that know what they are doing but they dont do that constantly. I am trying to create a position for myself. My company takes really good care of me and I am very motivated to become a much larger part within.
Basically what I am saying is I am willing to take what is thrown at me. I enjoy writing complex queries more than administration. I have always been willing to do "bitch" work because I have always learned something from doing stuff other people dont like doing. Thats usually why its concidered bitch work because they arent very familiar with it.
My EDC: Handcuffs, Bandana, and Ball Gag.
If I'm ever at a party and the cops come to arrest people. Ill blindfold myself, throw the ball gag in, handcuff my hands, and hide in a closet. Police never arrest hostages!