How to sell LINQ to DBAs?
-
This is an interesting problem: how am I going to get my DBA on board? Let's say that I am convinced and I want to go LINQ. All the DBAs that I have talked to have had the same attitude towards LINQ. Can you point out any arguments that would make sense from this perspective?
Cheers, Dani
-
This is an interesting problem: how am I going to get my DBA on board? Let's say that I am convinced and I want to go LINQ. All the DBAs that I have talked to have had the same attitude towards LINQ. Can you point out any arguments that would make sense from this perspective?
Cheers, Dani
"Developers won't actually be writing the SQL, the query will be generated on the fly by expert written Microsoft/D&C libraries." has worked for Diamond Binding in the past - which has very similar resistance from DBAs (especially the ones that love their stored procedures) ;)
Mark Churchill Director Dunn & Churchill Free Download:
Diamond Binding: The simple, powerful, reliable, and effective data layer toolkit for Visual Studio. -
"Developers won't actually be writing the SQL, the query will be generated on the fly by expert written Microsoft/D&C libraries." has worked for Diamond Binding in the past - which has very similar resistance from DBAs (especially the ones that love their stored procedures) ;)
Mark Churchill Director Dunn & Churchill Free Download:
Diamond Binding: The simple, powerful, reliable, and effective data layer toolkit for Visual Studio.to be fair, that sounds perfectly reasonable and you would think it would suffice. however, you haven't met the DBA that I am facing. :doh: Do you have any other selling points?
Cheers, Dani
-
This is an interesting problem: how am I going to get my DBA on board? Let's say that I am convinced and I want to go LINQ. All the DBAs that I have talked to have had the same attitude towards LINQ. Can you point out any arguments that would make sense from this perspective?
Cheers, Dani
Show him Linq using stored procedures. Once you've piqued his interest you can take him on a journey "into the mind". Anyway, Linq is for more than just databases - there's a whole world of XML to play with.
Deja View - the feeling that you've seen this post before.
-
to be fair, that sounds perfectly reasonable and you would think it would suffice. however, you haven't met the DBA that I am facing. :doh: Do you have any other selling points?
Cheers, Dani
DBAs don't like to give up ownership of their databases, which is fair enough. It is an issue with LINQ and ORMs (ones that are flexible enough to query themselves) that the queries they execute on the database aren't precisely determinable. Moving to an ORM solution though is typically suggested by the devs (ie: its going to be easier/faster/better to use), but the actual decision to go with it is made at the architecht level - and the DBA is told to go along. Personally I have used ORM products (sometimes ours, sometimes vanilla nhibernate) in a variety of large systems and havent had a problem with it. I can only assume LINQ will be the same - as long as you have indexes in the correct places and don't accidently ask for huge amounts of data in a non-lazy fashion, its all fine. Its the usual issue with abstraction. You can put a nice interface on something that suggests it will work a certain way - but that doesnt change whats actually happening on the metal ;)
Mark Churchill Director Dunn & Churchill Free Download:
Diamond Binding: The simple, powerful, reliable, and effective data layer toolkit for Visual Studio. -
DBAs don't like to give up ownership of their databases, which is fair enough. It is an issue with LINQ and ORMs (ones that are flexible enough to query themselves) that the queries they execute on the database aren't precisely determinable. Moving to an ORM solution though is typically suggested by the devs (ie: its going to be easier/faster/better to use), but the actual decision to go with it is made at the architecht level - and the DBA is told to go along. Personally I have used ORM products (sometimes ours, sometimes vanilla nhibernate) in a variety of large systems and havent had a problem with it. I can only assume LINQ will be the same - as long as you have indexes in the correct places and don't accidently ask for huge amounts of data in a non-lazy fashion, its all fine. Its the usual issue with abstraction. You can put a nice interface on something that suggests it will work a certain way - but that doesnt change whats actually happening on the metal ;)
Mark Churchill Director Dunn & Churchill Free Download:
Diamond Binding: The simple, powerful, reliable, and effective data layer toolkit for Visual Studio.Thank you for your thoughts. I can see it going that way and it will probably be an "enforced architect decision", even though I usually prefer to get people on board instead.
Cheers, Dani
-
Show him Linq using stored procedures. Once you've piqued his interest you can take him on a journey "into the mind". Anyway, Linq is for more than just databases - there's a whole world of XML to play with.
Deja View - the feeling that you've seen this post before.
I totally agree there's much more to LINQ than DLINQ but I am keen on using this one as well because I see many benefits, especially in the field of productivity and maintainability. I will try to use the stored procedures as a "trojan horse" :)
Cheers, Dani
-
Show him Linq using stored procedures. Once you've piqued his interest you can take him on a journey "into the mind". Anyway, Linq is for more than just databases - there's a whole world of XML to play with.
Deja View - the feeling that you've seen this post before.
Pete O'Hanlon wrote:
Linq is for more than just databases - there's a whole world of XML to play with.
Absolutely. I was rejoicing for a while when I briefly came to the conclusion that I would never have to deal with XPath again. Then a colleague showed me a scenario where I still needed XPath. Boo! :( Since then I've realised I still need XPath for lots of things.
Upcoming FREE developer events: * Developer Day Scotland Recent blog posts: * Different ways to add point data in SQL Server 2008 * Spatial References in SQL Server 2008 My website |
-
Pete O'Hanlon wrote:
Linq is for more than just databases - there's a whole world of XML to play with.
Absolutely. I was rejoicing for a while when I briefly came to the conclusion that I would never have to deal with XPath again. Then a colleague showed me a scenario where I still needed XPath. Boo! :( Since then I've realised I still need XPath for lots of things.
Upcoming FREE developer events: * Developer Day Scotland Recent blog posts: * Different ways to add point data in SQL Server 2008 * Spatial References in SQL Server 2008 My website |
Colin Angus Mackay wrote:
Since then I've realised I still need XPath for lots of things.
Irritatingly though, no XPath 2 support. :sigh:
Deja View - the feeling that you've seen this post before.