sorry if I am interfering between you two, though, yeah, Datasets are really disconnected stuff, but they still do need to get connected in a way, to the backend in order to get/fetch data from dbase. Ofcourse, for this we can use DataAdapters, by passing the dataset reference to the Fill method of it. If you are creating data on the fly, not fetching from backend, then we do need to get connected (Truely disconnected). What exactly means by disconnected, i feel is, we can have/maintain all the data in a dataset as it was in backend, like tables, constraints, relations etc. we can use and manipulate the data within the datasets in memory. No database access. And connection pooling, SQL Server will take care of pooling as long as the connecting parameters are same, like conn string. But still, we need to explicitly close the connections. IIS will not pool the database connections. Transaction can be done at different levels, like at Webmethod level or our individual database operations level. Here again, we need to take care of transactions. Any how, as Sreeram suggested, we should do it explicitly so that we can have a good control over it. hope its ok to you. burhan. |