Typed DataSet

[Mythran]

Which would be the better solution?

1.) 20 Tables In 1 DataSet, no relationships.

2.) 20 DataSet's with 1 Table each.

The tables have no relationship with each other (although they represent data
retrieved from normalized databases, they are normalized themselves.

Basically, if I have 20 tables in a single typed dataset, and I create the
DataSet, does it create the 20 tables when I just want to use one or two? That
would be quite some overhead, but not too bad being that they wouldn't be
populated, nonetheless, un-needed overhead.

Another question would be, if I create a typed DataTable object from that same
DataSet w/o creating the DataSet (bah, haven't checked to see if typed DataTables
have default constructor)...would it then create the other 19 tables?


Thanks,

Mythran
Disgruntled Programmer Analyst

 

[Guest]

If you use Microsoft ApplicationBlocks it has a nifty little function called ExecuteDataset. If you create an SP with 20 selects you can use this function and it will return a DataSet populated with 20 tables. Load all 20 tables in one line.

Then you could access the tables as an array if you ever needed to.

 

[Cor]

Hi Mytrhan,

I think the answer is very simple with dataset.

Think always that you are doing it on the Internet with a small bandwidth

When the user needs all 20 tables in the same time.
Mostly strange but than you can go for one dataset.

When the user needs them one by one.
In my opinion 20 datasets.

I hope this helps,

Cor