Technet Spotlight On Demand Video - Luca Bolognese - LINQ to SQL: Accessing Relational Data with Language Integrated Query

Database-centric applications have traditionally had to rely on two distinct programming languages: one for the database and one for the application. In this session we will introduce LINQ to SQL, a component of the LINQ project designed to help integrate relational data and queries with C# and Visual Basic. LINQ to SQL enables developers to express queries and updates against the SQL Server family of databases in terms of their local programming language without sacrificing the server-side execution model of today's high-performance SQL-based approaches. Using these advances, database queries that previously were stored as opaque strings now benefit from static type checking, CLR metadata, design-time type inference, and of course IntelliSense. LINQ to SQL also supports a rich update capability that lets you save changes to an object graph back to the database using optimistic concurrency or transactions.

https://www.microsoft.com/emea/msdn/spotlight/sessionh.aspx?videoid=716

Comments

• Anonymous
  January 01, 2003
  This is not just another ORM. Other ones like Nhibernate, ntiers, etc can't modify the inner workings as M$ can.. Very informative, love it so far.  Kudos to Luca's presentation, somehow you remind me of "Borat" :)

• Anonymous
  January 01, 2003
  You really nailed this concept for a EF "newbie"  Thanks for taking the time to prepare such a great presentation.  Wish I could have been there in person.

• Anonymous
  January 01, 2003
  Sorry, but was not impressed at all. There were a lot of obvious glitches and misstatements. "LINQ queries can handle any SQL and may even be better than SQL." Has any one shown him an outer join nested query that spans multiple tables, with "having" clauses and aggregate functions? It seemed just as tiresome to build the objects, build the right queries, debug them, see the data and SQL generated, and go back and forth until you finally get what you want. I don't see how that is any more efficient than just writing SQL and talking to the database directly with ADO.NET Wish LINQ and Luca the best. For some developers everything Microsoft pushes out is the best.. for the rest.. keep looking to solve your database problems..

• Anonymous
  January 01, 2003
  I am not impressed at all by this technology since it is another ORM layer with embedded syntax in the language and the CLR.How can you state with such assuarance that every possible SQL statement can be translated to this language? What methodology have you used to prove this? Why does an object have to match a table one to one? How about if my "square data" as the speaker mentioned, each column needs to match some field in some object and those fields span multiple tables?  

• Anonymous
  January 01, 2003
  The Comment at 16:00 about why LINQ uses FROM first is interesting. An additional reason FROM first makes more sense than SELECT...FROM...WHERE is that if you look at how relational algebra works and how SQL Server actually pulls data, IT Executes FROM to get the table, WHERE to get the Rows and SELECT to project the columns.  SELECT is the LAST thing chosen when Queries are run.

• Anonymous
  January 01, 2003
  LINQ is really exciting stuff. Thanks for a cool demo.

• Anonymous
  January 01, 2003
  Really good presentation, cleared all concepts associated to Linq.

• Anonymous
  January 01, 2003
  Well Done ! Thanks a lot ! Very interesting useful and good-explained information with a lot of funny moments

• Anonymous
  January 01, 2003
  This was very informative. Finally a decent way to program queries. GREAT JOB !!

• Anonymous
  January 01, 2003
  Hi, Thanks for the excellent presentation.  Shows that LINQ is a real game-changing technology.

• Anonymous
  January 01, 2003
  The comment has been removed

• Anonymous
  January 01, 2003
  I am really impressed with the Entity Framework. You guys have done wonderful job.