Is it normal to use a data access layer using only SqlConnection SqlCommand and SqlDataReader

Question

I know there are a lot of ready-to-use things that you can use at the moment, but if you want to have complete control over your db requests / requests and the best performance, I think this is the way to go. Also, since ADO.NET automatically connects the connection pool for SqlConnection, what do you think?

Answer 1

If you need better performance, everything is fine. This gives you more control and better performance. By the way, here is an article on what you should consider that affects performance when using ADO.NET: How data access code affects database performance

Answer 2

That's right. If extreme performance is what you want, you cannot get much faster than that. I think that everything is in order.

In fact, now I am making a reporting system that uses SQL, DataReaders and SQLConnections, because it all started SQL. OLAP cubes are not the best candidates for OR cards.

Answer 3

SQL- , . . , , .

Answer 4

, . , , , , .

, . drag-and-drop , , , Dynamic Data .

Answer 5

, , , , ORM, , .

Answer 6

, , ! , , db-, / .

, , , SqlDataAdapters DataTables , .

Answer 7

. ADO.Net, , .