IRI FACT (Fast Extract)
Use FACT v3 to unload your VLDB in parallel. Speed ETL, reorgs, and migration. Beat SLAs.
Accelerate Data Acquisition
Speed unloads up to 7X with parallel query technology. Performance scales linearly in volume . . . extract billions of rows in minutes!Learn More
9 Databases -> 1 Unloader
Use the same fast extraction tool for all of your databases. No learning curve -- use SQL syntax in simple text scripts or an Eclipse GUI.Learn More
Data Ready for Everyone
Produce flat files that any application can use. Plug into and feed ETL operations and offline reorgs. Archive your data. Migrate your VLDB.Learn More
Think about why you need to get data out of Oracle or another DB, where it's going, how often, and how long you think it should take.
Then weigh the alternatives you have, like SQL SPOOL to file (slow), the DB's own pump (into their proprietary format only), buying more hardware, or writing your own unloader.
IRI FACT was made to address all these issues in one fast, affordable, cross-DB extract utility. Front-ended in Eclipse and full of performance and formatting features, FACT also runs seamlessly in IRI reorg, ETL, and migration jobs.
IRI FACT Use Cases
"We have used FACT for almost 10 years to speed Oracle table unloads. We tried multiple alternatives and nothing could beat FACT's extraction speed."
"FACT helps us move data between massive DB sources and targets efficiently. We see FACT as an integral performance piece of our data warehousing operations."
"FACT is an essential component of our banking application because it, along with CoSort, runs faster and cheaper than any legacy ETL technology can."
The Only Unload Tool You Need
Fast Extract Tables from:
- DB2 UDB
- SQL Server
IRI FACT is Critical for:
- Data Archive
- Data Migration
- Data Protection
- Data Replication
- DW ETL
- DW ELT
- Offline Reorgs
- Offline Reporting
Consider IRI FACT
- Are you a data warehouse ETL / ELT architect, or DBA needing faster extraction?
- Do you experience unload, query, or load bottlenecks with large transaction tables?
- Are you responsible for DB archive, replication, migration, or subsetting operations?
- Upgrading or leaving Oracle, DB2, Sybase, MySQL, SQL Server, Altibase, or Tibero?
- Noticing slower query response times from unordered rows or fragmented table space?
What Others Are Reading
Among the key issues for companies who need to unload big data from Oracle, DB2, Sybase and SQL Server are speed, scalability, and simplicity.
Over time, data in large RDBMS tables eventually become fragmented. Reorgs can save table space and improve query performance.
The decision to transform data inside or outside the database has significant speed, support, and spend consequences.