SV: QTP migration questions

[Jon Kvisli]

>We're not replacing Powerhouse. 
 
Then I strongly advise you to KEEP your QTP programs, but spend some time optimizing ACCESS statements using cursors and SQL. This advise is based on personal, practical experience from converting two large systems (2-300 QTPs) from HP3000/Image to HP9000/Oracle. We then searched for other / better batch-processig tools, but finally decided to stay with QTP.
 
However, you WILL have to do changes in the QTP source. Due to the way QTP interacts with a relational database, most QTPs will do a high number of SQL-calls and perform VERY bad if ACCESS statements are left unchanged. The big issue is to let the databaseserver do most of the job by extracting only the data needed by QTP (that is moving functionality into the database). This will reduce the number of SQL calls from QTP to Oracle, and also reduce network traffic returning data back to QTP. If you do a good job rewriting ACCESS statements using cursors and SQL, you will most likely get performance that is even much better than the original qtp. 
 
Another way of moving functionality into the database, is using stored procedures in PL/SQL, but this is more useful for moving business logic away from QDESIGN/QUICK programs, than with QTP.
 
regards
Jon Kvisli
principal consultant
3800 Bo in Telemark
Norway
jon.kvisli@exchangemail.no