IBM P2090-018 Dumps

Users with DATAACCESS authority are exempt from the Row and Column Access Control rules.

Table data is protected against direct access to the table. Access using views is unrestricted.

In order to take advantage of this feature, applications must be changed to work with the RCAC feature.

Row and column level access control allows the creation of column masks that can control what column values a user is permitted to see.

You can use storage groups to implement multi-temperature data management in DB2.

Multi-temperature data management reduces the total cost of ownership by allowing efficient deployment of storage hardware with minimal administrative overhead.

Multi-temperature data management integrates with DB2's Workload Manager feature to let you prioritize your workloads based on the data being accessed.

Multi-temperature data management best practices recommend that cold data should be stored in faster devices in order to maximize overall system performance.

DB2 LBAC allows you to use labels to reference database objects by a short name instead of the full qualified name.

DB2 LBAC lets you decide exactly who has write/read access to individual rows and columns by comparing the security labels between database objects and users.

DB2 LBAC monitors table data access and tables modifications made by database users.

DB2 LBAC is the DB2 authority in charge of issuing GRANT and REVOKE statements.

Table partitioning allows you to make smaller tables automatically from large tables, thereby increasing the performance of your DB2 database.

Table partitioning allows you to create very large tables that are divided across multiple storage objects so that you can quickly attach and detach large quantities of data from the tables.

Table partitioning allows you to create result set tables from a join query, which automatically splits the data into smaller chunks, thereby increasing the performance of your DB2 database.

Table partitioning allows you to partition the table data based on the hash values of the primary key.

In both DB2 pureScale and HADR environments data is available all the time.

DB2 pureScale transfers log files from a primary database to a standby database.

HADR persists data in the cluster caching facilities (CFs).

In a pureScale environment, the data is available all the time, while in a HADR environment the data is available most of the time.