Enable snapshot isolation for the Accountant by executing the following statements.

SET OPTION PUBLIC. allow_snapshot_isolation = 'On';
SET TEMPORARY OPTION isolation_level = 'snapshot';

In the Accountant window, enter the following statement to list all the departments.

SELECT * FROM Departments
ORDER BY DepartmentID;

The Sales Manager decides to set up a new department to focus on the foreign market. Philip Chin, who has EmployeeID 129, heads the new department.

INSERT INTO Departments
   ( DepartmentID, DepartmentName, DepartmentHeadID )
   VALUES( 600, 'Foreign Sales', 129 );
COMMIT;

The final statement creates the new entry for the new department. It appears as a new row at the bottom of the table in the Sales Manager's window.

SELECT * FROM Departments
ORDER BY DepartmentID;

The Accountant can execute his query again, and does not see the new row because the transaction has not ended.

SELECT *
FROM Departments
ORDER BY DepartmentID;

The Sales Manager would like to add a second department to handle sales initiative aimed at large corporate partners. Execute the following statement in the Sales Manager's window.

INSERT INTO Departments
 ( DepartmentID, DepartmentName, DepartmentHeadID )
   VALUES( 700, 'Major Account Sales', 902 );

The Sales Manager's change is not blocked because the Accountant is using snapshot isolation.

The Accountant must end his snapshot transaction to see the changes the Sales Manager committed to the database.

COMMIT;
   SELECT * FROM Departments
   ORDER BY DepartmentID;

Now the Accountant sees the Foreign Sales department, but not the Major Account Sales department.

To avoid changing the SQL Anywhere sample database, you should roll back the incomplete transaction that inserts the Major Account Sales department row and use a second transaction to delete the Foreign Sales department.