LINQ to SQL, ExecuteQuery, etc.

Question

All of this may be a bit subjective:

Our organization has made a determined attempt to use LINQ to SQL as our primary method of accessing data, and for the most part, this works well. (Let's leave EF out of the discussion.)

Some of our developers find LINQ difficult and switch to traditional raw SQL through ExecuteQuery. We also use OpenQuery in some of our applications to access data on remote servers. OpenQuery cannot run through LINQ and always leads to code execution through ExecuteQuery. As an organization, we also decided to move away from stored procedures and rely on LINQ again.

So, is it possible to say that some queries are so complex that they cannot be completed using LINQ? We want to avoid the business logic in the database, so where do we go when you can't use LINQ? What is the general feeling of ExecuteQuery as the best alternative to ADO.NET Command.Execute ()? I think that one can make an argument against stored procedures, or at least avoid them, this is the right choice, but what about a Views query with LINQ as an alternative?

Thoughts on where to land the plane on this? What are others doing?

Thanks,

Answer 1

. Linq-to-SQL , -, . Devs , , , - !

- , SQL- - , - , ExecuteQuery. CTE , Linq-to-SQL, , , T-SQL ....

, - ! , LINQ. , , , . , SQL , LINQ ( - ).

Answer 2

, "", Linq-to-Sql. , Linq-to-Sql , SQL-.

, READ, VIEW LINQ. / , SQL .

, / Linq-To-Sql. , SQL-, - , Linq-To-Sql. : Linq-to-SQL. , (, ).

Answer 3

, , , LINQ?

, . LINQ to SQL - - . LINQ to SQL , SQL; . , marc_s, ExecuteQuery .

LINQ to SQL ( ), 100% .

LINQ raw SQL ExecuteQuery.

I think it’s hard to believe if they don’t have a simple fear of learning something new. If they manage to shape themselves in LINQ (by reading books, blogs or technical articles, or through courses or mentoring), they will surely find it worth the effort.