Hi just Got the book very intresting

just one question tho why did you choose to do it with stored procedures and not Linq Querys? thanks David

Hi David,

You can use LINQ queries or stored procedures to access your data. It really depends on what you are more comfortable using. However, stored procedures are compiled and generally run faster than LINQ queries, although depending on what your doing you may not notice the difference.

If you've gotten to Chapter 10 you'll notice that the Query Builder control is creating a dynamic where clause and executing in-line SQL against the database. The book shows examples of LINQ queries, stored procedures, and in-line SQL. All three are viable options, I choose stored procedures for speed of execution for the majority of the queries.

Hope this helps,
Vince

Based on what I've read online (I haven't been able to use ORM at work for various reasons), both parameterized SQL and stored procedures get their execution plans compiled and cached by SQL Server. Then the issue is server memory and how long these plans stay cached before they are bumped.

(I'm sure you're well aware of the 5+ years debate about stored procedures vs. an ORM's generated SQL.)

I'm not familiar with the DataContext's ExecuteQuery internal mechanics. Would inline SQL become subject to SQL injection attacks based on user input?

Thank you for writing this book, there are very few like it.