July 11, 2008 at 10:15 am
Hi,
i m learning sql server 2005 and want to become a DBA ..
i learned database engine,indexing,partition,notification service,optimization and maintainence,installation,security,configuration,schema,tables ,views..
i just want to know that do i have to learn integration service (i know ETL)replication service,analysis service, locking this subjects?
please guide me..
July 11, 2008 at 1:50 pm
how much amount of knowledge i need to start my career as trainee dba
I think you're going to get a wide variety of answers to a question like this, but I don't think you need a great deal of knowledge to get into a 'trainee' DBA position. This type of position, to me, represents an entry level into the DBA career path where most of your knowledge would come from continuing your self-education, maybe some employer-paid Microsoft SQL Server courses, on-the-job experience, and lastly, but most important, mentoring under a Senior level DBA. I would think that you only need a basic knowledge of RDBMS's, core competency in application systems and client-server architecture, and basic relational theory to get started down this path. Any topic related self-study such as what you've mentioned would be a major plus, but in my opinion not required for an entry level DBA position. The best attribute you could have is the willingness and desire to learn the trade, the humbleness to take coaching and mentorship from others with experience, and be a fast learner.
Much of what you'll do as a DBA will depend on what type of shop you end up in. DBA's today have a vast difference in responsibilities and skill set requirements depending on their role within their organization. For example, a Production DBA's focus would be on administering security, monitoring and patching servers, application performance monitoring and troubleshooting, ETL activities as needed, assisting end-users with query writing, data conversions, replication, etc. A Development DBA would be more focused on data modeling, stored procedure programming, system architecture, data flow analysis, indexing and storage strategies, etc. These are just a couple. Now you see database developers, BI developers, Data Warehouse DBAs, ETL specialists, Data Architects, etc, and many of the skill sets overlap into each of the specializations.
So to answer your question, much of what you'll need to know depends on where your focus will be once you get in somewhere. Most of your learning will come through experience so a great deal of what you are learning now could be easily forgotten if not put to immediate use. I've always tried to stay as well-rounded as I can so that I can delve into any aspect of database work that comes around. I think that with what you've already learned/studied, you should be able to get your foot in the door somewhere. Surely someone will give you a shot if you come off as teachable and motivated.
P.S. Just a side note, technical skills are great to have, but people skills will get your farther (even in technical positions). Learn how to deal with people!!
July 11, 2008 at 4:28 pm
oh my god ..what a great reply ..the way u explained me ,it cleared my all d doubts..salute u..thanks sir!!!!
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply