Powerhouse migration questions

Robert Edis robeconsult@sbcglobal.net
Wed, 12 Jan 2005 12:39:31 -0800 (PST)


Does Axiant have such a tool?  I know it is good for
converting non-relational to relational syntax in PH
code.

Blue
--- Viet Nguyen <VNguyen@wsboces.org> wrote:

> Hi ,
> I am in the process of moving from cisam to oracle
> using AIX - (we are
> keeping powerhouse in Unix) I would like to know if
> anyone out there has
> a parser or a smart search/replace routine to help
> with converting the
> Access statement otherwise I think it will take us
> forever to manually
> make these changes!
> Thanks in advance.
> Viet.
> 
> 
> -----Original Message-----
> From: powerh-l-admin@lists.sowder.com
> [mailto:powerh-l-admin@lists.sowder.com] On Behalf
> Of Jon Kvisli
> Sent: Wednesday, January 12, 2005 10:00 AM
> To: Pat Shugart; powerh-l@lists.sowder.com
> Subject: SV: QTP migration questions
> 
> >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.
>