ChrisM@Work (12/3/2013)
Steve Jones - SSC Editor (12/2/2013)
L' Eomot Inversé (11/24/2013)
I think the idea of "Core TSQL" isn't unreasonable, but no set of knowlege which is just about T-SQL and not about the bigger picture will ever make a competent database developer.I tend to agree. I was just focusing on T-SQL here. There are other skills, but we can easily get to a large list that's hard to discuss/debate.
I'm also inclined to agree with Tom, however, converting "the bigger picture" into a set of bullet points isn't straightforward. "Know your data", for instance. How you acquire that knowledge, with or without a usable ERD, is driven by numerous factors. Just thinking about it - and I'm in the middle of the process right now, two weeks into a new gig - it seems like a different method every time.
Relationships in the data - they only tell a small part of the story, especially in a data warehouse. Many times there will be a Business Logic layer, and this can be a key part in really 'understanding' the data.
I fall into the same thought pattern as Tom. If it is just the technical skills that they have, it's very possible that they are only a good order taker. The best work is usually the result of good back and forth conversation with the business, especially when a developer can map out some of the what if scenarios.
In light of how quickly the list can grow and vary in different environments, it is hard to focus on just T-SQL.
Desire to learn and master the unknown as it comes up (business changes over time), is something hard to quantify. But I see as important to success, and might be used to cover some of the scope creep.