Your mileage may vary, but almost *all* of our files are type 30's. Some of them grow and are purged annually as you suggest, for example G/L related files. *And* we have never.... resized them. Not ever. Never.
I don't really know why they never need to be resized, some of them have 100,000 records, some have 1000. Maybe they should be resized, maybe it's not efficient. All I know is we never do it. -----Original Message----- From: Scott Zachary <szach...@gardensalive.com> To: u2-users <u2-users@listserver.u2ug.org> Sent: Tue, Jul 9, 2013 9:15 am Subject: [U2] File type 30 (dynamic) I have very little experience with using dynamic (type 30) files and I'm looking for some pointers in that regard. I have a file that I am considering creating as a dynamic file. The file will be a log file with sequential numeric keys. The record size will normally range from about 200 to 700 bytes, with a probable maximum size of less than 1,000 bytes. We expect the file to continually grow without deletions and we will likely purge it annually. What are the pro's and con's of creating this file as type 30 verses other file types? Thanks, Scott Zachary UniVerse Developer Gardens Alive! Inc -- View this message in context: http://u2-universe-unidata.1073795.n5.nabble.com/File-type-30-dynamic-tp41129.html Sent from the U2 - Users mailing list archive at Nabble.com. _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
