I love Linq to SQL for the queries, but it is an absolute dog when doing inserts or updates of very large transaction sets. For example, my application requires doing about 60,000 inserts as a single transaction. Using SqlCommand it takes 20 seconds. Using Linq to SQL it takes 200 seconds. I believe that because of all the checking for Foreign Key integrity it actually grows exponentially as new items are added to the transaction. As for Entity Framework, I am also using VS 2008 and would not want to use Entity Framework until VS 2010 which has a more stable and mature product than the one with VS 2008. Also since ADO gives me so much better performance for my very large transaction set, I don't think the time taken to set up an experiment with Entity Framework is worth the effort. Robert Tanenbaum
