I understand that if one to disable JDBC steps, the TPS values would correctly represent the service requests' throughput. However, the "err" columns then would lid up as all the assertions that match values between JDBC returned rows and Soap response fail which is not something I would like to show in the reports.
I tried to run all the steps, then disable the JDBC steps and execute the load test, hoping that the records retrieved through this "manual" run would persist, and can be used in the load test. But, alas, the load test simply ignores them.
P.S. JDBC steps have been marked distinctively, so identifying and disabling them is of no issue.
