LINQ Disadvantages
-
Can Any One expain the dis advantaged of LINQ,like where i Can use and where I can not... Thanks, Srinivas Mateti
Disadvantages of LINQ over Stored Procedures ----------------------------------------------- 1) Network traffic: sprocs need only serialize sproc-name and argument data over the wire while LINQ sends the entire query. This can get really bad if the queries are very complex. However, LINQ's abstraction allows Microsoft to improve this over time. 2) Less flexible: Sprocs can take full advantage of a database's featureset. LINQ tends to be more generic in it's support. This is common in any kind of language abstraction (e.g. C# vs assembler). 3) Recompiling: If you need to make changes to the way you do data access, you need to recompile, version, and redeploy your assembly. Sprocs can sometimes allow a DBA to tune the data access routine without a need to redeploy anything.
-
Can Any One expain the dis advantaged of LINQ,like where i Can use and where I can not... Thanks, Srinivas Mateti
sris 426 wrote:
Can Any One expain the dis advantaged of LINQ
In ASP.Net Forum? :omg: I would have chosen LINQ [^]forum forum for that
Manas Bhardwaj Please remember to rate helpful or unhelpful answers, it lets us and people reading the forums know if our answers are any good.
-
Disadvantages of LINQ over Stored Procedures ----------------------------------------------- 1) Network traffic: sprocs need only serialize sproc-name and argument data over the wire while LINQ sends the entire query. This can get really bad if the queries are very complex. However, LINQ's abstraction allows Microsoft to improve this over time. 2) Less flexible: Sprocs can take full advantage of a database's featureset. LINQ tends to be more generic in it's support. This is common in any kind of language abstraction (e.g. C# vs assembler). 3) Recompiling: If you need to make changes to the way you do data access, you need to recompile, version, and redeploy your assembly. Sprocs can sometimes allow a DBA to tune the data access routine without a need to redeploy anything.
S.Dhanasekaran wrote:
Disadvantages of LINQ over Stored Procedures
How a comparison is possible between LINQ and Stored Procedures?
Navaneeth How to use google | Ask smart questions
-
Can Any One expain the dis advantaged of LINQ,like where i Can use and where I can not... Thanks, Srinivas Mateti
I dont want my Data Layer to Contain SQL Manupilation. Linq does that. I like Linq to Object. Am not a Fan of Linq to SQL
Vuyiswa Maseko, Few companies that installed computers to reduce the employment of clerks have realized their expectations.... They now need more and more expensive clerks even though they call them "Developers" or "Programmers." C#/VB.NET/ASP.NET/SQL7/2000/2005/2008 http://www.vuyiswamaseko.com vuyiswa@its.co.za http://www.itsabacus.co.za/itsabacus/
-
I dont want my Data Layer to Contain SQL Manupilation. Linq does that. I like Linq to Object. Am not a Fan of Linq to SQL
Vuyiswa Maseko, Few companies that installed computers to reduce the employment of clerks have realized their expectations.... They now need more and more expensive clerks even though they call them "Developers" or "Programmers." C#/VB.NET/ASP.NET/SQL7/2000/2005/2008 http://www.vuyiswamaseko.com vuyiswa@its.co.za http://www.itsabacus.co.za/itsabacus/
-
I dont want my Data Layer to Contain SQL Manupilation. Linq does that. I like Linq to Object. Am not a Fan of Linq to SQL
Vuyiswa Maseko, Few companies that installed computers to reduce the employment of clerks have realized their expectations.... They now need more and more expensive clerks even though they call them "Developers" or "Programmers." C#/VB.NET/ASP.NET/SQL7/2000/2005/2008 http://www.vuyiswamaseko.com vuyiswa@its.co.za http://www.itsabacus.co.za/itsabacus/
Vuyiswa Maseko wrote:
I dont want my Data Layer to Contain SQL Manupilation.
So what does your data layer contain?
only two letters away from being an asset
-
What About LINQ to XML and other options? I am using linq to load and process XML file? Will it give any extra burden to Application. Please advise..... Thanks in advance Srinivas Mateti
Anyhow, you are somewhat comparing apples and oranges. LINQ to XML (and LINQ in general) is a query language whereas XSLT is a programming language to transform XML tree structures. These are different concepts. You would use a query language whenever you want to extract a certain specific piece of information from a data source to do whatever you need to do with it (be it to set fields in a C# object). A transformation, in contrast, would be useful to convert one XML representation of your data into another XML representation. So if your aim is to create C# objects from XML, you probably don't want to use XSLT but any of the other technologies offered by the .NET Framework to process XML data: the old XmlDocument, XmlReader, XPathDocument, XmlSerializer or XDocument. Each has it's special advantages and disadvantages, depending on input size, input complexity, desired output etc.
-
Vuyiswa Maseko wrote:
I dont want my Data Layer to Contain SQL Manupilation.
So what does your data layer contain?
only two letters away from being an asset
In my Data Layer i call the SP that does the Necessary manupilation. What i mean is that you will never Find select statements in my Data Layer.
Vuyiswa Maseko, Few companies that installed computers to reduce the employment of clerks have realized their expectations.... They now need more and more expensive clerks even though they call them "Developers" or "Programmers." C#/VB.NET/ASP.NET/SQL7/2000/2005/2008 http://www.vuyiswamaseko.com vuyiswa@its.co.za http://www.itsabacus.co.za/itsabacus/