SSIS Reviews

Presently, we have decommissioned the solution. Earlier, we used SSIS with the SQL Server.

The most valuable feature of the solution is performance. It works by connecting to the SQL Server.

Integration and the user interface are areas with certain shortcomings that require some improvements.

I have been using SSIS for more than fifteen years.

Stability-wise, I rate the solution an eight out of ten.

It is not a scalable solution. You have to replace it.

There were five users of the tools in my company.

I have never contacted the solution's technical support team.

I have not used any other product that is similar to SSIS.

Some experts need to be involved in the deployment process, which is straightforward and easy to manage.

The product's setup phase was straightforward.

The product's deployment phase was easy.

People have to opt for a perpetual-based licensing model.

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 use the company's solution to build dashboards and back-end data integration with Microsoft SQL Server and Power BI.

The most valuable features of the solution stem from the convenience it offers, along with the ability to refresh data.

The product's stability needs improvement.

The high prices attached to the product can be an area of concern where improvements are required.

I have been using SSIS for two years.

The tool's stability is okay. Stability-wise, I rate the solution an eight out of ten.

There are three to four people in my company who use SSIS, and around twenty to thirty people are dashboard users.

My company has a database administrator, so we don't use the support provided by the solution in our company.

The efficiency of the deployment and management tools of SSIS is a bit technical, but it is alright since our company's technical support has hands-on experience with it, and they can deal with the deployment part in a very minimal amount of time.

The product's deployment phase is easy.

To deploy the product, I followed the solution's online tutorial and downloaded the tool to configure it.

If you don't want to pay a lot of money, you can go for SSIS, as its open-source version is available. When it comes to licensing, SSIS can be expensive.

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.

We have some business requirements, and we use this solution to create the machine tables, measures and APIs.

It is an easy solution but needs some improvement. The creation of the measure in the DAC's model could be improved.

We have been using this solution for two and a half years, and it is deployed on-premises.

We use this solution with Visual Studio. Sometimes we open certain files without making changes, and it saves the changes. In Visual Studio, while we're using TFS, it is easy to backtrack the changes, and we can undo them. However, those changes are pushed to another server if we are not alert and in a hurry.

It is scalable, and we haven't faced many issues. Sometimes, there are storage issues, but it is more of a DBA problem. We have a team in India and France and four people from the Eurofins team using this solution.

I have personally used the technical support and they are good.

The initial setup was easy, and we also used some YouTube videos for guidance. We use the latest version, and it is based on C Sharp.

I rate this solution an eight out of ten. Regarding advice, SSIS is good. However, everything is shifting to cloud, and in other organizations, everybody's moving to Azure which is much easier to use. We haven't worked with Azure, so I can't compare it to SSIS at this time.

SSIS (SQL Server Integration Services) is primarily an ETL tool. It's frequently used for data integration and transformation. In the past, we used it to integrate data into our systems. Microsoft is now focusing on Azure Data Factory for cloud solutions, but SSIS is still a viable on-premises option.

SSIS utilizes SQL Server Management Studio (SSMS) for management. I've used SSMS for many years and find it quite user-friendly, even for those new to SQL Server.

Being a Microsoft product, it integrates well with Visual Studio, a familiar development environment. It also has a graphical interface that displays the ETL process step-by-step. 

It's a familiar tool within the Microsoft ecosystem, which has its advantages. 

It lacked robust cloud integration and sometimes struggled with specific data types from sources.

Another area of improvement is performance. It has always been an issue. 

I used it for more than ten years.

It is a stable product. I would rate the stability an eight out of ten. 

I don't believe SSIS is a major development focus for Microsoft right now. Performance enhancements are always a concern.

Scalability mainly depends on the underlying SQL Server installation. A more powerful server can naturally handle larger data volumes. There might be performance bottlenecks specific to SSIS itself.

There are around two to three end users in my department. There might be more in the company. 

I usually resolve issues on my own.

The setup was easy. All Microsoft products are easy to set up. 

It comes with SQL Server. We didn't have a separate license for it.

It does its job. I'd probably rate it a six out of ten. Performance could be better.

SSIS is a good fit if you're heavily invested in on-premises Microsoft products. If you have a more diverse tech stack, better ETL tools might be available. Microsoft often limits how its products interact with others.

The use case is related to all reporting and transactions. On an hourly basis, we will pull the data for a few reports. Most of the time, it is a real-time integration between the applications.

Overall, it's a good product. I haven't had any issues with the product.

They can improve the solution in general. That said, I'm using around 30% to 40% of the SQL server. We have a separate team for the database administration site, so they probably have more of an idea of what needs to be improved.

We've had issues in terms of the amount of data that is transferred when we are scheduling. There are a few restrictions that we faced. In terms of the number of records, the limit can be increased. Sometimes what happens is not enough records are getting pulled, so sometimes the data is getting lost. After that, when the next schedule is running next time, the data is coming to our warehouse for data analysis. We need them to increase the limit of the data transfer on the schedule.

The initial setup was a bit difficult. 

I've been using the solution for seven or eight years.

The first time I attempted to deploy the solution, it was a bit difficult. However, it gets easier with time. 

I'd rate the ease of setup 6.5 out of ten in terms of ease of implementation. 

I don't do much on the deployment side and, therefore, can't speak to how long it takes to actually deploy.

We have around eight people on the solution working on the deployment in total. Around 5 are database administrators and there are three developers. 

I'm not sure which version of the solution I'm using. 

Before starting with SSIS, a person needs to understand the concepts of SSIS. They need some time to get comfortable with the product before jumping in. When I first started, I wasn't aware of a lot of things. Therefore, at first, it was a bit difficult. However, it gets easier with time. 

I'd rate the solution eight out of ten. It's flexible and very effective in terms of PLS skill programming. You can get real-time data from SSIS.

Mostly we are receiving files in either XML or Excel and then we collect them in databases. Sometimes it's CSV and sometimes it is also Excel. Mostly, it is XML.

We have many regulations that we must follow, and this solution helps us manage that. There are rules that we must follow, and we get files in a uniform structure, and we need to import them into databases. Doing it with SSIS saves us a lot of time.

The performance is better than doing it in some alternative ways. We don't have to worry about so much manual work. 

Mostly it was helping us with importing XML files by checking the access and then doing some look-ups and containers to implement loops and things like that mostly. That was quite helpful in terms of saving time. 

Technical support is helpful.

No big improvements are needed at this time. 

At one point, we did have to purchase an add-on.

Since we are not using it for a whole ETL, or for a data warehouse, maybe I'm missing something.

I've been using the solution for almost eight years. 

The performance is very good. It makes it easier to do things that you would have to do differently otherwise.

I'd rate the overall stability eight out of ten. We haven't had any stability issues in many years. 

The scalability is pretty good. I'd rate the ability to expand at a seven out of ten. 

There are only three of us using the solution at this time. 

We contacted technical support maybe once. I don't remember when it was, however, once, we had to look at some dump size, and we called Microsoft to help us with that. They did help us, however, it was a very long time ago and I don't remember too many details about the problem or experience. 

While we are using it quite a lot, my understanding is that the company will go with Talend and not SSIS for a data warehouse project. I don't have any influence on that.

That said, we are not going to do any conversion from SSIS to Talend on what exists in our existing project. The data warehouse will be a totally new project, and they will go with Talend.

We did not use any other solution previously.

The initial setup is very easy. I'd rate it an eight out of ten in terms of ease of implementation.

The deployment itself only took a couple of hours. 

The installation that comes with SQL just requires some tweaking with Visual Studio or something like that. We had some problems with maybe deploying the product from the local machine, however, in the end, we solved it.

We have three people handling the initial setup. All of us are DBAs.

We handled the initial setup ourselves, in-house.

There are occasionally add-ons for SSIS that may increase the price. 

In the past, we did not evaluate any other solutions. 

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. 

In my experience with SSIS, I have found its most valuable features to be its package management capabilities and the flexibility it offers in designing workflows. We often use templates, inheriting and embedding scales in SSAS to streamline our processes.

In upgrading SSIS, we encountered challenges fixing SQL Server and performance issues, including problems during a failover in our data warehouse. After resolving these issues and conducting load balancing tests, we proceeded with the SSIS upgrade, anticipating potential complications. 

I have been working with SSIS for almost ten years.

I would rate the stability of SSIS at a solid nine out of ten. While there may be occasional encounters with bugs or performance issues, personally, we haven't faced significant problems in our usage. 

I would recommend SSIS for both smaller and larger companies. We operate as a small to medium-sized enterprise with a considerable volume of data, around 30 to 40 terabytes in our data warehouse. Despite being an SME, SSIS has proven effective in handling our ETL processes seamlessly. If an organization has a similar data size, around the 30 to 40-terabyte range, SSIS can be a suitable and reliable choice for managing their data integration needs.

Microsoft's technical support has been good, especially for critical issues in a financial institution like a bank. The bank receives strong support from Microsoft, and there is a significant level of accountability. If any issues arise, particularly those impacting financial operations, Microsoft is obligated to address and resolve them promptly.

While executing tasks and managing data flow, we occasionally encounter Oracle system integration, and in the past, we have used Antunica, though it seems Microsoft's support for it has dwindled in recent years. Despite some versioning challenges, our workflow design, execution, and deployment have been relatively smooth using SSIS.

SSIS implementation has been straightforward for us, using scheduled tools like Kubernetes for deployment and master packages in SSIS. It seamlessly integrates with Microsoft products and other databases like Oracle or Teradata. We haven't faced issues integrating with third-party solutions, and even with tools like Attunity, it has worked reliably for almost a decade without performance problems.

The pricing of SSIS is generally considered reasonable in comparison to other data integration tools in the market. In terms of licensing, I find Microsoft's pricing policy generally favorable, especially when comparing it to other products like Power BI. Microsoft's pricing is competitive, and they seem to have a good strategy, as evident in the success of Power BI. Over the years, SSIS has gained recognition, and Microsoft's promotion efforts have been effective. 

If you are considering alternatives to SSIS, I have worked with ODI in the past during consulting engagements. Colleagues have praised Informatica as a superior solution to ODI and SSIS, though I'm not aware of its pricing. While SSIS is lauded for its simplicity, there might be disadvantages compared to competitors like Informatica. However, our data warehouse team is highly satisfied with SSIS, and it is widely used in the industry. It is a common and reliable ETL tool with easily accessible solutions through internal resources and online searches, making problem-solving straightforward.

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.

We are using SSIS for applications in development and in production. We have applications that need to have a database to support them and those applications need to have different integration with other applications.

The most valuable feature of SSIS is its ease of use. It is easier to use than other applications.

The performance of SSIS could improve when comparing it to Oracle Database.

I have been using SSIS for a long time.

SSIS is stable.

This solution is good for small-scale developments. We have approximately 80 people using the solution.

I have used the support from SSIS and I am satisfied.

I would recommend this solution to others.

I rate SSIS a seven out of ten.