data binding - What is the .NET DataTable best usecase? -

I have three tables, customers, jobs, orders

I also keep these tables in a dataset I am in the database which is in line with their own similar obstacles.

Basically, I had to keep the data in the dataset, and the user had to create various databases to display this data, and also to make any necessary manipulations, which clearly Will be updated back to the database using NAT table adapters method.

However, it seems that the dataty objects are capable of operating on only one Sigal datatile object.

My question is: Which is the best way to create data in memory to ensure maintenance and performance.

1. Create multiple DataTable objects that contain denormalized data. This will probably make copies of the data in the memory, but I am more concerned that there are problems with updating the database on the changes.
2. Create some custom class, which expects dataweights to work, and is able to automatically update the dataset (and then database). Database with just the original dataset: You already have all the data and are separate- Creating separate data tables will be very difficult to monitor the changes in the data. .