S
Scott M.
As I start learning LINQ (and say to myself it's about time they came up
with a simple way to do querying of various data models) I am forced to
wonder, with the new classes in LINQ to SQL in particular, if there is any
performance impact of using things like DataContexts and tables, rather than
the traditional Connection, Command, DataSet classes.
I know that these LINQ classes map to the ADO .NET classes, but is there any
additional overhead to using them?
Also, since Strongly-Typed datasets used to be the way to go as a best
practice, does LINQ (and its table classes) make them obsolete for certain
purposes?
Thanks,
Scott
with a simple way to do querying of various data models) I am forced to
wonder, with the new classes in LINQ to SQL in particular, if there is any
performance impact of using things like DataContexts and tables, rather than
the traditional Connection, Command, DataSet classes.
I know that these LINQ classes map to the ADO .NET classes, but is there any
additional overhead to using them?
Also, since Strongly-Typed datasets used to be the way to go as a best
practice, does LINQ (and its table classes) make them obsolete for certain
purposes?
Thanks,
Scott