jvinsonncsu (10/26/2015)
This discussion hit a new turn. I am a software engineer who is getting MCSA designation because I wanted to know the whole picture. I know better than to ignore our DBA. I don't believe too many of my counterparts feel the same way though. I have seen it first hand. Working together you get a much better product and truthfully I use SQLite automation for column etc any time I can. I mean come on. Awl server agent rocks. Particularly with SSIS packages.I will pose a new question: Why do so few software engineers/developers try to learn everything they can about the deep workings of SQL server?
Not biased one way or the other. I am just curious.
I think I know the answer to that one: it's a result of overspecialisation, which is largely driven by sterotyping by recruiters. A developer needs to be not just a developer but a C++ developer or a C# developer of a Java developer or whatever kind of developer the recruiter is looking for, so time spent on looking at SQL Server internals won't buy employability in the market for developers. And looking at the internals of SQL Server would sound to a profesional recruiter (normally someone who hasn't a clue how many wheels a computer has or whether it runs on diesel or coal - believe me, when recruiting people I've had to deal with some of these recruitment "professionals" and they really haven't a clue) like someone who was looking at the internals of Microsoft's C# compiler - they wouldn't have a clue that understanding SQL Server internals would be of much greater use to an SQL developer than looking at the compiler's workings would have for a C# developer.
Tom