Last post Apr 30, 2015 02:25 AM by Mikesdotnetting
Apr 23, 2015 07:03 AM|rpk2006|LINK
Which is preferable with Visual Studio 2013:
Entity Framework, or
Someone suggested me to use Enterprise Library because it is light-weight. Also, Entity Framework becomes a headache when data grows.
Please let me know which one to opt.
Apr 23, 2015 08:12 AM|Mikesdotnetting|LINK
They are not the same thing. Enterprise Framework is an ORM, whereas Enterprise Library (DAAB) is just a set of ADO.NET wrappers.
Entity Framework becomes a headache when data grows.
Apr 30, 2015 02:11 AM|rpk2006|LINK
Is Entity Framework suitable for large databases with around 3000 tables?
What are the pros and cons if I simply use ADO.NET instead of EF and Enterprise Library?
Apr 30, 2015 02:25 AM|Mikesdotnetting|LINK
See here for a start: https://msdn.microsoft.com/en-us/library/vstudio/cc853327(v=vs.100).aspx
Search for 'entity framework large database performance' for more articles but note that a lot were written a whiel ago about older versions of EF. LAter versions have seen significant performance improvements in a number of areas.
Ultimately, it will be a case of you testing your scenario. The
EF Power Tools package makes it easy to generate a domain model from an existing database so you can get testing quite quickly.