Hi you seem to be taking my words the wrong way let me clarify things for you.

Since I work as part of a team of developers, DBA's and designers, the DBA's deal with writing complicated sprocs or help us write them so we (developers) just focus on our application. Because of this I'm in the position to be able to avoid writing SQL, that's doesn't mean I don't know my way round the database it's just I prefer to write C# not SQL.

"why is it so complicated to write a loop without turning the database upside down? "

That was meant as sarcastic comment it's perfectly possible to write a loop it's just that it's not as easy as writing say one in C# eg.

myList.ForEach(x => x.Category == "Home");

Naz

The whole point of the articles on my site are to help people learn and share knowledge.

We are not all programming genius like yourself and if you know what SCOPE_IDENTITY() why are you even reading this article? it's not intended for you.

I erg people to continue and write articles no matter how basic and to not be put of by comments like xlar54's.

On my example I'm binding to a list view and I am requesting the data by doing Eval("CustomerLINQ.CustomerName") but it doesn't show me the actual generated SQL it's running which was my point.

What your saying the only way to see what LinqToSQL it's actually running is by using SQL Profiler.