I have inherited this .net 2.0 project with the previous developer used dataset designer heavily. There are about 40 datasets and some of them have more than 15 datatables inside, with some of the datatables have tableadapter with SQL statements here.
The program was developed in a way when a dataset is called, all the datatables will be populated, regardless if all the datatables will be used or not.
Clearly the app is suffering from performance issue.
I am thinking of relieving the performance problem without rewrite the whole damned thing...
Should I be breaking up each dataset; or should I fill individual datatable only when the data is required, and then disconnect the connection after each call?
The project will eventually be moved up to 3.5 (not sure would be easy for .net 4.x). Do .net 3.5 datasets/datatables perform better than 2.0?
Thanks in advance. W
Go to the complete details ...