software design
Home » computers » computer science » software design » pragmatic ado net data access for the internet wo
|
Aftersleep Books
|
||||||||||||||||||||
Pragmatic ADO NET Data Access for the Internet WoThe following report compares books using the SERCount Rating (base on the result count from the search engine). |
|||||||||||||||||||||
|
Aftersleep Books - 2005-06-20 07:00:00 | © Copyright 2004 - www.aftersleep.com () | sitemap | top |
This was my second ADO.NET book. After I read (and in fact reviewed) an excellent Bob Beauchemin's "Essential ADO.NET", I thought I wouldn't need another ADO.NET book. But actually I did. There are plenty of ways to solve a database task using .NET, and Shawn Wildermuth carefully guides you through alternatives, not only identifying the best approach but also explaining his reasoning. Here is a brief example: data scalability (chapter 11). Shawn explains different caching scenarios (per user, per application, per server), its drawbacks, discusses how to scale out a DataSet, and if you should duplication or segmentation. Then he gives the following advices (again, with explanations):
1. Use DataSet schema
2. User typed DataSets to create business rule layers
3. Reduce roundtrips to the database
4. Cache data early and often
5. Use the DataReader
6. Use connection factories
7. Do not hard code connection strings
This is just one example of in how this book can help .NET database developer. It helped to get cleaner understanding of .NET database interfaces and its best use.