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.

From the Blogs
Jul 17, 2017
Sponsored

How Inferred Linking in Matched Records Digs Deeper into Your Data

Duplicate records clutter databases and render the data within them unclear. This kind of problem is very common, and it’s the main reason that deduping software exists. But there’s another benefit to deduplication software: the ability to infer connections between individual records from various data sets....More
May 22, 2017
Sponsored

Chief Data Officer Playbook: How to Be Successful in This Ground-Breaking Role

Companies looking to grow and extract value from their data are increasingly turning to Chief Data Officers (CDOs) to execute their data strategy. The role is new, and a playbook is necessary to address the many challenges CDOs face....More
May 12, 2017
blog

5 Common Challenges to Building BI in the Cloud

After spending 20 years building analytics, BI and database solutions, I've focused on Cloud data solutions over the past 2 years. I've chosen 5 common challenges that I face every day with Cloud migrations and that you'll face in your Cloud BI projects....More

Sponsored Introduction Continue on to (or wait seconds) ×