LSAdvantage (9/17/2010)
I am a .NET developer working with a small team of developers who have to also double as our own DBDs. Recently, the subjects of LINQ to SQL and Entity Framework have been raised by one of our developers. I realize this is a SQL Server forum and developers would be using these via .NET, but I want to know how DBAs feel about these technologies hitting their databases. I've very quickly skimmed:LINQ - http://msdn.microsoft.com/en-us/library/bb308959.aspx
Entity Framework: - http://msdn.microsoft.com/en-us/library/aa697427(VS.80).aspx
At first glance, this goes against everything I was taught. I was taught "NO INLINE SQL!" yet that's what I'm seeing here. And I even saw a foreach that looks like it is possibly masquerading as a cursor (another big no-no). I rarely have a call to the DB that is a simple "select this from that where this". Most DBAs do not want developers hitting the database like this. Am I completely missing the boat here? Is this a huge paradigm shift that we need to embrace? Does using these technologies mean DBAs roles will change to be more operational DBAs? I can't see any of you wanting that to happen, right?
I'm just looking for top of the trees feedback on these concepts. I'm not ready to drink the Kool Aid yet.
I started working with databases before the invention of relational databases, even then programmers managed to mask row-by-row loops on the application side - some stuff is not meant to change as I can see. 🙂
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.