问题描述
我们刚刚启动了一个项目，开发使用.NET 3.5和MSSQL 2008。有人问这是明智的选择，以处理涉及的记录几万至几十万数据访问的门户网站？我在某处看到了一个表，相比ADO.NET，EF和LINQ to SQL，它似乎像的LINQ to SQL是最笨的平均水平，但ADO.NET哽咽的大规模行动。
We just started on a project to develop a web portal using .NET 3.5 and MSSQL 2008. A question was raised on which is the sensible choice to handle data access which involves tens of thousands of records up to hundreds of thousands? I saw a table somewhere that compared ADO.NET, EF and LINQ to SQL and it seemed like LINQ to SQL is the slowest by average but ADO.NET choked on large operations.
顺便说一句，什么是使用NHibernate的大规模您的想法？
By the way, what are your thoughts on using NHibernate on a large scale?
推荐答案
一切都将使用ADO.NET，当它归结到它。
Everything is going to use ADO.NET when it boils down to it.
使用（使用实体框架，另一个使用ADO.NET原料与一个存储库）存储库模式我可能会写的概念应用程序中的证明。
I would probably write a Proof of Concept app using the Repository pattern (with one repository using Entity Framework and the other using raw ADO.NET).
运行一些测试，看看哪种方法更适合您的需求。
Run some tests and see which method suits your needs better.
我会告诉你，用香草ADO.NET会给你在什么实际上正在对数据库执行的更细粒度的控制。
I will tell you that using vanilla ADO.NET will give you finer grain control over what is actually being executed against your database.
这篇关于经典的ADO.NET或实体框架进行较大规模的数据库事务更好？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！