Traditional client-server applications typically established a connection to a database when the program started up, maintaining the data link until the user exited the application. The introduction of ADO.NET and a drive toward multitier development challenged that always-on connection preference with their disconnected models. Yet even a fully disconnected, web-based, data-centric application might execute multiple queries and updates against a database during a single server-side page processing event. An important question in designing database applications is this: How long should the conne...
Share this highlighthttp://www.safaribooksonline.com/a/microsoft-adonet-4/31527/