P
Piotr Ryszkiewicz
Guest
>> RECORD-LENGTH of template record is 236 >Are you sure? Dbanalys says that min record size is 210 bytes. And it was a database after load - hence the schema versioning is not applied here. The size reported by dbanalys is 2 bytes higher than the value returned by RECORD-LENGTH() function. It means that your table has at least one record with RECORD-LENGTH 208 bytes. I did not run your program yet, just checked it with this code: find first _file where _file-name = "old_trans". find first old_trans where recid(old_trans) = _file._template no-lock. disp record-length(old_trans). I suppose it's correct ? >> there is one field which takes about 1/4 of record size >I expected the bigger contribution. How large was the record or field? Max record size is 1667 bytes. I'd check the records with 1K size or larger. That was for records with average size, now I found some bigger than 1000 bytes it's more - 1/3 to 1/2. > That means, that during normal production when newly created record is allocated it takes at least 236 bytes, even if it's not filled yet, right ? If average record size is around 400, that means it will afterwards grow by around 170 bytes. That means create limit should be at least 170, am I right ? Most likely you're right. But I would also check _TableStat. Namely the ratio of _Table-create to _Table-update. If it's 1:1 with high presision then you're 100% right. Or check the slots used by the fragmented records in your production database (it's reported by AreaDefrag). I guess you will see the slots 15, 16 or so and no slots with low numbers. I will try AreaDefrag next week. I will have to prepare fragmented database again. Now I am playing with proper toss and create limits, so the database is supposed to not be fragmented so much. But I can run report on that one as well. Unfortunately I don't have enough space to keep more than one copy. Regards, Piotr
Continue reading...
Continue reading...