Database Sessions

Each time a user does a SAVEWORK or module switch, a new session will be created for that user for each modified database. Sessions are numbered sequentially for each database. Each database is sessioned individually; for example, a SAVEWORK on databases TEAM1/DB1 and TEAM1/DB2 may create a new session number 106 for TEAM1/DB2 and session number 289 for TEAM1/DB2. If at the next SAVEWORK only TEAM1/DB1 has been modified then its session number will be incremented to 107, and that for TEAM1/DB2 will remain unchanged. The user name and current date are stored against each session. Optionally, in the GUI modules, the user can add a session comment.

In GUI modules, users can compare their current data with that at some previous session or date, and query the session in which given attributes and elements changed.

Session Numbering

For any database, Session 1 is when the database is created, and Session 2 is when the World is created. This means that the first user session is Session 3. The current session, before a SAVEWORK is done, is session 0.

Session Date and Time

The current date and time is the machine local date and time for the project. AVEVA products are switching to include both local date and time, and UTC (Coordinated Universal Time) session date and time. Refer to Enable UTC Session Dates for more information.