If I were just starting out in this field today, I'd be asking the same questions. I was fortunate to be an "accidental DBA" starting back circa 1996 and had been in the world of computers long before that. With the understanding that I'm probably not qualified to help someone trying to break into the field figure out how to break into the field, I can tell you what I'd do if I had to start now.

You're on the right track. The certifications will help you focus on the "what is" and "how to". Except for the coveted MCM certification (think PHD in SQL Server) that may not be enough to land you your first DBA job any more than graduating from medical school qualifies you to be a neurosurgeon. There are also things that no certification will teach you. For example, I know of no SQL Server cert that teaches things like the "Tally Table" and how to use it to make blazing fast code instead of using certain types of WHILE loops. You either have to learn that on the "streets" (forums like this one) or, if you're lucky enough, to find it in a good book.

With that in mind, start building your personal "brand". Step 1 is to buy a copy of the Developer's Edition of SQL Server and start solving problems by researching the solutions both on the web and in Books Online (the technical bible for SQL Server which is available by pressing the {f1} key in SSMS). There's no better source of worldly problems than forums like this one. Pick a forum or two and participate heavily. Remember that you won't only be judged by the problems you solve, but how you solve them and how you react to people on the forums. You could do the same thing with a personal blog but I find that the exposure in well known public forums is a much better teacher and witness to your skills (including people skills) than a private blog ever will be. There are exceptions, of course, but neither you or I qualify as a Paul Randal, Kimberly Tripp, or Brent Ozar.

If you can afford it, buy a couple of machines and setup your own network at home. I don't know if there's such a thing as the Developers Edition of Windows Server, but the Developers Edition of SQL Server (about $60 USD including shipping and handling from Amazon) is the same as the Enterprise Edition and will work on a standard desktop box without Windows Server.

If you really want to be recognized by future employers, dedicate some time sharing your newfound skills with a charity or two of your choice.

When you think you're ready for the "show", contact a trusted recruiter or two and tell them that you're trying to break into the DBA world. Be prepared to tell them if you want to be "only" a Systems DBA, "only" and application DBA, or a "hybrid" that can to some of both. They should be able to help a lot because they know what every company in the region does, what the culture of the company is, and not only whether or not you not you might be able to do the job, but whether or not the company will give you a chance and whether or not you'll fit in.

To actually get a job, you have to pass an interview. Nothing in this world can prepare you for such a thing except the interviews themselves. Don't be nervous. When they ask you a question, answer the question honestly and, if you can (when appropriate), show that you really know the answer but talking about it, it's pros and cons, and any alternatives there might be. Any bulls4it or floundering on your part will be easily caught and weighed very heavily against you. It's better to answer "No, but here's how I'd find out" than it is to try to BS your way through a question that you really don't know the answer to.

To get an interview, you need a resume. You have somewhere between 1 and 15 seconds to have someone put your resume in the "look at again" pile or the round file during their first pass through the resumes. What are they looking at to make such a decision so quickly? Whether or not you have an "Objective" or not and if you do, what is says. If you put in some touchy-feely crap like "To further enhance my skills" or "To learn from the best", you're usually toast. A simple list like "SQL Server Certified DBA, T-SQL, SSIS, SSRS, and SSAS programmer" is all that they're looking for in the objective. The next thing after the objective should be a summary of what you can actually do. Think of it as an extension of the Objective. And, contrary to belief, honesty goes a very long way. If you're in the middle of learning something really good about SQL Server, it's ok to list it with "(Training in progress, 50% complete)" next to it.

Of course, you'd better be able to actually do what you state on your resume.

There's also the matter of job history. Although the recruiter should write the cover letter and they should explain your change in career, you should also include that explanation right at the beginning of the job history section of the resume because the cover letter doesn't always make to the people that are going to do the interview. Include your studies as if the were a full or part time job from some date to "Present". Include important points like how many hours of study you put in, that you have setup your own server and practiced, that you DO have and use a copy of SQL Server Developers Edition, and a list of the books you've studied in depth. Again, anything you put in this section, you'd better be able to actually do or have actually done.

I have to emphasize this and then I'll get off the soapbox and stop bothering you. [font="Arial Black"]If you get caught in lie, your new career as a DBA is over before it even started because being a DBA is one of the most trusted stations in life that you'll ever have.[/font] And, yes, if you lie, you will get caught. It's the nature of the position.