Astera Data Pipeline Builder is a no-code solution for designing and automating data pipelines. It allows users to read and write data across various file formats, databases, and applications. Users can execute ETL and ELT pipelines manually, schedule automated reruns, or integrate them into broader data management processes.
N/A
SSIS
Score 7.4 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
N/A
Pricing
Astera Data Pipeline Builder (Centerprise)
SQL Server Integration Services
Editions & Modules
Centerprise Enterprise
Contact rep
Lifetime License per Seat
No answers on this topic
Offerings
Pricing Offerings
Astera Data Pipeline Builder (Centerprise)
SSIS
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Discounts are provided for 10 pack, 20 pack, 50 pack, and enterprise wide Centerprise Professional licenses.
—
More Pricing Information
Community Pulse
Astera Data Pipeline Builder (Centerprise)
SQL Server Integration Services
Considered Both Products
Astera Data Pipeline Builder (Centerprise)
Verified User
Director
Chose Astera Data Pipeline Builder (Centerprise)
The biggest difference is with Astera Centerprise I could just start using it. Almost every other tool required me to write SQL or in another language... and if I'm writing SQL already, why not just use SSIS or raw SQL? There wasn't a tremendous amount of time savings being …
Verified User
Team Lead
Chose Astera Data Pipeline Builder (Centerprise)
Centerprise is easier for everything except the most demanding jobs. Centerprise is not for full blown enterprise data warehouses.
We looked at continuing to use SSIS as an alternative. Although we own SSIS as part of our SQL licensing, we found that it takes a much higher skill level to create solutions. It also does not have the ability to parse unstructured data the way that Centerprise Data …
By magnitudes...the time to implement a map. I was up an running in under an hour. The interface is extremely well designed and simple to use. Logging is very robust. Transformations and functions are much easier to use than other vendors I have tried.
SSIS
Verified User
Project Manager
Chose SQL Server Integration Services
When looking to evaluate different options, we looked first to the experience and software we had in-house that would accomplish the job. When assessing alternatives outside we were looking for the tool that would offer the most flexibility.
I have only been using Astera Centerprise for about 6 months and I am still learning the ins and out of it. A scenario where it seems to do well is in generating reports from SQL queries that we already had and no longer have to run the reports manually. The SQL Query Source object has been the most useful tool for me thus far. I have yet to fully stress test the server side of Astera Centerprise, but currently there have been some version updates that required me to re-set up all the scheduled jobs that we have. We only have 8 jobs thus far but have plans to expand this into the hundreds and those same updates would require exponential amounts of work.
As I mentioned earlier SQL Server Integration Services is suitable if you want to manage data from different applications. It really helps in fetching the data and generating reports. Its automation make it very easy and time efficient. It works well with large database as well. But it doesn't work well with real time data, it will take some time to gather the real time data. I would not recommend using it in a real time/fast-paced environment.
When purchasing Astera Centerprise you are given options on how you would like to be trained and each option comes with a different price tag. We chose to be trained using online meetings over several days. The training went too fast and it was not always easy to understand until I started using the product.
I am a person that wants to learn how and why something works so that I can use the knowledge in the future. When contacting the support team they take the problem, create a solution for you and send it back. The solutions always work, but when I get the solution I have to review every field and function to understand how it works so that I can re-create it for another solution I need. I would much rather have the support team explain what I had done incorrectly and what they changed or I would like to find a solution with them instead of having it handed to me.
Astera uses license keys to allow their customers rights to only the functionality that was purchased. Each user and server has its own key and each key is only good for one year. There have been 2 different times that we received keys that had less functionality that we purchased. It wasn't until it created problems that we noticed and had to request new keys. This year our sales representative made sure she was available when we updated our keys so that if there was a problem she could fix it right away; however, there were not issues this year. I believe this is something they pay closer attention to now.
Connection managers for online data sources can be tricky to configure.
Performance tuning is an art form and trialing different data flow task options can be cumbersome. SSIS can do a better job of providing performance data including historical for monitoring.
Mapping destination using OLE DB command is difficult as destination columns are unnamed.
Excel or flat file connections are limited by version and type.
We've been using Astera Centerprise application for the last 6 years and we've already added EDI connect to it. Both applications are working really well for our enterprise needs so far with no issues, so we'll continue renewing the licenses.
Some features should be revised or improved, some tools (using it with Visual Studio) of the toolbox should be less schematic and somewhat more flexible. Using for example, the CSV data import is still very old-fashioned and if the data format changes it requires a bit of manual labor to accept the new data structure
Centerprise is highly usable; however the version we are currently using could be a little more intuitive in some areas though by no means unworkable. I think some of the issues we have have been addressed and solved in the latest version.
SSIS is a great tool for most ETL needs. It has the 90% (or more) use cases covered and even in many of the use cases where it is not ideal SSIS can be extended via a .NET language to do the job well in a supportable way for almost any performance workload.
In most cases Astera is stable. However, our client experiences the error from time to time. Mostly they are related to cdc file and ServerAdminConfig.xml file.
SQL Server Integration Services performance is dependent directly upon the resources provided to the system. In our environment, we allocated 6 nodes of 4 CPUs, 64GB each, running in parallel. Unfortunately, we had to ramp-up to such a robust environment to get the performance to where we needed it. Most of the reports are completed in a reasonable timeframe. However, in the case of slow running reports, it is often difficult if not impossible to cancel the report without killing the report instance or stopping the service.
Support is great! No matter if you need technical assistance or you have general questions about the tool - the support is very responsive and provides solutions quickly. They are available via various channels, which makes it very convenient to get in touch with them (Support portal, direct email contact, LinkedIn).
The support, when necessary, is excellent. But beyond that, it is very rarely necessary because the user community is so large, vibrant and knowledgable, a simple Google query or forum question can answer almost everything you want to know. You can also get prewritten script tasks with a variety of functionality that saves a lot of time.
Astera support provided us implementation/installation tutorial and we were able to perform all the activities. Also one of the support was there to shadow us to make sure the process was smooth with no issues
The implementation may be different in each case, it is important to properly analyze all the existing infrastructure to understand the kind of work needed, the type of software used and the compatibility between these, the features that you want to exploit, to understand what is possible and which ones require integration with third-party tools
We looked at continuing to use SSIS as an alternative. Although we own SSIS as part of our SQL licensing, we found that it takes a much higher skill level to create solutions. It also does not have the ability to parse unstructured data the way that Centerprise Data Integrator can. We also looked at Datawatch Monarch as a possibility but found it over-all to be cost-prohibitive. We also looked at a cheaper alternative called SimX but did not have a strong confidence in the product as we evaluated it. We landed on Centerprise Data Integrator as it met all of our business requirements and we know we could leverage it for many uses across our enterprise.
I think SQL Server Integration Services is better suited for on-premises data movement and ADF is more suited for the cloud. Though ADF has more connectors, SQL Server Integration Services is more robust and has better functionality just because it has been around much longer
I was helping on purchase this product but I am not sure about the term and pricing for it. But based on what I understand that the term of the licenses are good.
I think Astera can do multiple things. However, we are not sure what it can do. We only know the basic features. If they can give us some kind of training, then we maybe able to benefit for it. We are planning to use their Azure connection in the future. If they can provide the training for it, it will be wonderful.
It is tough to say on how Centerprise would have helped us with ROI. Unfortunately our project (after 3 years) was scrapped (put on hold) due to the impromptu purchase of another Crop Insurance company. But with that, Centerprise was huge in getting our warehouse loaded for our BI Team to make important decisions about our policies.
Without this, we would have to manually update a spreadsheet of our SQL Server inventory
We would also have poor alerting; if an instance was down we wouldn't know until it was reported by a user
We only have one other person who uses SQL Server Integration Services , he's the expert. It would fall to me without him and I would not enjoy being responsible for it.
