| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| fgiuser.c | 2020-05-11 | 1.1 kB | |
| mk_runner | 2020-05-11 | 39 Bytes | |
| readme.txt | 2020-05-11 | 3.9 kB | |
| tblusage.4gl | 2020-05-11 | 17.7 kB | |
| tbstat.c | 2020-05-11 | 2.5 kB | |
| Totals: 5 Items | 25.3 kB | 0 | |
Newsgroups: comp.databases.informix
Subject: Space each table occupies
From: rovkg426@glen-ellyn.iit.edu (VINAY GIDWANI)
Date: 23 Jun 1995 17:53:11 GMT
Is there a informix utility which can let me know the space each table
occupies?
Also from what I understand, in a table there may be some spaces which are
blank. Is it possible to know how much of the space of the table has
actual data.
Thanks
Vinay.
From: cwakins@leia.alloys.rmc.com (Clem Akins)
Date: 26 Jun 1995 15:08:05 -0400
You can use "tbcheck -cI -pI dbname > filename" to print a report of space
usage by table. The interesting things for you are the "number of pages
used, allocated" rows. RTFM about this command, there are lots of options.
A pet peeve of mine is how people worry about reclaiming "unused space".
IMHO, a table should occupy a fairly stable space, fluctuating between
purge cycles. These cycles should be defined and planned for at the
onset of the project, not added in at year-end by the new DBA whose first
job is to get the database back up from its "unable to allocate next
extent" error. Whew!
__________________________________________________________________
| Clem Akins Standard Disclaimers Apply |
|Reynolds Metals Co, Alloys Plant "Climb High, Cave Deep!" |
| Muscle Shoals, Alabama USA cwakins@leia.alloys.rmc.com |
|________________________________________________________________|
From: melin@hermes1.sps.mot.com (Darin Melin)
Date: 26 Jun 1995 17:53:03 -0400
I had received an application from informix pertaining to determining
the table spaces allocated and sizing. The code is listed below:
+----------------------------------------------------------------------------+
| | |
| . . | |
| ... ... | Darin Melin |
| ..... ..... | Software Engineer, DBA |
| .. ... .. | Business Systems Integration Group |
| . . . | Semiconductor Products Sector - LATG |
| | 2200 West Broadway Road, MD M300 |
| | Mesa, AZ 85202 |
| Motorola, Inc. | rp29560@email.sps.mot.com Phone:(602) 655-3627 |
| | melin@hermes1.sps.mot.com FAX: (602) 655-2820 |
| | Director - Arizona Informix Users Group |
+----------------------------------------------------------------------------+
| 'connectionLESS IS MORE' -- Data Broker |
+----------------------------------------------------------------------------+
TBLUSAGE DOCUMENTATION
Consists of 3 files:
FILENAME DESC
-------- ----
mk_runner Builder for making the fglgo executable
tblusage.4gl Source code for tblusage program
fgiusr.c Source code for making the 4gl runner
tbstat.c Source code for reading "tbstat" data
Build notes
-----------
There is one change required within the source code. The "tblusage.4gl"
program uses a variable "LET G_PAGE_SIZE". Set this to your system
default page size (ie Sun 4.1.3 = 2048).
!!!! FAILURE TO SET THIS CORRECTLY WILL RESULT IN ERRONEOUS REPORTS !!!!
Interpreted Build Instructions
------------------------------
1- Execute the mk_runner shell script
2- Use R4GL and compile the "tblusage.4gl" file as runable.
C-Compile Build Instructions
------------------------------
1- Compile the "tblusage.4gl" file as runable and link in tbstat.c.
Running Instructions
--------------------
RDS (r4gl): ./fglgo tblusage.4gi <dbname> KB
C-Compiled (i4gl) : ./tblusage.4gi <dbname> KB
Source Code
----------