When you're migrating in-house apps away from an HP 3000, replacing a database is a crucial choice. Much of the 3000 community is moving such apps to Eloquence for good reasons: the database is affordable, it understands IMAGE structures and programming, and the solution is loaded with lots of extras. Eloquence is full-featured enough to be considered a language.
However, your migration choices might be dictated by your IT personnel. If your company is losing its 3000 expertise and you're exploring the world of open source databases, eventually you'll look over SQL options. They don't all have to be spelled Oracle or SQL Server. You can get a comparison of two open source tools in an online seminar mid-day US time.
EnterpriseDB, advocates of using Postgres, is sponsoring a GoToMeeting webinar starting at 1PM EDT today. The invitation says in part:
For years, the common industry perception has been that MySQL is faster and easier to use than PostgreSQL. PostgreSQL is perceived as more powerful, more focused on data integrity, and stricter at complying with SQL specifications, but correspondingly slower and more complicated to use. Like many perceptions formed in the past, these things aren't as true with the current generation of releases as they used to be.
If you register, the company will email you a link to download a recording of the seminar, even if you can't attend.
• Pros and cons of using PostgreSQL or MySQL
• Ongoing trends towards using open source in the enterprise
That last item will be of interest to the migrating HP 3000 site that's trying to contain costs and control its own future. One well-regarded vendor of 3000 applications, QSS, has been migrating its customer base slowly onto such open source tools as Ruby on Rails. You need relationships in technology to stay stable and vital, but the old sort of arrangement where a vendor can cancel your platform grows more passe with every day. Vendor lock-in is something that open source is relegating to a "perception formed in the past."