The document discusses the pros and cons of connected vs disconnected data access in ADO.NET. It notes that disconnected access is generally simpler to design and scale but has limitations for large data volumes, custom aggregation, and performance-sensitive code. The document provides examples of when different connected and disconnected approaches such as cursors, data readers, and incremental loading are better suited. It concludes that while disconnected access is preferable by default, a balanced approach using both connected and disconnected pieces as needed works best.

1. DAT336 Connected vs Disconnected Data Access in ADO.NET Pablo Castro Program Manager – ADO.NET Team Microsoft Corporation

23. Attend a free chat or web cast http://www.microsoft.com/communities/chats/default.mspx http://www.microsoft.com/usa/webcasts/default.asp List of newsgroups http://communities2.microsoft.com/ communities/newsgroups/en-us/default.aspx MS Community Sites http://www.microsoft.com/communities/default.mspx Locate Local User Groups http://www.microsoft.com/communities/usergroups/default.mspx Community sites http://www.microsoft.com/communities/related/default.mspx

24. © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.