Here are some things to check to make sure that the iTest mySQL database is set up correctly. First, from the installation guide, ensure that the my.conf file has the following lines: max_allowed_packet = 32M and max_connections = 10000 These lines allow for larger packet sizes as needed by iTest reports and allow for many user connections. If you are having issues with slow report retrieval from the database when clicking on test case steps, execute the following mysql command when the test resport database is selected to ensure that the database is indexed properly: explain SELECT MAX(id) FROM reportitem WHERE stepGuid= '83acee6a-1cd4-404d-bbf9-95b65a675fed'; where the stepGuid is a step from your test case (you can find the step GUI ID by opening the test case with a simple text editor). You should see the following key being used: reportitem_stepguid_id_index If you do not, your database is missing an index that helps iTest quickly find test report items. Execute the following command when at the mysql prompt and using your test report database to add this index: CREATE INDEX reportitem_stepguid_id_index ON reportitem (stepGuid(255),id); You should see a vast improvement in speed for retrieving results when clicking on test case steps.