• For a very, very simplistic view of becoming a SQL Server DBA 5 stars, however in the REAL WORLD only 1 star - how many of us actually wanted to become a DBA and just fell into it by accident? Hell I even had to retake Database Design in my degree as I didn't "get" Normalisation (eventually it clicked) however I didn't become a SQL DBA until nearly eight years later - now *then* 3NF et al became very handy.

    How many companies acutally give people training? Not willingly I'd guess.

    I'd add a few other points for the real world:

    1. Get a mentor - a few posters mentioned this and this is how I got started.

    2. Buy one book and one book only - the rest is on BOL/Web/SSC (Unfortunately you could just buy Inside SQL Server 2000 however now they've split it into about four books - pick one! 😛

    3. Become a contractor. I've been a SQL DBA Contractor for nearly 10 years and in that time I've been a Developer, Production DBA, you name it I've had to fix it! 😀 And it's probably only at this stage that I can fully understand SQL Server (I'm still working on AS!)

    4. MS Courses/Exams - sure, they're nice to compliment your CV and brag to your collegues, but in my time I've only been on a few SQL2K and one 2005 course and have never taken any exams - i'd probably fail! 😀

    I had a conversation with a SQL DBA staffer colleague and I was taking about index fragmentation and using DBCC SHOWCONTIG and what scan density was and how to fix it all. He looked at me blankly then said he didn't know any of that - this guy has a MCITP for SQL Server 2005! :w00t:

    I rest my case, m'lud.

    Rgds,

    quackhandle

    [font="Tahoma"]Who looks outside, dreams; who looks inside, awakes. – Carl Jung.[/font]