Hi,
Just a suggestion, since ADO.Net is disconnected , it loads all of your retrieved records to your memory and that's where you tend to play with the data. You might say that ADO.Net is like a memory-resident mini database. And that is where the problem is. If your handling large sums of data and performing relationships in it, you tend to place the burden of sqlserver in your clients applicaiton. This action tends to slow down the performance of your apps.
So I suggest to just manually perform this operations using Command executions (SELECT statement everytime the record moves to emulate a child-parent view). In this scenario, not all of your data is being placed in your memory, thus removing the burden of over populating your datatable...
cheers
Paul June A. Domag
|