Join / Log in
Very important to to mess with is the first extent, because you cannot change this size. The size of the next extent is also important to avoid having a high number of extents over time, but you can modify it anytime: the new value will apply for the next newly created extent, so the impact of giving it a size is not so critical as it can be modified anytime.
If your customer is insisting on not giving you a growth forecast, apply 10% of first extent size to the next size and monitor with sysmaster over time.
If you see the table has 30 extents in one week, next size is way too low and needs to be increased.
This query will help
select dbsname,tabname,min(size) as min,sum(size) as sum,count(*) as count from sysmaster:sysextents where dbsname not matches "sys*"group by 1,2;
And I would add: NEVER count on storage pool to get rid of this calculation (which is fun and a first-do exercise thing for IDS beginners).If you let the Storage Pool manage the growth of your table, you will probably end your first load with TONS of extents. This happened to one of my customer who was happy to be a bit lazy.Laziness pays sometimes, but not in all cases ��
Eric VercellettoData Management Architect and Owner / Begooden IT ConsultingBoard of Directors, International Informix Users groupIBM Champion 2013,2014,2015,2016,2017,2018,2019,2020
Tel: +33(0) 298 51 3210Mob : +33(0)626 52 50 68skype: begooden-itGoogle Hangout: email@example.comEmail: firstname.lastname@example.org : http://www.vercelletto.comwww https://kandooerp.org
isn't the slot table entry 4 bytes per row ?
Amitif you go to my personal website, you'll see links to both spreadsheets and worksheets that walk you through table sizing. They include page size implications as well as used and wasted space calculations.
IT27997: BFCHECK BAD PAGE PG_FRPTR <SIZE> < SIZEOF(IFX_PAGE_T) 24 OR > SLOTBEG <SIZE> WHEN UPDATING PAGE WITH OUTSTANDING IN PLACE ALTERS