Re: Is there a limit to how many table you can have in a dataset?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: moondaddy (moondaddy_at_nospam.com)
Date: 02/22/05 

Date: Tue, 22 Feb 2005 16:05:12 -0600

Thanks for the feedback. yes, we're using a little less then 2 billion
tables and I recognize that it does take longer to instantiate a dataset in
the designer, but haven't noticed any difference at run time. Also, there's
not tones of users hitting the server at any given time where lots of these
datasets would be created at one time. So I guess its a matter of whether
its really a performance issue vs. convenience. Strongly typed datasets
sure are a nice way to package multiple blocks of data for marshaling. I
appreciate your comments 

-- 
moondaddy@nospam.com
"Sahil Malik" <contactmethrumyblog@nospam.com> wrote in message 
news:e9EncmlFFHA.3312@TK2MSFTNGP15.phx.gbl...
> The limit is 2 billionish - whatever the highest number is on Int32 - you 
> will probably run out of memory way before that.
>
> Try not to send TOO MUCH data using a webservice, and try not to hold TOO 
> MUCH data in a dataset.
>
> Logical question - what is TOO MUCH? - Thats subjective and depends on a 
> lot of uses - just remember - a dataset is not a database :)
>
> One good reason NOT to specify 50 tables in a dataset schema - assuming 
> when you say schema you mean the XSD that generates the strongly typed 
> dataset, is the insanely complex code and super insanely complex 
> constructor alongwith all the event hooking it will have to do; everytime 
> the dataset is instantiated.
>
> You might want to look into a custom business object for this purpose IMO.
>
> - Sahil Malik
> http://codebetter.com/blogs/sahil.malik/
>
>
> "moondaddy" <moondaddy@nospam.com> wrote in message 
> news:eOsgaTkFFHA.3336@TK2MSFTNGP10.phx.gbl...
>> Is there a limit to how many tables you can have in a dataset?  I have a 
>> situation where it would really be advantageous to use one main dataset 
>> to marshal various tables via a web service.  the problem is that we have 
>> a group of about 50 tables that are all very closely related and we 
>> usually need to send or receive about 1 to 3 tables at a time, but it can 
>> be any combination of the 50 tables.  if we break them down into smaller 
>> datasets (logical groupings of tables) then we will have to retrieve 
>> multiple datasets which would require several  round trips or serializing 
>> them all into a blob and parsing them out on the other side (messy).  So, 
>> is there any good reason why having 50 or so tables in a dataset schema 
>> would be a bad idea?
>>
>> Thanks
>>
>> -- 
>> moondaddy@nospam.com
>>
>
>

Relevant Pages

  • Re: Is there a limit to how many table you can have in a dataset?
    ... Logical question - what is TOO MUCH? ... One good reason NOT to specify 50 tables in a dataset schema - assuming when ... is the insanely complex code and super insanely complex constructor ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Declare an object as its parent class?
    ... > Is there any reason to declare an object as its Parent or Grandparent ... then instantiate it as the intended class? ... then instantiate as its own object. ...
    (comp.lang.java.programmer)
  • Re: Can we create an_object = object() and add attribute like for a class?
    ... Is there any reason that under Python you cannot instantiate the object ... I was under the impresssion that instances of type object did have a __dict__ but was hidden for some reason. ... which may make little sense for a namespace). ... any natural way of declaring a namespace SHOULD allow ...
    (comp.lang.python)
  • Re: Can I use an increment >1 when vectoring components in Composer?
    ... >I'd like to instantiate a cell as follows: ... >Composer doesn't seem to allow this for no reason that I can fathom. ... Is this just a shortcoming of Composer? ... There are a lot of things in the net naming syntax which would make no sense ...
    (comp.cad.cadence)
  • Re: Generics question
    ... I assume its made abstract to prevent fools like me trying to instantiate it, or is there some other reason? ... Langer explains that Enum can only be instantiated for its ...
    (comp.lang.java.help)