I enjoyed reading the article as I use articles like this to help me determine what SQL Server skills I am missing that I should have. I also think this article relates to the recent editorial, The General. SQL Server has become so complex that it is difficult to answer all the questions about DBCC commands, etc.. and know all about Windows clustering, RAID, etc.. The tools for SQL Server have gotten better also, so you can maintain a SQL Server without using DBCC commands directly. When I am in an interview I am upfront that there is more I don't know about SQL Server than I do know, but I know where to go to find the answers I need to a problem, whether BOL, google, or SSC. I can do the Day to tasks security, backups, restores, etc.. and in 8 years of working with SQL Server I have never had to do a point in time restore and have only once had to restore a failed server. It was a long night, but no data was lost because we had a good backup plan in place. If I were hiring a DBA, or any IT staff, the first thing I want to see is someone who know they don't know it all, but know where to go to find the answer. Just don't use QotD in the interview. Why would I know that stored procedures can accept up to 2100 parameters!:w00t: