Re: LINQ Queries vs Stored Procs
- From: Michael Nemtsev [MVP] <nemtsev@xxxxxxx>
- Date: Wed, 2 Jan 2008 12:16:59 +0000 (UTC)
Hello Frank,
adding to other posts, I'd recommend to consider between LINQ vs SP in the aspect of changability.
SP logic changed easily without any code chages (if params are not changed) and your can tune your queries easily.
for example today u have 100 rows, tomorrow 100 mils rows, in case of LINQ there are few steps for optimizing, in terms of SP you can apply partitioning, sectioned indexing and etc to improve your data selection
---
WBR, Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it" (c) Michelangelo
FC> I've been looking at LINQ and it seems very nice to be able to make
FC> queries in code, but I use stored procs for efficiency. If LINQ to
FC> SQL only works with SQL Server and stored procs are more efficient,
FC> what use is LINQ to SQL, other than to have a simpler way to call my
FC> stored proc?
FC>
.
- References:
- LINQ Queries vs Stored Procs
- From: Frank Calahan
- LINQ Queries vs Stored Procs
- Prev by Date: Adding data columns to a disconnected database
- Next by Date: Re: make entire exe private
- Previous by thread: Re: LINQ Queries vs Stored Procs
- Next by thread: Re: LINQ Queries vs Stored Procs
- Index(es):
Relevant Pages
|
