Unless I indicate otherwise, you can assume that any feature I reference from an older release still applies today. I also talk about the SQL Server Isolation Levels, which Microsoft added in SQL Server 2005. In this article, I refer to the MERGE and GROUPING SETS enhancements, which Microsoft added in SQL Server 2008. Some developers might have to support older versions of SQL Server.
Baker's Dozen Spotlight: Dealing with a long list of columns in a MERGE statement.Understanding the SQL Server Snapshot Isolation levels.Understanding the SQL Server Isolation Levels.Determining when subqueries are necessary.Obtaining the row count of every table in a database.Knowing the differences between Materialized Views and Standard Views.
Although this article isn't an interactive software product that requires you to answer before seeing the results, you'll at least have a chance to read the questions and try to answer, if you can avoid peeking to the second half of the article to see the answers! In the first half of this article, I'll cover the test questions, and then in the second half I'll cover the answers. (These are the types of interview questions I'd expect a mid-level database developer to be able to answer). I'd categorize these 13 questions for intermediate developers. Regardless, the more a person can speak in terms of scenarios on a technical topic, the more likely they'll impress the interviewer. I can't guarantee that any topic I cover in these articles will appear on a technical interview screening (though I suspect a few will). In other words, the dirty details and their role in reality checks-are precisely what Robert Palmer was talking about.Ī few readers might be going on database technical interviews in the near future. Often, discussions with other developers help to bridge technology gaps, address misunderstandings about how a specific database feature works, and why a feature might work acceptably in one scenario but not others. In my opinion, one of the keys to success is recalling past issues and even prior mistakes, and how you solved/learned from them. Nearly every week, I work with developers on database technology topics that remind me of prior blog entries, interview and certification questions, classroom discussions, and webcast talking points that go back many years. I have a million shortcomings in life (as friends and co-workers will attest), but one of my strengths is a photographic memory. Some days I write code, some days I lead in design efforts, and often I'm laying out work for others and going over some of the technical hurdles they might face. In my consulting business, I mainly serve as a technical database/applications mentor. Those occur in software development as well! One of my favorite musical artists is Robert Palmer and one my favorite Palmer tracks is called “Life in Detail.” The song contains rapid-fire lyrical messages about reality checks, false conclusions, perspectives, and (painful) discoveries.
In the last issue of CODE Magazine, I started using the Baker's Dozen format to present 13 technical test questions on SQL Server topics, and I think that format will work well for this subject. I'm going to borrow from those experiences in this installment of Baker's Dozen, by giving you a chance to take a test on SQL Server and Transact-SQL topics. I also taught SQL Server programming for years, coached people preparing for technical interviews, and authored certification and test questions. Of course, I've also sweated through interviews as the applicant. I've interviewed other developers, either as a hiring manager or as part of an interview team. Throughout my career, I've been on both sides of the interview table.