Deadlocks A deadlock condition occurs when two users have to wait for each other in order to complete their respective transactions. For example, one user’s transaction needs records currently being used by a transaction started by another user. The second user’s transaction in turn requires records that the first user’s transaction is holding (while it…
Read more
A well-designed database application is of no use if data and the application are not available 100% of the time. Data loss and corruption are not common in most systems, but occasional occurrences are unavoidable. Some of the events that can cause data loss include the following: Event Description User error Individual records, or even…
Read more
Because Zim 9 always operates in the client/server mode, memory operations performed by the client are not affected by what is being done in the server and vice-versa. When running Zim on Windows in the client side, the local machine is dedicated to the client session; therefore, all resources available can be used solely for…
Read more
If the contents of all files that an application requires at any given time could be stored in memory, response time would be very rapid. Using main memory is much quicker than using disk input/output (I/O) because the time required to access files from disk is much greater than that required to access them from…
Read more
When considering the performance of an application, individual users have different criteria in mind. To some, performance is the speed at which an application responds to the requests of an application user. To others, it is the ability of the application to run properly within the limits set by the hardware or operating system. Performance…
Read more
English 
Portuguese