subject: legacy question
posted: Wed, 16 Oct 2002 12:21:34 +0100


Hi folks,

A number of customers I have met have old databases of various
descriptions, either real dBASE, Paradox or FoxPro databases, Access
databases, or database applications built on top of a database engine
(such as the Borland Database Engine (which is Paradox again) or
Progress).

My question is, would it be the opinion of the group that the best
practise in this situation is to migrate the customer to an SQL-based
database with a web-based front-end?

That is, what is now a 16-bit DOS/Win 3.x application running over the LAN
(typically using a shared drive) should become an intranet application
running over TCP/IP.

Proprietary server software is replaced with MySQL on unix, while
proprietary client software is replaced with any web-browser. Business
logic is relocated to SQL, PHP and HTML.

This approach ports the database to a modern, extensible environment, will
allow the use of standard tools and processes on the database (eg. backup
and other administrative tasks), and will provide a more flexible means
for users to work with the data. In the long-term this will produce more
efficient and effective use of the database, while reducing the cost of
its maintenance, and presumably increasing speed, security and
reliability.

Correct? :)

Stuart


---
* Origin: [adminz] tech, security, support (192.168.0.2)

generated by msg2page 0.06 on Jul 21, 2006 at 19:04:36

 search: