I have a set of stored procedures that perform complex selects based on multiple tables (between 3 and 8 ) with various join strategies.

Is it worth the time investment to convert all these to LinqToLlbl?

Is LinqToLlbl performant in more complex scenarios?

What is the cutoff to switch to LinqToLlbl from stored procs and the vice versa?

Thank you,

Val

The answer, as ever is of course "It depends". It can depend on many things, such as the volume of data being process, calculations done, join strategies chosen by the query optimizer, and a whole host of other things.

The only real answer in the scenario is to try it out for your self, and run some profiling to see how they compare side by side.

Matt