kimberly_lehman (6/6/2014)
You could potentially miss out on some great employees if you let your ego get in the way of making an objective hiring decision. I've been working with T-SQL for over 10 years and I've helped to make a lot of money for the companies I've worked for. I've also had a very wide variety of experience which I think makes me a valuable asset, but it also means that I don't have to write that particular piece of code frequently enough to have it memorized. I don't mind admitting that I don't know everything. I figure out what I don't know.
That seems valid. However, if you're trying to get a T-SQL developer job, you should at least prepare to don't confuse most functions. I've interviewed some people who claim to have worked with Oracle who presented for SQL Server and wouldn't get correct the Oracle or the Sql Server option.
Most people won't be able to differentiate inner joins from outer joins and some even consider left join different from outer join.
If you've worked over 10 years with SQL Server, you should know that most answers are on BOL and you don't even need Google. I worked for a company for 5 years using SQL Server and made them make a lot of money but that didn't make me good on T-SQL, it only made me an "Expert Beginner".