LINQ scares the heck outta me!

Some integration efforts are great ideas, but others are not sure bets. Such as the inventor who wanted to make carbonated vegetable drinks.  Sure, the idea integrates the great nutrients of vegetable juices and the effervescence of sodas.  But, in this case, 1 + 1 = 0.

I’m wondering if Microsoft’s newest language development idea, called LINQ (for the .Net Language Integrated Query), is a sure bet or not.  LINQ was announced at Microsoft PDC (Professional Developer’s Conference) yesterday and was created by .Net grandfather, Anders Hejlesberg.  LINQ is intended to solve the problem of how to integrate various sources of data into applications built with object-oriented programming models.

LINQ does this by adding new data-query capability to .Net languages.  Now, this is not just relational databases, this applies to all forms of data such as XML documents from the VB.NET and C# code.  You will then use the LINQ syntax for querying data rather than using SQL (the Structured Query Language).

Am I in favor of this direction?  Well, there are two sides to this coin.  Developers are going to love not having to learn new languages, and the additional debugging, troubleshooting, and performance tuning techniques for a whole new language.  On the other hand, as an enterprise DBA, I don’t like it. 

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

 

Every enterprise IT shop I visit these days has multiple database platforms in place.  As a database professional, you’ll need to be able to move between these platforms.  You won’t need to move smoothly, but you should be able to at least write a decent SELECT statement on each of your major databases.  Will LINQ enable you to do this – almost definitely not – unless the database platforms of your enterprise IT shop consist solely of Microsoft SQL Server.

 

The silver lining in this cloud on the horizon is that it is far, far off on the horizon.  LINQ probably won’t be here for a long time.  It requires new work in both Visual Studio and SQL Server, and we all know how long the last iteration of those products took.  Still, it’s something to think about and keep in mind.

 

For more details, see http://www.infoworld.com/article/05/09/14/HNfuturewithlinq_1.html?source=rss&url=http://www.infoworld.com/article/05/09/14/HNfuturewithlinq_1.html.

 

Let me know what you think.  Is LINQ more bark than bite?

 

Cheers,

 

-Kevin

Please or Register to post comments.

Upcoming Conferences

Register now to get the best rate available!

From the Blogs
Baby duck swimming alone
Jul 15, 2014
blog

The Marginalization of SQL Server Standard Edition 5

Microsoft seems to be bent on marginalizing SQL Server Standard Edition—both in the sense of the artificial constraints placed upon how much memory it can use, and in terms of what seems to be a shift in focus on the role of Standard Edition from Microsoft....More
Jul 8, 2014
blog

Replication: Sometimes More is Less

The unconventionality of having two publications for complex, unruly databases typically ends up saving huge amounts of time over the long haul and makes replication much easier to manage....More
Red restore key on computer keyboard
Jun 24, 2014
blog

AlwaysOn Availability Groups and Third Party Log Readers

When DBAs and SysAdmins learn the ins-and-outs of AlwaysOn Availability Groups, they’re then able to address high availability and disaster recovery concerns from a single interface or set of tooling, thus providing better scalability of management....More
SQL Server Pro Forums

Get answers to questions, share tips, and engage with the SQL Server community in our Forums.

Sponsored Introduction Continue on to (or wait seconds) ×