Q4 Server testing and monitoring

1. Testing and Recording of Results

The performance test activities will be limited to the business transactions as defined in the
subsequent sections of this document. The test strategy assumes that there is no batch
activity therein during normal business operations. Performance testing scenarios that are
modelled on real-life transactions and user load would be carried out on the system to
investigate the system response, resource utilization, and other system parameters. During
performance testing, the PwC performance testing team will simulate only those
transactions from the source system that cause server interaction or place load on
Application, Web, and DB servers. Any waiting period for transactions posted within the
application would be handled through appropriate wait time in the scripts. Any other
external systems/portals that have a direct/indirect reference/interaction with <Application
Name> Application, will not be considered a performance test.

2. Rectifying Errors Using Troubleshooting Tools and Techniques

When errors were encountered during testing, I used troubleshooting tools and techniques
to identify and rectify them. Some of the tools I used included Event Viewer: This tool allows
you to view event logs and trace errors.

Performance Monitor: This tool allows you to monitor system performance and identify
bottlenecks.

SQL Server Profiler: This tool allows you to profile SQL queries and identify performance
issues.

Event Viewer: I also used techniques such as debugging, logging, and error handling to
identify and fix errors.

3. Retesting

Once errors were fixed, I retested the system to ensure that the changes had been properly
implemented and that there were no new issues introduced. I repeated this process until all
issues were resolved and the system was functioning as expected.

4. Validation of Changes

Finally, I validated the changes made to the system by conducting a thorough review of the
system documentation, configuration files, and code. I also conducted user acceptance
testing (UAT) to ensure that the system met the requirements and expectations of the end-
users.

Overall, thorough testing and validation are crucial steps in ensuring that changes made to a
system are properly implemented and meet the needs of stakeholders. By following these
steps, I was able to successfully upgrade an MS 10.1 installation with Server 2008 and
MSSQL 2008 server, while minimizing disruption to the business and ensuring that the
system was secure, stable, and efficient.