We just raised a $30M Series A: Read our story

SSIS OverviewUNIXBusinessApplication

SSIS is the #4 ranked solution in our list of top Data Integration Tools. It is most often compared to Informatica PowerCenter: SSIS vs Informatica PowerCenter

What is SSIS?
SSIS is a package is an organized collection of connections, control flow elements, data flow elements, event handlers, variables, parameters, and configurations, that you assemble using either the graphical design tools that SQL Server Integration Services provides, or build programmatically. You then save the completed package to SQL Server, the SSIS Package Store, or the file system, or you can deploy the ssISnoversion project to the SSIS server. The package is the unit of work that is retrieved, executed, and saved.

SSIS is also known as SQL Server Integration Services.

Buyer's Guide

Download the Data Integration Tools Buyer's Guide including reviews and more. Updated: September 2021

SSIS Customers
PKP Energetyka, UniCredit Bank, Mostar, waldwasser, Ashok leyland, Florida Atlantic University, Stadt Frankfurt am Main
SSIS Video

Pricing Advice

What users are saying about SSIS pricing:
  • "t's incredibly cost effective, easy to learn the basics quickly (although like all ETL tools requires the traditional learning curve to get good at) and has an immense user base."
  • "Based on my experience and understanding, Talend comes out to be a little bit expensive as compared to SSIS. The average cost of having Talend with Talend Management Console is around 72K per region, which is much higher than SSIS. SSIS works very well with Microsoft technologies, and if you have Microsoft technologies, it is not really expensive to have SSIS. If you have SQL Server, SSIS is free."
  • "It would be beneficial if the solution had a less costly cloud offering."
  • "We have an enterprise license for this solution."

SSIS Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
GaryM
Data Architect at World Vision
Real User
Top 5Popular
SSIS 2016 - The good, the bad, and the ugly
Sql Server Integration Services (SSIS) 2016 Review Summary SSIS 2016 - the Good the Bad, and the Ugly SSIS is a unique ETL tool for a number of reasons. Most shops already own it but may treat it as a free utility rather than as an enterprise ETL tool.  Which is ironic given it is superior to many of the supposed enterprise-class tools in a number of areas. The lack of respect in our industry is likely due to immature beginnings in its former "DTS" days and because it comes bundled "free" with Sql Server.  But don't let that fool you into thinking it can't compete with the expensive ETL tools. I've used many ETL tools over the years and I'll take SSIS over any of them. I've now used SSIS exclusively for close to a decade and have no regrets.  SSIS is extremely flexible,…

Sql Server Integration Services (SSIS) 2016 Review

Summary

SSIS 2016 - the Good the Bad, and the Ugly

SSIS is a unique ETL tool for a number of reasons. Most shops already own it but may treat it as a free utility rather than as an enterprise ETL tool.  Which is ironic given it is superior to many of the supposed enterprise-class tools in a number of areas. The lack of respect in our industry is likely due to immature beginnings in its former "DTS" days and because it comes bundled "free" with Sql Server.  But don't let that fool you into thinking it can't compete with the expensive ETL tools. I've used many ETL tools over the years and I'll take SSIS over any of them. I've now used SSIS exclusively for close to a decade and have no regrets. 

SSIS is extremely flexible, extensible and integrated with many other Microsoft tools and a multitude of add-ons - both for purchase and for free. It's come a very long ways since its DTS days.  It's incredibly cost effective, easy to learn the basics quickly (although like all ETL tools requires the traditional learning curve to get good at) and has an immense user base. There are also endless bits of quality shareware available that seamlessly plug-in and a wide variety of low priced vendor supported add-on products to fill in any out-of-the-box gaps (see my other review of MellissaData Data Quality MatchUp for SSIS). And if you can't find something you need and you know how to code C#.net you can extend the tool yourself. So unlike any other tool on the market, there's always a way to make something work with SSIS.

The Good...very good

  • How is free for a price? (for anyone running enterprise or BI editions of SqlServer)
  • Limitless Extensibility

This comes from the fact that SSIS is merely Visual Studio code and comes with templates to add your own custom components. A large variety of pre-built shareware is available at the codeplex.com website and vendors such as MellisaData and Pragmatic Works provide sophisticated add-on components from advanced realtime monitoring to state-of-the-art data quality plug-ins. BIML shareware allows for automated ETL code generation based on XML templates. Some of the shareware available on Codeplex are very high value such as the MultipleHash component providing very sophisticated hashing to support CDC and SCD operations. If you don't like out of the box functionality (such as the SCD wizard which is largely worthless) then there's likely a worthwhile supported replacement by some vendor for a reasonable price. There's built in support for CDC from many database sources such as Sql Server and Oracle for no added charge which is unheard of among their competitors.

Adding plug-ins such as BiXpress, Task Factory and DocXpress from Pragmatic Works are relatively inexpensive tools that do some really amazing things. BiXpress is a MUST for providing real-time and historical monitoring of ETL including tracking package parameter and local variable value changes both in real-time and historical. I highly recommend MelissaData Matchup for SSIS - you'll never see any other data quality tool as easy to use as that one which seamlessly integrates with SSIS.

  • Common Development Environment - Visual Studio

Unlike any other ETL tool - if you learn Visual Studio, you gain familiarity with an entire toolset. Its navigation and project organization is common to all other .net development. Along with Visual Studio you get all the  source control plug-ins inherent with the tool such as TFS (aka. TFVC in VSO which is cloud based and free!), and Git.

  • Job/package Parameters

2012 Version introduced very flexible parameter capability superior to most all other ETL tools. Project and package parameters integrate seamlessly into Sql Agent to provide step-level dynamic change runtime values such as source/target connections. They of course can be used with many other job schedulers albeit a little less tightly integrated.

  • Endless Add-ons

Either via shareware or purchased products. Github provides a huge amount of free shareware code - some of which is very high quality. Vendors such as KingswaySoft and PragmaticWorks and many others provide multitude of inexpensive add-ons from adapters to enhanced components to connect to just about everything.  I use SSIS to connect to Microsoft Dynamics CRM, Oracle Netsuite, on-prem Oracle, hosted source using SOAP calls, and Azure SqlServer as well as flat file loads and on-prem SqlServers.

    • Logging

    Built in reports show package execution and messages.  Logging can also be customized so only what is needed is logged. There is also an excellent logging replacement called BiXpress that provides both historical and real-time monitoring which is more efficient and much more robust than the built-in logging capabilities.  And none of this requires custom coding to make it useful unlike many other ETL tools.

    • Extremely Large User Community

    Just google if you don't know the answer - from youtube to blogs there's an incredible amount of information out there about this tool. I suspect far more than any other ETL tool.

       List of good features...

    1. Respectable Performance and includes a balanced distributor that allows for endless parallelism of data flow pipes
    2. Robust historical repository reporting provided in the included SSISDB repository
    3. Includes connectivity to large variety of sources/targets
    4. Built in CDC for multiple sources (formerly a purchased add-on from Attunity). This feature alone is often 6 figure add-on from other vendors.
    5. High value/low cost Data Quality component integrations from MelissaData
    6. Sophisticated breakpoint debug capability including inside VB and C# scripts
    7. Integration with Change Control Software (e.g. TFS, Subversion, Git)
    8. Fully integrated with Sql Server Agent for scheduling including dynamic job step parameters
    9. Integrates with SSAS tabular and cubes as well as Data Mining algorithms
    10. Includes data profiling task and wizard
    11. High level of sophistication with source/target drivers
    12. Free Attunity OLEDB drivers for higher performance connections to Oracle and Teradata
    13. Multiple plug-ins for interfacing with applications such as Salesforce.com and Dynamics CRM
    14. Longevity of the tool and consistent support and enhancements by Microsoft
    15. Full power of either VB or C# script tasks to accomplish pretty much anything that isn't already included

    The Bad

    • No direct support for push-down of joins

    You have to write push down join & lookup SQL to the database yourself via joins in the data flow source to get very high performance. That said, this is a common complaint for nearly all ETL tools on the market and those that offer an alternative such as Informatica offer them at a very expensive add-on price and even then don't work for all join situations.  (My best practice is complex joins go into views of the data lake/landing area tables anyways so the queries are easily audible but I know there are deferring opinions here.)  

    • Slowly Changing Dimension (SCD) Wizard has poor performance

    No surprise here as this is a common issue with ETL SCD wizards. Requires custom/shareware enhanced wizard or one from 3rd party vendor to get good performance. This begs the question why Microsoft can't come up with a better wizard since it's pretty straight forward to code a dynamic merge as a workaround and someone wrote a much better shareware version. Pragmatic Works also sells a much better and supported version in their toolkit along with many other tools.

    Here's a list of constraints or potential gotchas...

    1. Difficult to monitor server memory usage/bottlenecks. Possible but non-intuitive.
    2. Expression Language primitive and inconsistent with other languages. The workaround is to use the script task that allows either VB or C#.
    3. Limited native scalability - Direct support for multiple server/clustered installation/processing requires the 2016 version but I haven't yet tested this feature so I'm leaving this in as a constraint for now.
    4. Flat file connectors are overly difficult to build and maintain - Changes in columns and file layout is cumbersome and problematic. Datatype detection is almost always wrong requiring manual settings for every column. Flat files that use quoted fields between delimiters don't work if a quote is included in the data - it can't find the field alignment and the data flow errors out. I know of no simple solution for this as it errors in the source before you can apply a cleansing function to it.
    5. Default datatypes not always correct when reading from views. This can cause syntax errors in data flows and components such as union all. Workarounds are to explicitly convert in datatype conversion task or override the default metadata datatype.
    6. Previous metadata often does not disappear when changing targets/sources. Tasks have the tendency to hold onto previous datatypes and lengths and not automatically pick up the changes.
    7. Inconsistent data types for variables and parameters. Start with one set of datatypes coming from a database, combine with a completely different set of internal variable datatypes, another set with either Vb or C# variable datatypes when using script tasks, another set of datatypes when passing parameters to stored procedures, and yet another when applying SSIS expressions...and it's quite the mess in the end. You get it figured out eventually but it leaves you scratching your head asking why it has to be so difficult when it's all the same vendor's product. The C# and VB and database datatypes are a given but why can't the others follow one of those?
    8. Confusing context/scope for variables to watch when running multiple levels of parent/child execution. Debug mode shows all of them at the same time and the context for each set is not intuitively obvious. For example you get list of each parent and child in the hierarchy of calls and its easy to mistake which package the variables relate to when viewing in the debugger.
    9. Expression editor is clumsy and language is cryptic.  There are 3rd party shareware editors which may help develop your code but the end result is hard to read if complex. As a general rule it is best to move complex expressions into VB or C# script task to avoid hard to maintain expressions.

    10. Logging significantly impacts performance. You can customize logging however starting with 2016 version.

    The Ugly

    SSDT is still 32 bit!

    Yup...and you thought this was the year 2020 and everything is 64 bit. Apparently Microsoft doesn't know that yet. Combine that with its tendency to not release memory and its not difficult to hit out of memory errors when doing SSIS development.

    So...

    Here we go with more not-so-pretty "features"...

    Development environment and deployment wizard becomes unstable with larger projects

    It is not unusual to get "out of memory" errors IF you use the default deployment wizard which is 32 bit on even medium sized projects. However there is a 64 bit version that eliminates this issue but you have to realize that using it isn't the default.

    SSDT (the development tool) keeps grabbing more memory as you open new solutions so you have to exit at least once a day to free up memory. SSDT is unstable if you open more than about 30 packages at a time (such as when you're applying framework code to a bunch of packages - you have to limit how many you do at a time).

    Containers that help group tasks have several very annoying bugs. For example, sometimes if you attempt to resize the container it will make the diagram tool move about wildly and out of control. A task within a container sometimes becomes detached and you can't get it back into the container.  This is common with sequence containers when you try to add a new task.  The new task seemingly disappears but is actually behind the container.  The workaround is to cut and paste it in but you may start to scream before you figure that out.  

    And if that's not enough, here's a very special feature for you to enjoy...If you change the "show annotation" on a precedence constraint when the constraint is using a package parameter, Pennywise the clown slaps you in the face, laughs and then SSDT dies. There is fortunately a workaround.  You can make the constraint something generic like 1==1, change the show annotation again  and then put the real constraint into it. In the end you walk away with satisfaction knowing you found a way to slap it back.  

    Prior to 2012 not recommended!

    Prior versions had many issues including debugging instability with large parent-child package call volumes and .com locking issues when running many parallel threads. It's largest drawback however was it was WAY overly complicated with its configuration XML file method of passing data between packages. That said, it was still superior to ETL tools that require passing parameters via just files (such as Informatica)! But these issues were resolved with 2012 when they introduced project and package parameters and they also improved memory management for parent/child package calls.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Ismail Lahbabi
    Data Engineer at a tech services company with 11-50 employees
    Real User
    Top 10
    Good support, user-friendly, and easy to integrate with Microsoft tools, but needs a better console, more features, and better capability to handle a large volume of data

    Pros and Cons

    • "The most valuable thing is that it is easy to connect with Microsoft tools. In Europe, particularly in France, a lot of companies use Excel, SQL Server, and other Microsoft tools, and it is easier to connect SSIS with Microsoft tools than other products."
    • "It is also easy to learn and user-friendly. Microsoft is also good in terms of technical support. They have built a large community all over the world."
    • "When I compare Talend and SSIS, Talend provides more features. With Talend, we can handle a large volume of data. Talend is usually used to treat a large volume of data, which makes it better than SSIS on the data side. Talend also has a very good Talend Management Console to schedule the jobs and do other things. It can also be easily connected to version control tools such as GitHub or SVN. The last time I used SSIS, it was connected through TSS for the Windows Console version. I am not sure it has been improved or not. If it is not improved, Microsoft should improve it. They should change the product to provide another console."

    What is our primary use case?

    We are using it in our company and for our clients. I have experience in working with the whole data cycle, which includes data collection, transformation, and visualization. I have worked with the end-to-end process, and I have handled data integration, analysis, and visualization.

    I specialize in Microsoft tools, and I have used SSIS for data integration and Power BI for data visualization. I have also worked with Tableau for data visualization and Talend for data integration.

    What is most valuable?

    The most valuable thing is that it is easy to connect with Microsoft tools. In Europe, particularly in France, a lot of companies use Excel, SQL Server, and other Microsoft tools, and it is easier to connect SSIS with Microsoft tools than other products.

    It is also easy to learn and user-friendly. Microsoft is also good in terms of technical support. They have built a large community all over the world.

    What needs improvement?

    When I compare Talend and SSIS, Talend provides more features. With Talend, we can handle a large volume of data. Talend is usually used to treat a large volume of data, which makes it better than SSIS on the data side. 

    Talend also has a very good Talend Management Console to schedule the jobs and do other things. It can also be easily connected to version control tools such as GitHub or SVN. The last time I used SSIS, it was connected through TSS for the Windows Console version. I am not sure it has been improved or not. If it is not improved, Microsoft should improve it. They should change the product to provide another console. 

    How are customer service and technical support?

    Microsoft is good in terms of technical support. They provide 24-hour support. They have built a large community all over the world, and one can find easily the answer to an issue or problem by searching on the web.

    How was the initial setup?

    Its installation wasn't my job. We have a team that specializes in infrastructure, and they install and set up the tool. When I was a student, I used to install it myself, and it wasn't really difficult, but I have not installed it on a professional site or for a company. 

    What's my experience with pricing, setup cost, and licensing?

    Based on my experience and understanding, Talend comes out to be a little bit expensive as compared to SSIS. The average cost of having Talend with Talend Management Console is around 72K per region, which is much higher than SSIS.

    SSIS works very well with Microsoft technologies, and if you have Microsoft technologies, it is not really expensive to have SSIS. If you have SQL Server, SSIS is free.

    What other advice do I have?

    I would rate SSIS a six out of ten. I prefer Talend over SSIS.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    Find out what your peers are saying about Microsoft, Informatica, Oracle and others in Data Integration Tools. Updated: September 2021.
    541,462 professionals have used our research since 2012.
    Muhammad Arif Javed
    Senior Manager Software Development at Techlogix
    Real User
    Top 5
    While you can build your own components, that is not straightforward

    Pros and Cons

    • "The debugging capabilities are great, particularly during data flow execution. You can look into the data and see what's going on in the pipeline."
    • "It should have other programming languages supported as well from a scripting perspective. Currently, only C# and VB.NET are supported, which limits it to .NET. It should have Java support as well."

    What is our primary use case?

    We have used SSIS in many ways. Primarily, it has been used for building ETLs for populating data warehouse and staging areas. We have developed a number of data marts that were populated. We build data migration packages, which have been reused a number of times with minimal configurations. Additionally, we build complex data integrations solutions and data hand-offs between different applications. We have even used it for creating and parsing SWIFT messages for data integration purposes. We also used it for email triggers. 

    How has it helped my organization?

    SSIS is a tool which anybody can learn in no time. When we started the project, the whole team learnt it in one week's time and then were ready to start on project tasks. It gives you control. 

    What is most valuable?

    Script task and Script component for custom tasks: It gives you power to build your own logic if your requirements are not being fulfilled with existing available components. While the big thing is you can build your own components, that is not so straightforward. 

    It's visual design interface is good and you can easily understand the flow. 

    The debugging capabilities are great, particularly during data flow execution. You can look into the data and see what's going on in the pipeline. It has good logging capabilities as well.

    What needs improvement?

    It should have other programming languages supported as well from a scripting perspective. Currently, only C# and VB.NET are supported, which limits it to .NET. It should have Java support as well. 

    We couldn't explore big data related components, and this area should be up to the mark, if not already. Certain data quality checks should also be part of it. Currently, this is the biggest area that should be looked into. Data quality is an essential part of the integration process and ETL. Currently, only the data profiling task is there.

    For how long have I used the solution?

    Five years.

    How was the initial setup?

    Its setup is very easy. You don't need too many components to start building ETL tools. Plus, there are a lot of online learning available for this tool. It can be deployed on any Windows machine with minimal requirements.

    What other advice do I have?

    Overall, we remained in a good position and in control while using SSIS. We didn't face any challenges.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    ChitraGovindasamy
    BI Consultant at a tech services company with 201-500 employees
    Consultant
    Top 10
    Variety of transformations, good SQL integration, and allows C# scripting

    Pros and Cons

    • "The script component is very powerful, things that you cannot normally do, is feasible through C#."
    • "The solution could improve on integrating with other types of data sources."

    What is most valuable?

    Some of the valuable features I have found with this solution has been the variety of transformations that are possible and it works well with SQL servers. The majority of our clients that I worked for, their whole systems of data is using SQL server which has worked better for them.

    The script component is very powerful, things that you cannot normally do, is feasible through C#. If you can write a script you can import it through the Script Task.

    What needs improvement?

    The solution could improve on integrating with other types of data sources. We had issues with connecting to Oracle, it did not do as good of a job as it did with SQL servers. 

    In my experience, more efficiency is needed when it comes to dealing with huge volumes of data. However, this is also dependant on the server capacity.

    In an upcoming release, they should update the features to facilitate efficient data transfers. 

    For how long have I used the solution?

    I have been using the solution for approximately 10 years.

    What do I think about the stability of the solution?

    We have not experienced any behavioural differences with the operations of the solution, it is stable.

    What do I think about the scalability of the solution?

    We typically implement the solution for enterprise-size companies.

    How was the initial setup?

    The installation was easy.

    What's my experience with pricing, setup cost, and licensing?

    It would be beneficial if the solution had a less costly cloud offering.

    Which other solutions did I evaluate?

    Informatica and Talent, are two options I am currently evaluating.

    What other advice do I have?

    Customers have moved on pass SSIS and use Azure Data Factory, Databricks or something similar. We have a few of our customers looking to moving on to Informatica or Talent. This is how I was led to itcentralstation.com, to learn more about SSIS and how it was compared to Informatica. 

    I have never had a situation where a particular transformation was not possible in SSIS. We have always been able to meet the demands of our need with SSIS.

    I rate SSIS an eight out of ten.

    Disclosure: My company has a business relationship with this vendor other than being a customer: partner
    Flag as inappropriate
    AL
    Teaching Professional at a tech services company with 1-10 employees
    Real User
    Top 20
    Straightforward to set up, easy to operated with a user-friendly interface

    What is our primary use case?

    We are a software development company and implement solutions like SQL Server SSIS for our clients. We do not use this product ourselves in the company but have experience with it because our client asked for it. Our clients use it to transform data and generate reports. The use cases are generally simple, and not advanced or complex.

    What is most valuable?

    The interface is very user-friendly.

    What needs improvement?

    It runs a little bit slowly, although this may be because of our laptops. I would like to see better integration with Power BI.

    What do I think about the stability of the solution?

    The stability is okay. It is easy to support.

    What do I think about the scalability of the solution?

    There are approximately 10 users. At this…

    What is our primary use case?

    We are a software development company and implement solutions like SQL Server SSIS for our clients. We do not use this product ourselves in the company but have experience with it because our client asked for it.

    Our clients use it to transform data and generate reports. The use cases are generally simple, and not advanced or complex.

    What is most valuable?

    The interface is very user-friendly.

    What needs improvement?

    It runs a little bit slowly, although this may be because of our laptops.

    I would like to see better integration with Power BI.

    What do I think about the stability of the solution?

    The stability is okay. It is easy to support.

    What do I think about the scalability of the solution?

    There are approximately 10 users. At this time, there are no plans to increase usage.

    How are customer service and technical support?

    I have not used technical support. Instead, I read blogs and the support that is available online.

    How was the initial setup?

    The initial setup is easy, and we did not find it complex.

    What about the implementation team?

    Our in-house team was responsible for deployment.

    What other advice do I have?

    I would rate this solution an eight out of ten.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    MB
    Project Lead Performance Engineer & Automation at a insurance company with 10,001+ employees
    Real User
    Top 5Leaderboard
    Stable, good technical support, and scalable

    What is our primary use case?

    We are using SSIS for all of our relational database management systems (RDBMS) data.

    What needs improvement?

    The solution could improve by having quicker release updates.

    For how long have I used the solution?

    I have been using SSIS for approximately 

    What do I think about the stability of the solution?

    The solution is stable.

    What do I think about the scalability of the solution?

    The solution is scalable. With virtualization enabled we are able to scale horizontally. We have approximately 2,000 users using this solution in our company.

    How are customer service and technical support?

    The technical support is very good.

    Which solution did I use previously and why did I switch?

    We have previously used Oracle.

    What about the

    What is our primary use case?

    We are using SSIS for all of our relational database management systems (RDBMS) data.

    What needs improvement?

    The solution could improve by having quicker release updates.

    For how long have I used the solution?

    I have been using SSIS for approximately 

    What do I think about the stability of the solution?

    The solution is stable.

    What do I think about the scalability of the solution?

    The solution is scalable. With virtualization enabled we are able to scale horizontally.

    We have approximately 2,000 users using this solution in our company.

    How are customer service and technical support?

    The technical support is very good.

    Which solution did I use previously and why did I switch?

    We have previously used Oracle.

    What about the implementation team?

    We have approximately 12 administrators and managers that do the implementation and maintenance of the solution.

    What's my experience with pricing, setup cost, and licensing?

    We have an enterprise license for this solution.

    What other advice do I have?

    I would recommend this solution to others.

    I rate SSIS a nine out of ten.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    Bob Amy
    Sr. Architect - Data warehousing & BI at Molina Healthcare, Inc.
    Real User
    Top 10
    Fast insert, fuzzy logic matching, and free for developers to learn on

    Pros and Cons

    • "The most valuable features of this solution are the fast insert and fuzzy logic matching."
    • "Generic processes should be used instead of custom code for each table."

    What is our primary use case?

    We use this solution to ingest data to a data lake that is built on SQL Server.

    How has it helped my organization?

    SSIS seems easy to use, is freely available for programmers to learn on their own, and has a lot of resources on the web for any trouble you get into.

    What is most valuable?

    The most valuable features of this solution are the fast insert and fuzzy logic matching.

    What needs improvement?

    This may be done, but upgrades to new versions required re-implementing each package.  This is worse for us because we have about one thousand SSIS packages. Hopefully they are now allowing backwards compatibility.

    Generic processes should be used instead of custom code for each table.

    For how long have I used the solution?

    I have been using this solution for fifteen years.
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Product Categories
    Data Integration Tools
    Buyer's Guide
    Download our free Data Integration Tools Report and find out what your peers are saying about Microsoft, Informatica, Oracle, and more!