• Since we've gone through two year searches in the past for DBA's, I sure can't tell you how to find them. While we weren't trying to get them to know .NET like Blandry, we did expect them to know SQL Server. It was extremely frustrating looking through stacks of resumes, most with 3-7 years of experience but with only 1 in 10 able to answer a majority of the questions posted here[/url].

    Since I work for a large company, we've had better luck getting people from within the company. There are so many jobs that work with data. You can identify developers or report writers or ETL people working within their area that are likely candidates. Grabbing them and training them up has been more successful than tracking down viable candidates through any of the job sites.

    BTW Blandry, if it makes you feel better, we would have found even fewer people if we also required .NET. There are a few of us that came into the DBA job through the programming route that understand .NET languages, but most people came up through systems or ETL and only know databases, TSQL, and servers.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning