« Making a Way Forward by Riding Data | Main | Checkup Tips to Diagnose Creeping Crud »

March 25, 2015

Places Where a Migration Can Lead

This afternoon on a Wednesday Webinar, IT managers were watching what advanced software can do to move the identity of a company. A company knows itself by its data. When transforming IT to a new generation, data's got to move, even if it's just to another generation of HP server. More likely, that shift will eventually be leading to a more comprehensive change: a new environment, new server, new database, new application.

Moving the application is an exercise that requires custom work, the sort of programming, development and testing that'll emerge from a team inside a 3000 shop, plus some help from outside. But moving to a new database demands the checking of database schemas, the review of naming conventions, and more. Carrying a company's identity from a TurboIMAGE database to Oracle or SQL Server has been viewed as a complex task for a long time.

Database MapperIt looked a lot less complex during today's demo of MB Foster's UDA Central. Choosing source databases, then selecting a target database of another type, was straightforward. More importantly, this software ensures that data makes its move in a way that delivers a useable resource, not one overrun with table errors and illegal dataset names. Warnings before the data's moved keep the identity of the company clear. There's a default data mapping between databases that's done automatically to get database administrators and managers started quickly.

Watching the software in action made me realize how far we've come in the task of making transformations to our IT enterprises. There was once a Computerworld reporter who asked me what barriers IBM might have to overcome if it stood a chance of converting HP 3000s to AS/400 sites. Well, those databases, I said to him. "You might move the applications or replace them. But the data's got to remain the same."

Database tools have evolved far enough now, 20 years later, that UDA Central's got everyday uses, not just a one-time utility. It's got operations for data stores, for pulling data out for analytics, and more. Those analytics are crucial. Birket Foster said that "If you've never done data analytics, you don't really have clean data." The company's experience with customers moving data taught MB Foster that, he explained.

I saw UDA Central used to transfer a Sybase database hosted on a Linux RedHat server to Oracle on a Windows system, from source to target — and the software had built-in functions such as checks for the length of names. An column bearing a 31-character name won't pass Oracle's 30-character limit, a flag that UDA Central raised automatically. In today's demo the index name was modified right inside of UDA Central to move the data successfully.

Quick data dumps, so you can use the tool to learn about your data without needing to start anything else up. SQL statements called out for a copy and paste, so you don't really have to learn that language to make use of SQL. I watched a lot of power engineered into this software, a tool whose target is successful change. And oh, the places your data can go. From TurboIMAGE to three different flavors of SQL databases, to Oracle and Eloquence and EnterpriseDB and more.

The insight into data through UDA Central makes moving an identity easier. Even if a migration of apps and systems is off in the future, "you can start your data migration today," Foster said. "You can start making a list of what you have for data, you can start figuring out what the fields should look like, and you can start looking at how you can clean up the data."

09:06 PM in Migration | Permalink

Bookmark and Share

Use our search engine to find 20 years
of HP 3000 news and articles



The comments to this entry are closed.