HP3000-L Archives

March 2006, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tony Summers <[log in to unmask]>
Reply To:
Tony Summers <[log in to unmask]>
Date:
Fri, 3 Mar 2006 13:52:28 -0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (145 lines)
As John says,  there are massive advantages to moving to SQL as you are
guided towards a cursor-less approach,  but that really requires you to
re-engineer your applications and the way they approach the data.  Other
recommendations from my SQL experts are to avoid using embedded SQL and
always use stored procedures. 

A lot of legacy applications have grown up using a cursor based
approach;  read a record from a database, process it,  update it, move
onto the next record.  I've looked at what we would have to do to move
our applications onto a RDBMs - and it would quadruple (at least) the
amount of work we would need to spend on each application to migrate it
properly. 

You can use cursors in SQL - and some 3rd party products have a proven
track record of translating image calls onto SQL calls on the target
database - but you would have to seriously consider the overhead of such
an approach. 

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of John Hohn
Sent: 02 March 2006 17:41
To: [log in to unmask]
Subject: Re: [HP3000-L] Migration recommendations; PRELIMINARY INQUIRY

Charles,

My recent experience in migrating two applications (now working on a
third) to an RDBMS environment (not Eloquence) leads me to agree
wholeheartedly with your statements. I liken it to the y2k quandary of
whether to "window" 6 character dates or just bite the bullet and expand
the date field to 8 characters. As long as you're in there
re-engineering, do it right the first time; the downstream payoff (some
known now; most to be realized as the industry continues to evolve) are
enormous.

I think people are afraid of writing SQL, but it's not that hard once
you get used to it. 

There are many advantages to SQL; one that we found is, by re- writing
our complicated reports to not use cursors (doing intermediate
summations with unions instead of programmatic adding up of numbers
inside cursor loops) we can complete reports in seconds (yes, seconds!!)
that used to take 20-30 minutes on the HP3K.

But the real reason to go with SQL, as you stated, are the tools; which
will get better and better and remain cheap or free.

- John Hohn
Comp Three

Date sent:      	Thu, 2 Mar 2006 09:25:19 -0800
Send reply to:  	Charles Finley <[log in to unmask]>
From:           	Charles Finley <[log in to unmask]>
Subject:        	Re: [HP3000-L] Migration recommendations;
PRELIMINARY INQUIRY
To:             	[log in to unmask]

> Ok, I'll risk getting flamed.
> 
> Connie Sellitto Wrote:
> 
> "...... this migration is not driven strictly by HP's discontinuance 
> of the 3000 line.  Our goal is not simply to continue to run existing 
> applications on a supported platform, but to enable easier development

> of web applications with standard tools, give our in-house users a GUI

> interface which can be customized to meet their needs, and allow 
> (read) access to our extended customer base via the Internet.
> 
> Our Board's philosophy regarding data entry, processing and storage 
> has shifted from a 'mainframe' mentality to a server-based system, 
> using non-proprietary DB's and tools.  IMO, they are listening to PC 
> and Mac users who claim "I can do all this in 5 minutes on my PC - why

> can't CFA give me the same info via the web?""
> 
> Fortunately, today this is an achievable goal.  A lot of companies are

> not satisfied with the options provided on the HP 3000 development
environment.
> However, as we can see from other opinions on this list, some people
are.
> 
> Migration to Linux, Unix and Windows with the tools available today 
> can give you the opportunity to not only have comparable capabliity to

> what you have today but to extend development options available to 
> you.  However, not all migration choices lead to expanded options.  
> For example, since so many people on this list recommend using 
> Eloquence, migrating to Eloquence limits you mostly to use of the 
> TurboIMAGE API (there was some talk about ODBC as well).  That does 
> not mean that Eloquence is bad or that you should not use it.  It 
> means that once you migrate your database to Eloquence, your choice 
> for how to get at your data are more limited than they are if you
migrate to an RDBMS. There are similar limitations in other choices of
tools.
> 
> Charles Finley
> 619-795-0720
> 
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________


The contents of this email are confidential to the intended recipient
and may not be disclosed. Although it is believed that this email and
any attachments are virus free, it is the responsibility of the recipient to confirm this.

Smith & Williamson Corporate Finance Limited - A member of the London Stock Exchange.  
A member of M&A International Inc. http://www.mergers.net  Registered in England No. 4533970. Authorised and regulated by the Financial Services Authority 
Smith & Williamson Investment Management Limited, Registered No. 976145. Authorised and regulated by the Financial Services Authority.
Smith & Williamson Pension Consultancy Limited - Independent Intermediary. Registered No. 3133226. Authorised and regulated by the Financial Services Authority.
Smith & Williamson Fund Administration Limited, Registered No. 1934644. Authorised and regulated by the Financial Services Authority.
Smith & Williamson Limited - A member of Nexia International.  Registered in England No. 4534022. Regulated by the Institute of Chartered Accountants in England & Wales for a range of investment business activities.
NCL Investments Limited, Registered No. 1913794.
Member of the London Stock Exchange authorised and regulated by the Financial Services Authority.

Registered Office: 25 Moorgate, London EC2R 6AY
Telephone: 020 7131 4000 http://www.smith.williamson.co.uk

Nexia Audit Limited - A member of Nexia International. Registered in
England No. 4469576. Registered to carry on audit work and regulated by the Institute of Chartered Accountants in England & Wales for a range of investment business activities.

Registered Office: 25 Moorgate, London EC2R 6AY
Telephone: 020 7131 4000 http://www.nexiaaudit.co.uk


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2