AuthMinder 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 will cause the tables to grow. Because of restricted disk space, as a database administrator managing AuthMinder deployments, you might 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.
You must only trim the tables that capture transaction details, such as audit log information. You must not trim tables that capture user information, which is necessary to authenticate users.
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 will adversely impact performance during the delete process. Depending on the size of the rollback segments, this may even cause the system to fail. It is also highly recommended that you archive older records and not delete them completely.
This appendix discusses the recommendations on database table replication, how to calculate the database size while you are planning to set up the database for AuthMinder, and lists all tables used by AuthMinder along with some trimming recommendations:
|
Copyright © 2013 CA.
All rights reserved.
|
|