Problem: we've grown to the point where we need a real DBA. Real DBAs are hard to find.
Possible solution: I know someone with extensive experience (currently working on MSSQL) who is looking for a new DBA job. He might be willing to consider working for a MySQL shop (I haven't asked).
Snag: I don't know to what extent MSSQL DBA skills map to MySQL DBA skills. I'm a developer, so I know enough about MySQL to develop apps which use it (including the basic performance-tuning, index selection, etc.), do schema design, and perform simple utility tasks (backup with mysqldump, scripting, etc.). I don't know anything about MSSQL. Nor do I actually know much about the boundaries of the DBA role.
Can anyone with more experience - perhaps as a DBA - weigh in on this? Are there enough similarities between MSSQL and MySQL that it's worth asking a MSSQL DBA if he'd be interested in applying for a MySQL position?
I probably wouldn't go for this without further evidence of MySQL-specific knowledge or qualifications. You wouldn't hire an experienced Windows admin to take care of your Linux boxes either, would you? With experience in a different environment, you would know most of what to do, but probably not much about how to do it.
That said, MySQL offers a number of trainings and certifications, so maybe the candidate should take a round of those. That should get him up to speed with the product specifics.
It really depends upon the DBA.
I used to manage a few teams of them - Informix, Oracle, MS SQL and some are willing and eager to learn another platform, while others are not.
The basics are pretty much the same, but the details are very different.
I recently went back to hands on, in Oracle initially and had an opportunity to work on a SAP project using DB2. I had little DB2 experience before this, but with experience on many DB flavors came up to speed quickly.
You do not say which platform you are running MySQL on. If it is Windows, your friend would probably come up to speed very quicklky. A big part of being a DBA in a small shop is managing, tweaking, and tuning the host OS as well as the DB. If you are running it on Linux, I would have to ask how much xNIX experience he has as well as the DB experience.
I hope this helps.
Some skills are transferrable ie. database structure optimisation, sql, etc. as the same basic concepts apply to both MSSQL and MYSQL. However things like performance tuning and the way you go about task are highly specific to each platform.
I would say that it is possible to cross over with a little work as long as you have half decent Linux skills already.
But contrary to what someone said earlier I would take an MS DBA over a Linux admin if you can't get a Linux DBA because you can learn the Linux interfaces much more easily than DBA concepts and gotchas.
i'd rather take linux admin without earlier experience with database administration than mssql expert. but that's highly subjective.
Like Kevin K said, it depends. One thing to consider is what you mean by DBA. In larger shops the DBA is primarlily looking at code and database application performance tuning (what microsoft certifies as MCITP: Database Developer 2008 ) and an admin looks after the OS performance tuning and knows just enough sql to figure out that a performance problem is not a OS issue but a blocked process instead (that's what microsoft considers an MCITP: Database Administrator 2008). I'm not positive but I'd be suprised if mysql certs are not similarly split.
In small shops the DBA does both, so there may be a learning curve for a DBA who never did any real windows admin work, in addition to the the fact that they simply may not want to do linux administration.