Data Integrator - A worthy competitor to SSIS?
May 03, 2016
Data Integrator - A worthy competitor to SSIS?
Score 7 out of 10
Vetted Review
Verified User
Software Version
Pervasive Data Integrator (legacy version)
Overall Satisfaction with Actian DataConnect
We use Data Integrator to bridge data from our Admissions software to our Student Information System. It is used by the IT developers only, with guidance from both the Admissions department and Registrars department. We have three bridges we have built using Data Integrator, one for each main branch/type of student. This product allows us to successfully transition the data appropriately into our core system.
- Map multiple source and destination tables - what would be done in many steps in SSIS can be done in one or two "maps" in Data Integrator.
- Platform independent, cloud based, no client software.
- Conversion of data types, write flat files - this helps us with integrating systems.
- Fairly straightforward to use if the user has ETL experience.
- Sometimes the screen does not load- since it is a web based software, this can be seen as a reliability issue.
- "Maps" can become somewhat complex, and between multiple developers this can be painful when sharing or explaining others' work.
- The concept of macros adds flexibility in how to solve problems, but is a separate language and can take time to learn and master.
- This tool was chosen prior to my arrival and was used to build three integrations. We have decided to switch to SSIS since we have licenses for it and it is a more common tool for ETL integrations.
- It has been difficult to network with individuals that have experience with this tool.
- Having been a part of a software package purchased, we have chosen to use a different tool for future integrations and plan to rewrite existing integrations.
Data Integrator was initially a part of a package deal for us with our new Student Information System. It was chosen prior to my arrival at the institution. Since I discovered we have SQL Server licenses, we have decided to use SSIS instead since I have a background in the MSBI stack and SSIS appears to be more straightforward (process flow philosophy vs "map" philosophy.)