We primarily use SSIS to collect data from one system and transfer it to another.
The Classical ETL processing of data.
We primarily use SSIS to collect data from one system and transfer it to another.
The Classical ETL processing of data.
It's a competent product. You can do a lot of things with it and learn how to use it. You can't do modern things with it, but you can do legacy things with it.
It is an out-of-date product, that we shouldn't be using anymore, as it no longer has many positive aspects.
It is an old tool. We make an effort not to use it. It's a legacy tool, that is nearing the end of its useful life. There could be some good things but we try not to get into that.
We have selected to go with another tool. SSIS should not be used whatsoever anymore. There are new versions, that are cloud-based, which are much more improved and much more feature complete.
We have been working with SSIS for 15 years.
We are working with the latest version. It hasn't been updated for many years.
I would say it's both reliable and stable. It's been on the market for 20 years, so it's a very mature product.
There are limitations. I wouldn't say that it is easy to scale. You can scale it, but I wouldn't say it can easily be done.
We have eight people who use this solution in our company.
Support is available, but it is no longer up to date. It needs to be improved.
We switched to Data Factory, which is the cloud version of SSIS and the primary reason for the switch.
Absolutely, the initial setup is a simple process. In my opinion, it's easy.
SSIS doesn't require any maintenance.
The deployment was completed internally.
It comes bundled with other solutions, which makes it difficult to get the price on the specific product.
It's actually a tool that we're attempting to eliminate. That should not be used. It's an old piece of equipment. That should not be used in any way.
If I was asked five or six years ago, I would recommend this solution, but not anymore.
I would rate SSIS an eight out of ten.
We primarily use the solution for data transformation.
The most valuable features for our company are the flexibility and the quick turn around time in producing simple ETL solutions. Also, the use of the configuration on Azure. Our clients are basically secret sever based, so it works well there.
In terms of improvements to the solution, I don't think I have that expertise on it to recommend product enhancements right now. I've only used a few parts of it. Based on what I've used so far, I am happy with it.
I come from a coding background and this tool is graphically based. Sometimes I think it's cumbersome to do mapping graphically. If there was a way to provide a simple script, it would be helpful and make it easier to use.
The solution is currently running in production. It's stable.
We've never had to contact technical support. We generally handle any issues ourselves.
The initial setup is straightforward. Deployment is done by another team. I download the package and deliver it to them and they deploy it onto the cloud. In terms of maintenance, we only need one person.
We are using the 2014 Public Cloud version of the solution, under Microsoft Azure.
In terms of recommending the solution, it obviously depends on the level users you have. If you mainly have a simple graphical based user then maybe you could go for SSIS. If you want to take control of the whole ETL process, you should look for another tool. I use Informatica PowerCenter as well. That's a bit more of a robust ETL solution.
I would rate the solution at six out of ten.
SSIS' most valuable feature is its reporting services.
SSIS sometimes hangs, and there are some problems with servers going down after they've been patched.
I've been using SSIS for over eight years.
SSIS' stability is fairly good, but there's room for improvement.
The initial setup was pretty simple.
SSIS is fairly well-priced - I would rate it at four out of five.
SSIS is best suited for small and medium companies. I would rate SSIS eight out of ten.
It's too early to say how it has improved my organization, as we've just begun using the solution. First, we need to create the appropriate role before we see organizational improvements. We're just in the discovery phase of the tool.
I couldn't point out a specific feature above all others, but I can say the solution is very useful to us. It's well designed and quite straightforward. There isn't much of a learning curve involved. It's a well-documented solution.
It's at a very early stage in terms of adopting the tool, so I can't speak to if there are areas for improvement just yet.
Video training would be a helpful addition, however.
The stability of the solution is impressive.
The scalability of SSIS is very good. Right now, only I am using the solution, but we plan to increase usage in the future.
I haven't required any technical support, so I'm not in a position to judge it.
The setup is straightforward. It's very easy to install.
We did the implementation ourselves.
We did not evaluate other options before choosing this solution.
We are just beginning development with this solution, so we're currently starting with the on-premises version.
So far, I haven't been disappointed by the tool. I have not explored the dashboard tuning feature yet, so I don't know if there are things we can do, like building our own matrixes or choosing deployment preferences, but I hope that will be the case.
I'd rate the solution ten out of ten.
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.
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.
I have been using the solution for approximately 10 years.
We have not experienced any behavioural differences with the operations of the solution, it is stable.
We typically implement the solution for enterprise-size companies.
The installation was easy.
It would be beneficial if the solution had a less costly cloud offering.
Informatica and Talent, are two options I am currently evaluating.
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.
We primarily use the solution for integration packages for ETL in order to build data warehouses.
The workflow features have been very valuable. You can have automated workflows and all the steps are controlled. The workflow functionality of integration services is excellent.
The solution should offer more information online for users of SSIS. There are only a few general data sources available, but it would be helpful if there was more extensive information.
The solution could also use some more intelligent discs for data manipulation, or maybe some artificial intelligence as well. It needs more integration tools, so you can connect to different sources.
The solution is quite stable.
The solution is very scalable. The amount of people that use SSIS from our end depends on the project, so it varies. We increase the usage of this product based on the projects that we get. Basically, each project that we do, we use this solution for integration purposes.
Technical support is quite good.
I've always used SSIS. We never considered any other solution. We might have used some tools that were developed in-house occasionally, but by and large, we always use SSIS.
The initial setup was straightforward.
We use the on-premises version of the solution.
I would recommend the solution to others. I'd give it a rating of eight out of ten.
SSIS is a very flexible solution that allows data to be generated through code or external software. As a result, we can create reproducible patterns and improve code quality.
Because of the code generation, code quality improved and the time to develop decreased. This led to a quicker and more agile development phase.
It has the ability to be deployed into the cloud through Data Factory, and run completely as a software as a service in the cloud.
Metadata management. A change in the metadata source cripples the whole ETL process, requiring each module to be manually reopened.
We use SSIS for transformation and migration.
The most valuable feature of SSIS is that it can handle real complex transformations.
SSIS should be made a little bit more intuitive and user-friendly because it needs an expert-level person to work on it.
I have been using SSIS for more than 10 years.
SSIS is a stable solution.
SSIS is a scalable solution.
The solution's initial setup is easy, but you'd need expert-level knowledge to work on it.
Overall, I rate SSIS an eight out of ten.
First,
Great review and thanks for posting.
There are a few things you can do to lessen the crippling effect of a change to the source. Use variables to loosen the grip the source has, making it more dynamic.
I would agree that unless you have been doing this for years and are a top consultant in the field you wouldn't know this. You could also argue that it could be over verbalization and troubleshooting this can be a bear in SSIS.
Again Thanks for posting. Keep the reviews coming.
V/r,
Brian Dandeneau
CEO Applied Governance