The RiskMinder database contains a number of tables, some of which grow with increased usage. Some tables grow in direct relation to the number of users, while others grow in direct relation to the usage of the product. Also, a user accessing the system multiple times causes the tables to grow. Because of restricted disk space, as a database administrator managing the RiskMinder deployments, you may not want these tables to grow indefinitely. In this case, you can use the information in this appendix to trim some tables to manage your disk space and improve the database performance.
Trim only the tables that capture transaction details, such as audit log information. Do not trim tables that capture user information, which is necessary to assess the risk evaluation.
Note: It is recommended that you make appropriate adjustments to the SQL databases based on the configuration and the need for reporting data. For example, deleting a large volume of data adversely impacts performance during the delete process. Depending on the size of the rollback segments, this deletion may even cause the system to fail. It is also strongly recommended that you archive older records and not delete them completely.
This section discusses the recommendations on database table replication, how to calculate the database size while you are planning to set up the database for RiskMinder, and lists all tables used by RiskMinder, with some trimming recommendations:
|
Copyright © 2013 CA.
All rights reserved.
|
|