<<<<<<<<1. 1 yr - internal audit (no IT job but i need to eat)
2. 2 yrs - IT support (oracle 8i, e-business suite 11i - financials, purchasing, PC >>support. have to quit because IT dept are forced to do non-IT stuff -- there goes >>my dba plan
This thread and a couple of other recent postings in a similar vein have prompted me into some extended musing on why people want to be a DBA. See my blog if you're interested.but i always wanted to be an oracle dba.
Yes and the rest usually come in through being a sysadmin. It is interesting that now there is a third route - application server, not least because this tool uses a database for some of its functions. AS underpins Collab Suite, so I would have thought the current position is a possible springboard into a fully-fledged DBA role.The great majority of people hired into entry DBA positions have development experience
Well obviously YMMV applies here. Some shops have sysadmins, DBAs, network engineers and app server guys in separate units, maybe in separate offices. At the other extreme in smaller places they all share the same pair of pants (because they are the same person, no aspersions on personal hygiene habits of admin people intended). But I have come across several places where these tech-y infrastructure roles are lumped into one unit, with at least the possibility of cross-fertilisation of experience and even job-swapping.But how much DBA work (creating objects, making db backup, practicing restore and
recovery, SQL tuning) would an web server administrator ever do? We dumped
the web server on the System Administrators