Zim Thin Client

ZimQTC Client provides remote client access to Zim database and application servers and all critical data resides on the server, dramatically improving security and performance.

With all data residing on a centralized server, administration and management of Zim applications and data is made easier saving time and money. Deploying applications is easier, since all licensing is managed on the server and there are no product activations required on the client.

Advanced Zim Lock and Data Management

Integrated into Zim Server, our Advanced Lock and Data Management provide multi-threaded lock and data management controls and operating system- independent lock management. Automatic and immediate deadlock detection is associated to a ‘pending list’ where lock requests are serialized and prioritized. As lock requests are serialized, it eliminates the need to swap out and involve Lock Manager when a lock is granted.

The redesigned internal transaction execution dramatically reduces deadlock occurrences and Time Limits controls how long a lock request can remain on the ‘pending list’.

Lock request priority lists are applied the oldest lock requests first so the older the pending request, the higher its priority in the queue. Once committed to disk, changes are kept in the shared memory, increasing the number of supported users and making database changes immediately available to other processes. All transactions are exclusively and centrally controlled by the Data Manager within Zim Server.

Individual checkpoint threads apply the transaction log to the database while users continue processing. The result – no more waiting for database to be updated before users can write new changes!

Online Backup

Zim 9.00’s Online Backup automatically generates a mirror database. This dramatically improves your database integrity and recovery while minimizing downtime after a system crash or human error.

The “mirror database” is always ready for queries, even during “main database” normal operation. In the event of a crash, all committed transactions up to the last checkpoint are already available in the backup database. Users simply switch over to the mirror database and continue work.

To download the mirror database to a tape, online backup is suspended during the process. Once resumed, all pending committed transactions are applied to the mirror, bringing it to the current main database status.

Server Side Sequence Numbers Eliminate Lock Competition

Sequence numbers are assigned by the server, ensuring files can remain open and are only updated at checkpoints. This effectively eliminates lock competition between Zim 9.00 instances that use sequence numbers.