It does not matter to a user why his or her database request failed. The steps required to maximize performance given in the below article.
Whether a transaction timed out because of bad performance, or a component of the solution failed, or an administrator has taken the database offline to perform maintenance, the result is the same to the user: the database is unavailable to process requests.
Steps you need to maximize database availability
- Redundancy: Having secondary copies of each component of your solution that can take over workload in the event of failure.
- System monitoring: collecting statistics about the components of your solution to facilitate workload balancing or detecting that components have failed.
- Load balancing: transferring some workload from an overloaded component of your solution to another component of your solution that has a lighter load.
- Failover: transferring all workload from a failed component of your solution to a secondary component.
- Maximizing performance: reducing the chance that transactions take a very long time to complete or time out.
- Minimizing the impact of maintenance: scheduling automated maintenance activities and manual maintenance activities, so as to impact user applications as little as possible.
Explained all the steps that you need to maximize database performance.
