Database changes made by a transaction are invisible to other users until the transaction is committed. In a multi-user environment, where more than one transaction is open concurrently, this behavior maintains database consistency. If two transactions are writing to the same database tables, the DBMS lock manager makes one transaction wait until the other is finished. A transaction that writes to the database locks pages in the tables that are affected, thus enforcing database consistency.