OpenText: Guidance for Administrators
Contributed by Steve Simpson
Optimizing your database is the key to good performance. OpenText libraries are created with generic performance parameters to support the basic document and record creation for an average customer site. Indexes created on the database by Library Generator benefit when clients tune them to their environment.
As the volume of data grows in your eDOCS system, a decrease in performance may appear. This can be resolved with database optimization.
Basic Items for Database optimization
The following are the general issues that can be optimized.
- Location of data files and log files.
- Placing index files on separate physical drives from the table files can significantly improve performance
- Predefine file space
- This saves SQL Server needing to initialize and expand files while in production
- Periodic Maintenance
- Doing appropriate and regular backups, see
- Rebuilding indexes
- Updating statistics
One critical issue is learning to use SQL Server Profiler and SQL Server Database Tuning Advisor. The basics of doing this are covered at:
- Creating a Workload by Using a Trace Log
- Running Database Engine Tuning Advisor and Selecting Indexes
Best Practices
The following should be a part of your regular activities:
- Checking Windows Events Viewer
- Errors should always be examined.
- Checking the DM Server Logging when performance is not acceptable
- Check for “Error” in the log
Summary
For more information and some TSQL Scripts to assist with the above, see Steve's presentation “OpenText eDOCS DM 5.3 - Technical Architecture, Tips and Tricks”, and look for future visual step-by-steps on this blog.