Reflecting database changes

By: Ben Matterson

Abstract: Chnages to a database are not always immediately seen by other users.

Problem

When a user posts a record, other users cannot see that record unless the database is closed and opened again.

Solution

All changes made to the database must be committed before the changes can be visible to others. When another user actually sees the committed changes depends on the transaction isolation level they are using. If another user is using snapshot isolation he/she will not see the change until he/she commits and starts a new transaction. If he/she is using read committed isolation he/she will see the change the nest time he/she selects the changed record.

Server Response from: ETNASC04