What advice do you have for others considering SSIS?

I would not recommend SSIS to other people because there are too many bugs, and it is unstable. I'd rate the solution five out of ten.

You need to be patient with the bugs and restart frequently. I rate the solution an eight out of ten.

It can be useful for data integration across different sources since it is a stable product. In terms of a complex data transformation process you've managed, the tool offers some accesses associated with integration services. The data warehousing capabilities of the tool benefited our company, and it is one of the good things about the solution because there are different databases that you can access throughout the process to collect information as you desire. Our company can recommend the tool depending on the client's requirements. We are using it for data warehousing and collecting some information from the database. Nowadays, there are probably different solutions that can do that efficiently and effectively. The debugging and error handling capabilities of the tool improves our company's data integration task but it is very challenging. The people who use the tool to work have mentioned that debugging issue is a bit difficult for them. I think it would be better if people could check out other solutions available in the market and compare them to SSIS. I rate the tool a seven out of ten.

I have managed a complex data transformation process in my company with the solution's transformation functions. Previously, I worked at my company with the data streaming destination in SSIS. For integration purposes, my company uses SSIS connection managers. With SSIS, I can also get data locally installed in Power BI and design the dashboard. I mostly rely on the dashboards provided by Power BI instead of SSIS. I use SSIS for the data integration process. I don't use Power BI that much for the data integration process. The data warehousing capabilities of SSIS are okay. If you are not using any product that offers integration services in your company, then you can start using SSIS for your organization's applications. The debugging and error handling capabilities improved our company's data integration task, as the tool helped me detect many issues. The benefit of the product is that there are a lot of online tutorials available about the tool. Users will not face any hurdles when trying to search for information about the product online. I rate the tool an eight out of ten.

I'd rate SSIS an 8 out of 10 for its overall performance. I would recommend SSIS for its ease of use. Whether you're a beginner or experienced, it's intuitive and allows for easy development of logic and infrastructure.

For those interested in SSIS, my advice is to go for it because it is a simple and effective solution. Even without deep knowledge, there are ample resources, including comprehensive documentation from Microsoft. Exploring their documentation provides access to numerous samples and best practices, making it user-friendly, especially for developers. So, don't hesitate to leverage the available materials and give it a try. Overall, I would rate SSIS as an eight out of ten.

Overall, I rate the solution an eight out of ten. There is room for improvement.

The solution is easy to maintain. SSIS is a handy tool but requires vast knowledge to build the pipeline using it. I advise others to go for SSIS if the user is versed in developing a pipeline. Otherwise, you can quickly build a pipeline using multiple user-friendly solutions. I rate the solution as a ten.

I rate SSIS six out of 10. SSIS can get the job done for bigger datasets. However, SQL Server lags if you're working with more than a terabyte or petabyte of data. I recommend exploring the tool because most of the video tutorials on the internet are outdated, and the official Microsoft documentation is geared toward advanced users. Beginners will have a hard time. You need a senior engineer to teach you, or you must explore the tool on your own.

We are end-users. The SQL version that we are using is 2019. However, I'm not sure about the exact version of SSIS we're using. We installed it with the 2019 version. I'd rate the solution eight out of ten.

I would definitely recommend SSIS and I would rate SSIS a seven on a scale of one to ten.

I was a user. If you want to perform some transformation or data warehouse and the product is used for data analysis purposes, it's a good option. You can perform some transformation, et cetera. I'd rate the solution eight out of ten. It was very useful for day-to-day tasks.

SSIS is best suited for small and medium companies. I would rate SSIS eight out of ten.

I would recommend SSIS to others who would be interested in using it. I would rate SSIS an eight out of ten.

My company is a Microsoft partner, and we use multiple Micorosft products. We're using the latest version of the solution. I'd recommend the solution to other users and companies. I'd rate the solution eight out of ten.

We highly recommend this solution as it is comparable with all of the major ETL software on the market. However, it should be noted that this is an enterprise class tool; it requires a team to be commissioned to do the proper development, there is a lot of standard documentation that comes with it, and a permanent team will be required to maintain it. So whilst it is a high-performing product, it requires a lot of commitment to optimize its use and capabilities. I would rate this solution a nine out of ten.

I rate SSIS seven out of 10. I would recommend using a cloud solution if possible, but if you need an on-prem product, SSIS is a good option. If you want to start using SSIS, there is a learning curve because SSIS isn't an easy solution to use. It's complicated, so you have to learn about the components and their functionalities to use them to meet your requirements.

I rate SSIS seven out of 10. This is the only product I've used so far, so I don't know how it compares to others.

This solution was one of the easiest versions to use compared to other vendors' solutions. I would recommend SSIS to others. I rate SSIS a nine out of ten. This solution has all the functions needed. It is a complete solution and they are always adding additional features.

If an organization has the money, I recommend they use Informatica. I would rate SSIS a seven out of 10 overall.

I rate SSIS eight out of 10. I would recommend it.

I rate SSIS nine out of 10.

I'm not a fan of SSIS itself. I would rate out-of-the-box SSIS a four out of 10, but with the ZappySys tool, it is a pretty good solution, and then I would rate it an eight out of 10.

In summary, this is a good product and I recommend it. For people that are working in a Microsoft environment with the SQL Server database, it's the most recommended tool. I would rate this solution an eight out of ten.

I rate SSIS eight out of 10. I recommend it.

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.

I would recommend this solution to others. I rate SSIS a nine out of ten.

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

I would rate this solution an eight out of ten.

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.

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

I would rate it a seven out of ten. Not a ten because of the data extraction that crashed. Tableau is better in this aspect. The transformation of data is very good in SSIS.

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.

I would recommend the solution. It's always worked for me and it's usually a top choice for my clients. I would rate this solution at seven or eight out of ten. It's not a perfect solution, but it works well.

In terms of advice I would give in regard to implementing this product, I'd say to examine your business needs in relation to the solution. You need to make sure those are met before implementing it. A lot of companies use data filers and they already have existing databases. You need to make sure the solution you choose is able to deal with old databases of client records. I would rate this solution ten out of ten.

If you have data needs and you are a small or medium enterprise this is a good solution. If you are an organization and you're not dealing with terabytes of data, but you still need to analyze data to make that decision, you should go with this solution. I would rate it a 7.5 out of ten.

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.

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.

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.

My advice for anybody who is considering this solution is to install the trial version first. You can get the SQL development edition, which pretty much has everything the enterprise edition has. You can download it, put it somewhere and use it as a development or testing area. Then, if you like it, look to purchase it. We're looking to move more to the cloud at some point. I don't know when, but we'll be doing more research before we do. Overall, I think for what this solution does, it's pretty much all there. I don't see any way or any changes that can be made to make it work faster, or easier. I know the tool inside out, so we know what to do with it. The other solutions that I have looked at appear to be very good in certain situations. These are good for specific information, for situations that cover everything. With SSIS, it is specific to SQL and what we do, but it's lacking in some things like logging. Monitoring itself, for example, is what is missing. I would rate this solution an eight out of ten.

My advice to anybody implementing this solution is to look into whether to use it on a catalog in a database, versus using package deployment. There are pros and cons to both approaches in terms of deployment and security. I would say that's something that needs to be evaluated quite early. There are lots of benefits to the catalog, but also a bit more admin attached to it. Another consideration is real-time processing needs. If this is a requirement then I would recommend against using this solution, unless the next version has a new set of features specifically for real-time processing. I would rate this solution an eight out of ten.

We're using the on-premises version of the solution. My only recommendation to those considering implementation of the solution would be, if they want to check data lineage, they should set up the packages with a particular configuration that they would have to follow in order to get data lineage. If they were to start it from scratch, my recommendation would be just to follow the pattern to ensure data lineage. I would rate this solution eight out of ten.

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.

Overall, I am quite satisfied with this product. I would rate this solution an eight out of ten.

We chose the solution because we have some data in Oracle and we wanted to extract it and load the data into SQL Server. The type of port, like SSIS, I always recommend other companies to use it and other Microsoft products because they are very easy to use. There are very handy tools. It's very user-friendly and has a good dashboard. I would rate the solution nine out of ten.