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 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.
The interface is very user-friendly.
It runs a little bit slowly, although this may be because of our laptops.
I would like to see better integration with Power BI.
The stability is okay. It is easy to support.
There are approximately 10 users. At this time, there are no plans to increase usage.
I have not used technical support. Instead, I read blogs and the support that is available online.
The initial setup is easy, and we did not find it complex.
Our in-house team was responsible for deployment.
I would rate this solution an eight 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 use this solution to ingest data to a data lake that is built on SQL Server.
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.
The most valuable features of this solution are the fast insert and fuzzy logic matching.
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.
Our primary use for this solution is to move data between points and applications.
This is a flexible tool to use and comes with the MSSQL server package.
This solution is easy to implement, has a wide variety of connectors, has support for Visual Basic, and supports the C language.
Tuning using this solution requires extensive expertise to improve performance.
This solution is included with the MSSQL server package.
We use this solution for extracting data from various databases and saving it in our data warehouse.
We use the on-premise deployment model.
My team is facing problems regarding the database connectors, which are not available. The MySQL connectors need to be purchased from outside vendors. They should provide connections for more SQL databases, free of charge.
The performance of this solution is not as good as other tools in the market. Compared to the same job is running in a different tool, it will take longer using SSIS.
This is a stable solution.
This solution is scalable.
The number of people I have using this solution depends on the size of the project. Normally, I need three to five ETL developers. Sometimes, if the project is big enough, then I will need more.
I have not contacted Microsoft Technical Support for this solution, although we have sometimes accessed the internet to research problems that we face.
In my previous company, I was leading a team who were working with Informatica. Here, they stick to Microsoft technologies and are unwilling to change.
The initial setup of this solution is very straightforward. In a few hours, everything was up and running.
The decision to use this particular solution includes many factors. Some companies do not want to purchase a license for another product because this one comes included with the database.
SSIS worked well for small or medium-sized Projects. For larger projects with huge data, I believe that you should search for another solution as you will need to do manual fine tuning. Additionally, some components such as SCD will show unexpected errors with huge data.
As Microsoft is very slow in providing updates and enhancements to SSIS, I see that the future for Integration projects in Saudi Arabia goes towards other vendors products such as Informatica powercenter, IBM DataStage, and Oracle ODI.
Compared to other Integration tools, I would rate it a six 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.
I'm using the solution primarily for e-memory and e-database calculation, mostly data blending (ETL) and massive table joining, etc. I also use it for data preparation and modeling.
With this solution, there is the potential to expand so that you can immediately write code onto the SQL server. Auto-parallelization is also critical for us. It decides automatically how many parallel sessions you have to run to get your query handled. You don't need to take care of any code, which is ideal. It's also highly scalable.
The solution should work on the GPU, graphical processing unit. There should also be a piping integration available.
The design of the dashboard isn't great, visually, but the solution works, so this isn't so important to me.
SSIS's competitor, Autonomous Database by Oracle, offers you, depending on the performance of the server, new hardware, should you update your software. It advises you on how to optimize your system. It's AI and works as an artificial database manager. Microsoft doesn't have anything like this yet, but it would be nice if they did.
The stability of the solution is perfect.
The solution is very scalable. We have approximately 25-30 users for the on-premises version, and our cloud version has around 5,000 users.
We don't ask for much from technical support. We utilize community information, and source answers via the internet or online user information. I do find that communicating with Oracle is much better.
We previously used Oracle as an integration tool, but it's much more expensive than Microsoft.
The initial setup was easy.
We had a consultant that assisted us with the implementation.
I use the private cloud as well as the on-premises version of the solution.
I would rate this solution eight out of ten. I would rate it higher if the solution offered full automation AI for database managing, setup and management, and scaling of the solution.

MySql connectors do not need to be purchased. Just use ado.net connector and ODBC. That's been a part of SSIS for a decade. I've used it for Mysql before without any issues. This is all well documented and available from many forums.