Should Microsoft-oriented Database Administration and Database Development be kept separate (as in, separate positions)?
The question was raised to me “Why are the words Microsoft-oriented in the question?”. While I am definitely open to input from anyone who wants to weigh in on this question, I used the words “microsoft-oriented” NOT because I think best practices should “change” per toolset or platform, but because the applications that fall under the “SQL Server 2005” and “SQL Server 2008” umbrella cover a very wide range of functionality – much of which does not fall under any of the typical “job descriptions” of a DBA – nor a DBD. I’m particularly interested in how others are addressing these issues. It’s insufficient (IMO) for a traditional DBA to be expected to administer Analysis Services or Reporting Services simply because it’s a “database product”. Many of the traditional lines have been blurred with the more recent advancements in Microsoft’s database platforms…
Related Questions
- Is there a separate application process for the Certificate in International Studies or the Certificate in International Development?
- Should Microsoft-oriented Database Administration and Database Development be kept separate (as in, separate positions)?
- Are protected rights kept separate from non-protected rights?
- Are protected rights kept separate from non-protected rights?
- What is Database Administration?
- What is Database Administration?
