Unimark EC3000 Series Especificaciones Pagina 169

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 278
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 168
AIMS Attachment A: AIMS Statement of Work
Page 109 of 130
iii Provide original data values upon query when updated transaction
remains uncommitted
iv Utilize rollback methodology for uncommitted transactions
v Utilize record locking mechanisms to prevent simultaneous updates
to the same record. Only the record(s) being updated shall be
locked.
vi Provide support for both distributed processing and distributed
multiple databases along with standard DML operations, including
queries, inserts, updates, and deletes of remote table data
vii Provide support for automatic recovery from system or network
failures (i.e., automatically commits or rolls back any in-doubt
distributed transactions consistently on all involved nodes when a
failure occurs)
a Provide referential integrity for all data such that modifications to
current data does not affect historical data
b Provide capability of online “live” backup of all database objects
c Provide capability of “point of failure” recovery of all database
objects within one hour of the failure (i.e., dump transaction logs
hourly) with a native utility package.
5. Database Security: Third-party database and reporting tools shall
support database security functions. Database security shall include
the following items as a minimum:
i Encryption capability for defined data fields within database objects
such as tables or views
ii Prevention of unauthorized database access
iii Prevention of unauthorized access to schema objects
iv Control of system resource usage (such as CPU time)
v Auditing of user actions and database transactions
vi Assignment of valid username/password combinations
vii Assignment and control of resource limits for a user including
hardware, database and application resources
viii Control of user access rights including database, table, record and
field level authority
ix Control of which system functions a user can perform.
6. The CONTRACTOR shall submit all database schema(s) for review
and approval. The CONTRACTOR shall coordinate with the County,
airlines, and applicable third party vendors to identify unique database
requirements. The CONTRACTOR shall add needed fields as
Exhibit 3
Page 169 of 278
Vista de pagina 168
1 2 ... 164 165 166 167 168 169 170 171 172 173 174 ... 277 278

Comentarios a estos manuales

Sin comentarios