Matillion Reviews

* If you've done any type of ETL work before, this will be a breeze. If you haven't it might take a few hours as opposed to minutes to get up and running
* The trial is full featured, get started today without waiting
* The software is on a EC2 instance in your own VPC in AWS. If you have company policies for how/where data can be processed -- you have complete control
* You can pay by the hour or the year, no hassle no fuss!

If you do encounter an issue the support organization is amazing. All questions were answered the same day, many within the hour.

More examples to work through on the transformation components would be helpful, but again... it's pretty easy

I like the bunch of API integrated in Matillion it helps me to directly grab the data from different sources without manually extra and import in my database.

I am using Matillion for Redshift from last more than 2 years. When i setup a project in Matillion with connection to a Redshift cluster, sometimes there is a need to extract the data from other instance of Redshift while running job in Matillion. In that case there is straight forward way of getting the data from other instance of Redshift like you have comments to extract the data from databases like SQL Server, Oracle etc. instead of first i need to run another job by connection second Redshift cluster and extract the records after that run different job to load the extracted records from S3 to main Redshift cluster.

1) Most of the components are user friendly.
2) Development of ETL orchestrations and transformation consumes less time.
3) Advanced features are available in some of the components makes the complex scenarios achievable.

1) OAuth document does not provide the details of proper permissions and access levels on account_id or client_id which are required for a connector.
2) Differentiation of naming convention of metrics between the console and matillion data model , mapping document of these naming conventions is not available.
3) Connector for Outbrain is not available.
4) Indirect file loading concept is not available , for example if we have five files with same structure , reg ex can not be used to load all files in a single component(s3 load,s3 put or excel)
and need to use the file iterator.
5) Loss of properties when the component configuration is changed from Basic to Advanced features , ideally the component should include all the properties of basic and then additional setting should be provided.

Matillion is very intuitive.
The GUI is easy to use and fairly easy to learn.
The support team is great and they respond to your questions quickly.
I like how the Matillion team is frequently looking to add new functionality and features. The new keyword search functionality is very helpful.

Matillion works great extracting data from a variety of databases and is very efficient unloading onto S3 or Amazon Redshift. However, when we attempted to use it to unload large datasets to Microsoft SQL Server it was very slow and we experienced performance issues.

Matillion is very easy to use. It's simplicity allows you to drag an drop components to easily create orchestrations. It also simple to create shared jobs and use the components.

Although there is a decent set of components, they are not very versatile, hence I end up using a SQL script instead. For example, the S3 unload component does not allow one to specify some criteria and some fields are mandatory whereas I would not have to specify such specific criteria when doing this from an SQL script.

Easy to learn and use. The knowledge from other products is transferable. The documentation is amazing (one probably cannot understand how good without the experience). Support is always available and of good quality.

There is no restart-from-point-of-failure option for failed loads. Everything has to start from scratch or remaining jobs need to be run manually.

Matillion integration with AWS services is flawless and has real time impact in batch jobs pulling data from on-premises to cloud platform.

Restricting the number of user can access Matillion, Lot's of time huge data set get stuck and fail with many other issues lastly better full log specifically for Developer to debug the issues.

It is very easy to implement features and changes to existing workload. It is very good for creating POCs

It is not scalable and has numerous limitations. Concurrency setting for Matillion limits the possibility of using it for multiple warehouses. It is highly insufficient when executing commands parallel and does not utilise the resources to it's full potential.
The environment limitation is also very problematic when trying to scale.

Matillion offers a powerful feature set within a robust UI. There are other options but none have the ease of onboarding that Matillion offers. The API adds a powerful layer to do advanced integrations.

Some threads have become unresponsive while running. This has been rare and was easy enough to resolve by resetting the service.

User interface and range of connections.
Powerful capabilities.
Compatibility with AWS

Licensing is not flexible, Why cant you specify the number of concurrent users for a given instance? It comes with a fixed amount, if you don't like it, update to a much large and expensive instance that we do not need.

I love the GUI that Matillion employs - it makes creating and adjusting tasks very simple and transparent.

The scheduling of tasks is a little tricky, as we have to separately have to schedule the virtual machine to fire up and down. Once this is done though, it works faultlessly.

This tool helps in automating etl process.

Integration with python is limited. Need this feature

1) Easy to use
2) Several ingestion integrations
3) Custom RDBMS ingestion support
4) Robust transformation and Orchestration components

No availability of change data capture feature for many databases

Connectivity to Saas sources. Reliability and Customer Support team

RSD creation for Saas sources that do not have built in connector.

Easy to understand and follow processes. Easy to pass variable values between jobs. Works well with Redshift and S3.

Use of API's can be a little confusing to setup/configure.

Easy to use, graphical way to do data flows on Google Cloud

The most missing functionality, is to be able to setup data destinations additionally to BigQuery

Target based ETL application. Cloud Native.

I would prefer it to support multiple target DBs like SQL Server, Oracle, MySQL, Redshift, Snowflake.

Workflow Layout and clarity of all components

Environment Management, licensing model