Table Presize (OpenInsight 32-Bit)
At 04 APR 2004 09:13:58PM Karl Pozmann wrote:
Having seen the brochure "You and offshore programming" on one of my client's desks, I thought it might be a good time to dust off an app or two we had tabled earlier. Its also an exercise I do everytime I renew my subscription.
I thought I might modify the "Number of records" parameter in order to presize a table properly because the original table would contain about 250,000 records that would be imported. 400 bytes/records would be about as good a guess as any. I would imagine OI would resize it properly during the import but I would also think that would slow things down. But when I did that, I got a message "The size of the table is too large. Please reenter Estimated Data Size."
Now, if I were someone new to the MV world, I might get worried. Is there another way to presize a table? Searching here reminded me about using "RemakeTable" in Arev but it's not in OI.
Whatever the solution may be, I think that more than 250,000 records should be able to be entered in "Estimated Data Size", or don't make that parameter edittable. Experienced this in both 4.1.3 and 7.0.
At 05 APR 2004 07:46AM Mike Ruane wrote:
Karl-
Found this in the code- it's a hardcoded limit to make sure a file didn't exceed the 4gig limit, a limit exceeded with the Universal Driver.
I'll modify this to see if you are using a UD and allow an appropriate size.
Thanks
At 05 APR 2004 09:00AM Donald Bakke wrote:
Mike,
Found this in the code- it's a hardcoded limit to make sure a file didn't exceed the 4gig limit, a limit exceeded with the Universal Driver. I'll modify this to see if you are using a UD and allow an appropriate size.
This is what I guessed was going on, but how does the math work? I mean, 250000 records at 400 bytes each seems hardly close to 4GB. Also, it appears that this is hard-coded in the DM and not CREATE_TABLE, correct?
dbakke@srpcs.com
At 05 APR 2004 09:32AM Mike Ruane wrote:
Correct, hardcoded in the TB New Tablew window.
At 05 APR 2004 06:49PM Chris Callaghan wrote:
Mike
Wouldn't you need to check the header of ths file as well to see if it was created with the Universal Driver rather than just using it - so the file can actually exceed the 4GB limit?