SV: QTP migration questions

[Joe Boyle]

my comments related to QTP performance are certainly related to the
PowerHouse QTP cursor concept and syntax as opposed to the original caller's
( assumed ) current processing with standard non-cursor access syntax.

I.e. if you replace QTP syntax like 'access filea link ... to filen ...'
with QTP syntax like 'declare qtpC as cursor for select itemlist from
tablelist ...', I suspect that you will see a large performance increase. 

And even if you leave your QTP syntax as is, when moving from Mpe to Unix
with Oracle, QTP will still run faster.

Regards, Joe.

This e-mail and all information contained in it is confidential and may be
legally privileged. If you are not the intended recipient, your access to
this e-mail is unauthorized. Any use, dissemination, distribution,
publication or copying by you of this e-mail or any of the information
contained within it is prohibited and may be unlawful. Do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so. The content of this e-mail and any
attachments sent with it may have been altered without the consent or
knowledge of the author.

-----Original Message-----
From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Robert Edis
Sent: 12 January 2005 20:38
To: PowerHouse List
Subject: Re: SV: QTP migration questions

Pat

To clarify my earlier message I was referring to
database cursors, those create and used within objects
such a stored procedures.  

Most of the other respondents are referring to the
Cognos idea of a cursor which is construct in QTP
created in order to make SQL calls to the database.

Blue

--- Jon Kvisli <jon.kvisli@exchangemail.no> wrote:

> >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
>  
>  
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = =
> = =
> Mailing list: powerh-l@lists.sowder.com
> Subscribe: "subscribe" in message body to
> powerh-l-request@lists.sowder.com
> Unsubscribe: "unsubscribe <password>" in message
> body to powerh-l-request@lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you
> must be a subscriber.
> 

= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.sowder.com
Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request@lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.