Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What’s wrong with Linq to SQL?
Or – what about Linq to SQL would make it unsuitable for a project, either new or existing? I want to hear about why you would not choose Linq to SQL for a particular project – including what project parameters make it unsuitable.
It is not very adaptable to changes in the database schema. You have to rebuild the dbml layer and regenerate your data contexts.
Like any ORM (I am not getting into the debate as to whether it is an ORM or not), you do have to be aware what SQL is being generated, and how that will influence your calls.
Inserts are not batched, so can be high cost in performance.
It’s being sunsetted in favour of Entity Framework
Despite the fact it is using a provider model that will allow providers to be built for other DBMS platforms, only SQL Server is supported.
[EDIT @ AugustLights – In my experience: ] Lazy loading may take a bit of hacking to get working.
That being said, I think it it is very handy if used correctly