Get users to commit their current transactions periodically, and allow the write server to drop old table versions to free disk blocks. Specifying the auto_commit option helps minimize space due to minimize version buildup.
SAP Sybase IQ cannot drop old versions of tables while any user on any server might be in a transaction that might need the old versions. SAP Sybase IQ may therefore consume a very large amount of disk space when table updates and queries occur simultaneously in a multiplex database. The amount of space consumed depends on the nature of the data and indexes and the update rate.
You can free disk blocks by allowing the write server to drop obsolete versions no longer required by queries. All users on all servers should commit their current transactions periodically to allow recovery of old table versions. The servers may stay up and are fully available. The sp_iqversionuse stored procedure can be used to display version usage for remote servers.