Components show
Name:
PostgreSQLDataWriter
Description:
Receives data through connected input port or reads it from input file, connects to PostgreSQL database using psql utility and loads data records into specified database table. It works faster than DBOutputTable.
Central customer database migration
Migrating a database to ensure long time viability.
I think this is the first major database migration done with Clover, at it happened in 2004. This project involved the migration of the central customer database of a company. The database had grown with the company during 3 years, with no DBA, and had become unmanageable due to its bad structure. It also was running on MSSQL, and we decided to migrate it to Postgresql. So we completely changed the database structure, opting for an extermely flexible approach, and changed of database server. ClovertETL really enabled us to achieve great results. As it was still in early development stages at that time, its code availability let us adapt it and send patches to be included in the project. There was no Clover GUI available at that time, and all migrations were dfined by hand in XML files. That didn't cause any problem though as it was by far the most efficient tool for the job I could find.
Clover Usage | |
| CloverETL framework usage: | Standalone-runGraph util & XML graph definition |
|---|---|
| Main reason for Clover usage: | Best tool for the job. Great flexibility. |
| CloverEngine version: | pre 1.0 |
| CloverGUI version: | none |
| Number of different data sources: | 1 |
| Transformed data volume (MB): | 80.00 |
| Clover usage experience (years): | 1.50 |
| Number of transformations (mappings): | 30 |
Technology | |
| Operation system: | Linux |
| System version: | debian |
| Number of CPUs in system: | 1 |
| Other used systems: | |
| System type: | 32 |
| Java Virtual Machine: | Sun JVM 1.4 |
| Database: | MS SQL, PostgreSQL |