Definitely.

Everybody has a unique set of ETL requirements. Over the last decade we've seen them all, and continually added functionality to RODIN to support everything we've come across. We are confident that RODIN will be up to the task for you.

Listed below are some of the common requirements that RODIN supports -  but this is not an exhaustive list, so if we haven't listed your specific needs, it does not necessarily mean that RODIN doesn't have that capability.

• Real time or batch ETL
• Change Data Capture from journal images
  
• Access data from remote LPARS and non-IBM platforms
• Conditional joins
• Support for partial and closest match joins
  
• Conditional business rules
• Derived columns
  
• Automatic casting of data types
• Legacy date conversions and date calculations
  
• Join multiple rows from the same table
• Incremental load of summary tables
• Load multiple tables in one ETL process (inserts and updates)
  
• Generate Surrogate Keys
• Support for Slowly Changing Dimensions
• Extensive error handling
• Reprocess errors (after correction)
• Reusable components
• User exits
• Simple integration with other processes
• Extensive security layer
  
• Provide extensive documentation via metadata layer
• Impact analysis tools
  
• Manage indexes
• Change Management
• Versioning
• Extensive metadata reports
• Visual development environment
• Integration with DB2 Web Query
• Export metadata to other tools via XMI specification
• Reverse engineering (1 table, or entire database)
• Excellent load performance 
  
• Parallel loading on multi-CPU systems
  
• Push data to other platforms
• Data models
• Enforced data integrity