SSIS Reviews and Pricing - page 5

Try our new research platform with insights from 80,000+ expert users

Azeezulla Sheriff

General Manager IT at a manufacturing company with 10,001+ employees

Oct 6, 2022

Good SFTP connectivity but technical support could be better

Pros and Cons

"SSIS' best feature is SFTP connectivity."
"SSIS' best feature is SFTP connectivity."

"Microsoft's technical support has decreased in quality over the last few years, becoming less responsive and tending to pass problems on instead of solving them."
"Microsoft's technical support has decreased in quality over the last few years, becoming less responsive and tending to pass problems on instead of solving them."

What is our primary use case?

SSIS is mainly used for data migration transfer.

What is most valuable?

SSIS' best feature is SFTP connectivity.

What needs improvement?

In the next release, SSIS should include automated JSON file management.

What do I think about the stability of the solution?

SSIS is stable.

Free Report: SSIS Reviews and More

Learn what your peers think about SSIS. Get advice and tips from experienced pros sharing their opinions. Updated: February 2026.

884,976 professionals have used our research since 2012.

What do I think about the scalability of the solution?

SSIS is scalable.

How are customer service and support?

Microsoft's technical support has decreased in quality over the last few years, becoming less responsive and tending to pass problems on instead of solving them.

How was the initial setup?

The initial setup is straightforward.

What's my experience with pricing, setup cost, and licensing?

SSIS' licensing is a little high, but it gives good value for money.

What other advice do I have?

I'd give SSIS a rating of seven out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud

Disclosure: My company has a business relationship with this vendor other than being a customer. Partner

Syed Fahad Anwar - PeerSpot reviewer

Syed Fahad Anwar

Principal System Developer at DiwanDubai

Sep 21, 2022

It allows you the flexibility to write custom code, but it's difficult to use if you lack experience

Pros and Cons

"SSIS provides you with lookup and transformation functions, and you have the flexibility to write your own custom code."
"SSIS provides you with lookup and transformation functions, and you have the flexibility to write your own custom code."

"SSIS doesn't have a very good user interface, but if you can work with it, it'll provide you with almost all of the functionality."
"SSIS is not that scalable. You can scale it vertically to handle a high load, but it lacks horizontal scalability."

What is our primary use case?

We are using SSIS for ETL and ELT in a business intelligence context. We bring in data from different sources and use SSIS transform and load it into our intermediate database where we are developing dashboards. There are three people doing configuration and about 50 end-users.

What is most valuable?

SSIS provides you with lookup and transformation functions, and you have the flexibility to write your own custom code.

What needs improvement?

SSIS doesn't have a very good user interface, but if you can work with it, it'll provide you with almost all of the functionality.

For how long have I used the solution?

We have been using SSIS for four years now.

What do I think about the stability of the solution?

The SSIS is highly stable, but there are occasional issues with the script component.

What do I think about the scalability of the solution?

SSIS is not that scalable. You can scale it vertically to handle a high load, but it lacks horizontal scalability.

How are customer service and support?

Microsoft has some support for SSIS, but because the company is increasingly transitioning to the cloud, so these on-prem solutions are becoming obsolete.

How was the initial setup?

The initial setup isn't too difficult, but it's not easy. Sometimes, you may need help from a database administrator to set up the SQL Server Integration Services. It can take almost a day to deploy.

A database administrator can deploy it alone. You may need another person to develop the packages and set up ETL, so it's you need about two or three people for deployment in all.

What's my experience with pricing, setup cost, and licensing?

SSIS is included at no additional cost in the SQL Server license.

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Free Report: SSIS Reviews and More

Learn what your peers think about SSIS. Get advice and tips from experienced pros sharing their opinions. Updated: February 2026.

884,976 professionals have used our research since 2012.

Admin at IEC (Electoral Commission of South Africa)

Jun 22, 2022

It's easy to use, so you can spend less time and get more done

Pros and Cons

"The main value of any Microsoft product is the ease of use. You can achieve more with less time. That's what's beneficial for me. With many competitors, you might need to spend more time coming up with a solution because you have to focus on taking care of the product."
"The main value of any Microsoft product is the ease of use."

"It would be nice if you could run SSIS on other environments besides Windows."
"Microsoft support isn't helpful most of the time. We get most of our answers from forums."

What is our primary use case?

SSIS is helpful when you have tasks in a particular workflow that need to be completed on different schedules. You can start a specific task, and SSIS goes through the workflow to check a few things before it decides whether the task needs to proceed. Right now, maybe a quarter of the company is using it, but we plan to expand use in the future.

What is most valuable?

The main value of any Microsoft product is the ease of use. You can achieve more with less time. That's what's beneficial for me. With many competitors, you might need to spend more time coming up with a solution because you have to focus on taking care of the product.

What needs improvement?

It would be nice if you could run SSIS on other environments besides Windows.

For how long have I used the solution?

We use SSIS ad hoc when a problem arises that requires it. We've used it a few times over the last year.

What do I think about the stability of the solution?

SSIS is stable.

What do I think about the scalability of the solution?

SSIS is scalable.

How are customer service and support?

Microsoft support isn't helpful most of the time. We get most of our answers from forums.

How was the initial setup?

Installing SSIS is straightforward and takes an hour or two.

What about the implementation team?

We deployed SSIS in-house.

What was our ROI?

We've seen a return on using SSIS.

What's my experience with pricing, setup cost, and licensing?

An SQL Server license includes licenses for the database engine, reporting services, SSIS, and analysis services. That's the nice thing about this package. When you buy it, you get all of these different add-ons.

What other advice do I have?

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

Which deployment model are you using for this solution?

On-premises

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Anil Jha - PeerSpot reviewer

Director D&A at Iris Software Inc.

May 30, 2022

Integrates well with SQL servers, but technical support needs improvement

Pros and Cons

"SSIS integrates well with SQL servers and Microsoft products."

"I would like to see more features in terms of the integration with Azure Data Factory."

What is most valuable?

SSIS integrates well with SQL servers and Microsoft products.

From a cost perspective, it's a cheaper option than other ETL tools.

Also, it has a lot of in-built transformation, and it's easy to learn.

What needs improvement?

I would like to see more features in terms of the integration with Azure Data Factory.

For how long have I used the solution?

I've worked with this solution for about four years, on both the on-premises and cloud solutions. We had around 3000 plus users.

What do I think about the stability of the solution?

It's a stable solution.

How are customer service and support?

Technical support is not efficient, and I've had to search on the web to solve the problems.

Which solution did I use previously and why did I switch?

I worked on PowerCenter.

How was the initial setup?

The initial setup is straightforward and is not complex. It took about a day to install.

You would need two to three technical staff for the deployment and maintenance of the solution.

What about the implementation team?

We used an integrator for the deployment process.

What's my experience with pricing, setup cost, and licensing?

SSIS is a cheaper option compared to the cost of other ETL tools.

What other advice do I have?

SSIS is a cheaper solution, and I would recommend it.

On a scale from one to ten, I would rate it at seven.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Dominic Mackenzie

Data Architect at AMP Capital

May 20, 2022

It's easy to integrate data from various sources

Pros and Cons

"SSIS is an easy way to do data integration from various data sources. It doesn't matter whether it's a database, flat files, XML, or Web API. It can talk to the and join them all together."

"It's difficult to refactor SSIS. It gets cumbersome to reuse the solution."

What is our primary use case?

We use SSIS to integrate investment data we collect from different places into our portfolio management system. We get results out of portfolio management systems and integrate that into the downstream back-office, risk, and regulatory reporting systems. All the developers at my company use it.

What is most valuable?

SSIS is an easy way to do data integration from various data sources. It doesn't matter whether it's a database, flat files, XML, or Web API. It can talk to the and join them all together.

What needs improvement?

It's difficult to refactor SSIS. It gets cumbersome to reuse the solution.

For how long have I used the solution?

I have used SSIS off and on for maybe 15 years.

What do I think about the stability of the solution?

SSIS is stable.

What do I think about the scalability of the solution?

SSIS scales well

How are customer service and support?

I've never had any issues with SSIS, but I'm not responsible for managing the solution at an enterprise level.

Which solution did I use previously and why did I switch?

I've used free solutions or ones that allow you to create your own. I've used free ones like KNIME, etc. The open-source solutions have similar features, but I haven't found one with the same ease of use.

How was the initial setup?

I've never had to install SSIS at an enterprise level, but the installation is straightforward for development purposes. It takes less than an hour. However, installing it at the enterprise level would require a lot more configuration, tuning, etc. I'll leave that to the experts.

What's my experience with pricing, setup cost, and licensing?

We pay for a license, and I think SSIS is priced about right.

What other advice do I have?

I rate SSIS nine out of 10.

Which deployment model are you using for this solution?

On-premises

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Muhammad Arif Javed

Senior Manager Software Development at Techlogix

Nov 22, 2021

While you can build your own components, that is not straightforward

Pros and Cons

"The debugging capabilities are great, particularly during data flow execution. You can look into the data and see what's going on in the pipeline."
"SSIS is a tool which anybody can learn in no time."

"It should have other programming languages supported as well from a scripting perspective. Currently, only C# and VB.NET are supported, which limits it to .NET. It should have Java support as well."
"It should have other programming languages supported as well from a scripting perspective. Currently, only C# and VB.NET are supported, which limits it to .NET."

What is our primary use case?

We have used SSIS in many ways. Primarily, it has been used for building ETLs for populating data warehouse and staging areas. We have developed a number of data marts that were populated. We build data migration packages, which have been reused a number of times with minimal configurations. Additionally, we build complex data integrations solutions and data hand-offs between different applications. We have even used it for creating and parsing SWIFT messages for data integration purposes. We also used it for email triggers.

Now SSIS has introduced Big Data and cloud components. Though we haven't used any of these yet but it's really a very good addition to enhance SSIS capabilities.

How has it helped my organization?

SSIS is a tool which anybody can learn in no time. When we started the project, the whole team learnt it in one week's time and then were ready to start on project tasks. It gives you control. Recently, we used SSIS for a compliance project where we performed data cleansing and extensive data transformations to prepare data files for use of compliance (Trade Based AML solutions) application.

What is most valuable?

Script task and Script component for custom tasks: It gives you power to build your own logic if your requirements are not being fulfilled with existing available components. While the big thing is you can build your own components, that is not so straightforward.

It's visual design interface is good and you can easily understand the flow.

The debugging capabilities are great, particularly during data flow execution. You can look into the data and see what's going on in the pipeline. It has good logging capabilities as well.

What needs improvement?

It should have other programming languages supported as well from a scripting perspective. Currently, only C# and VB.NET are supported, which limits it to .NET. It should have Java support as well.

We couldn't explore big data related components, and this area should be up to the mark, if not already. Certain data quality checks should also be part of it. Currently, this is the biggest area that should be looked into. Data quality is an essential part of the integration process and ETL. Currently, only the data profiling task is there.

As an update, now SSIS offers big data components as well.

For how long have I used the solution?

5+ years.

What do I think about the stability of the solution?

I've been using it for last 7 years in different projects for different banks. Didn't face any stability issues yet.

What do I think about the scalability of the solution?

Yes. It's very much scalable, but it all depends on how you design your solution. SSIS provides you extensive features and toolkit to handle all sort of data problems.

Which solution did I use previously and why did I switch?

I also used Oracle Data Integrator as an ETL tool but it all depends on your need and customer preference. SSIS is being easy to use and things can be developed very quickly so I prefer to use SSIS for most of my data related tasks.

How was the initial setup?

Its setup is very easy. You don't need too many components to start building ETL tools. Plus, there are a lot of online learning available for this tool. It can be deployed on any Windows machine with minimal requirements.

What's my experience with pricing, setup cost, and licensing?

If you have SQL Server License then you can use SSIS without any additional cost.

What other advice do I have?

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

Which deployment model are you using for this solution?

On-premises

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Manjunath Bhimareddy - PeerSpot reviewer

Manjunath Bhimareddy

Project Lead Performance Engineer & Automation at Allstate

Sep 8, 2021

Stable, good technical support, and scalable

Pros and Cons

"The technical support is very good."
"With virtualization enabled we are able to scale horizontally."

"The solution could improve by having quicker release updates."
"The solution could improve by having quicker release updates."

What is our primary use case?

We are using SSIS for all of our relational database management systems (RDBMS) data.

What needs improvement?

The solution could improve by having quicker release updates.

For how long have I used the solution?

I have been using SSIS for approximately

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

The solution is scalable. With virtualization enabled we are able to scale horizontally.

We have approximately 2,000 users using this solution in our company.

How are customer service and technical support?

The technical support is very good.

Which solution did I use previously and why did I switch?

We have previously used Oracle.

What about the implementation team?

We have approximately 12 administrators and managers that do the implementation and maintenance of the solution.

What's my experience with pricing, setup cost, and licensing?

We have an enterprise license for this solution.

What other advice do I have?

I would recommend this solution to others.

I rate SSIS a nine out of ten.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Data Architect at World Vision

Aug 19, 2024

SSIS 2016 - The good, the bad, and the ugly

Pros and Cons

"Built in reports show package execution and messages. Logging can also be customized so only what is needed is logged. There is also an excellent logging replacement called BiXpress that provides both historical and real-time monitoring which is more efficient and much more robust than the built-in logging capabilities. And none of this requires custom coding to make it useful unlike many other ETL tools."

"You have to write push down join & lookup SQL to the database yourself via stored procedures or use of the SQL Task to get very high performance. That said, this is a common complaint for nearly all ETL tools on the market and those that offer an alternative such as Informatica offer them at a very expensive add-on price."

Sql Server Integration Services (SSIS) 2016 Review

SSIS 2019 - the Good the Bad, and the Ugly

SSIS is a unique ETL tool for a number of reasons. Most shops already own it but may treat it as a free utility rather than as an enterprise ETL tool. Which is ironic given it is superior to many of the supposed enterprise-class tools in a number of areas. The lack of respect in our industry is likely due to immature beginnings in its former "DTS" days and because it comes bundled "free" with Sql Server. But don't let that fool you into thinking it can't compete with the expensive ETL tools. I've used many ETL tools over the years and I'll take SSIS over any of them. I've now used SSIS exclusively for close to a decade and have no regrets.

SSIS is extremely flexible, extensible and integrated with many other Microsoft tools and a multitude of add-ons - both for purchase and for free. It's come a very long ways since its DTS days. It's incredibly cost effective, easy to learn the basics quickly (although like all ETL tools requires the traditional learning curve to get good at) and has an immense user base. There are also endless bits of quality shareware available that seamlessly plug-in and a wide variety of low priced vendor supported add-on products to fill in any out-of-the-box gaps (see my other review of MellissaData Data Quality MatchUp for SSIS). And if you can't find something you need and you know how to code C#.net you can extend the tool yourself. So unlike any other tool on the market, there's always a way to make something work with SSIS.

The Good...very good

How is free for a price? (for anyone running enterprise or BI editions of SqlServer)
Limitless Extensibility

This comes from the fact that SSIS is merely Visual Studio code and comes with templates to add your own custom components. A large variety of pre-built shareware is available at the codeplex.com website and vendors such as MellisaData and Pragmatic Works provide sophisticated add-on components from advanced realtime monitoring to state-of-the-art data quality plug-ins. BIML shareware allows for automated ETL code generation based on XML templates. Some of the shareware available on Codeplex are very high value such as the MultipleHash component providing very sophisticated hashing to support CDC and SCD operations. If you don't like out of the box functionality (such as the SCD wizard which is largely worthless) then there's likely a worthwhile supported replacement by some vendor for a reasonable price. There's built in support for CDC from many database sources such as Sql Server and Oracle for no added charge which is unheard of among their competitors.

Adding plug-ins such as BiXpress, Task Factory and DocXpress from Pragmatic Works are relatively inexpensive tools that do some really amazing things. BiXpress is a MUST for providing real-time and historical monitoring of ETL including tracking package parameter and local variable value changes both in real-time and historical. I highly recommend MelissaData Matchup for SSIS - you'll never see any other data quality tool as easy to use as that one which seamlessly integrates with SSIS.

Common Development Environment - Visual Studio

Unlike any other ETL tool - if you learn Visual Studio, you gain familiarity with an entire toolset. Its navigation and project organization is common to all other .net development. Along with Visual Studio you get all the source control plug-ins inherent with the tool such as TFS (aka. TFVC in VSO which is cloud based and free!), and Git.

Job/package Parameters

2012 Version introduced very flexible parameter capability superior to most all other ETL tools. Project and package parameters integrate seamlessly into Sql Agent to provide step-level dynamic change runtime values such as source/target connections. They of course can be used with many other job schedulers albeit a little less tightly integrated.

Endless Add-ons

Either via shareware or purchased products. Github provides a huge amount of free shareware code - some of which is very high quality. Vendors such as KingswaySoft and PragmaticWorks and many others provide multitude of inexpensive add-ons from adapters to enhanced components to connect to just about everything. I use SSIS to connect to Microsoft Dynamics CRM, Oracle Netsuite, on-prem Oracle, hosted source using SOAP calls, and Azure SqlServer as well as flat file loads and on-prem SqlServers.

Logging

Built in reports show package execution and messages. Logging can also be customized so only what is needed is logged. There is also an excellent logging replacement called BiXpress that provides both historical and real-time monitoring which is more efficient and much more robust than the built-in logging capabilities. And none of this requires custom coding to make it useful unlike many other ETL tools.

Extremely Large User Community

Just google if you don't know the answer - from youtube to blogs there's an incredible amount of information out there about this tool. I suspect far more than any other ETL tool.

List of good features...

Respectable Performance and includes a balanced distributor that allows for endless parallelism of data flow pipes
Robust historical repository reporting provided in the included SSISDB repository
Includes connectivity to large variety of sources/targets
Built in CDC for multiple sources (formerly a purchased add-on from Attunity). This feature alone is often 6 figure add-on from other vendors.
High value/low cost Data Quality component integrations from MelissaData
Sophisticated breakpoint debug capability including inside VB and C# scripts
Integration with Change Control Software (e.g. TFS, Subversion, Git)
Fully integrated with Sql Server Agent for scheduling including dynamic job step parameters
Integrates with SSAS tabular and cubes as well as Data Mining algorithms
Includes data profiling task and wizard
High level of sophistication with source/target drivers
Free Attunity OLEDB drivers for higher performance connections to Oracle and Teradata
Multiple plug-ins for interfacing with applications such as Salesforce.com and Dynamics CRM
Longevity of the tool and consistent support and enhancements by Microsoft
Full power of either VB or C# script tasks to accomplish pretty much anything that isn't already included

The Bad

No direct support for push-down of joins

You have to write push down join & lookup SQL to the database yourself via joins in the data flow source to get very high performance. That said, this is a common complaint for nearly all ETL tools on the market and those that offer an alternative such as Informatica offer them at a very expensive add-on price and even then don't work for all join situations. (My best practice is complex joins go into views of the data lake/landing area tables anyways so the queries are easily audible but I know there are deferring opinions here.)

Slowly Changing Dimension (SCD) Wizard has poor performance

No surprise here as this is a common issue with ETL SCD wizards. Requires custom/shareware enhanced wizard or one from 3rd party vendor to get good performance. This begs the question why Microsoft can't come up with a better wizard since it's pretty straight forward to code a dynamic merge as a workaround and someone wrote a much better shareware version. Pragmatic Works also sells a much better and supported version in their toolkit along with many other tools.

Here's a list of constraints or potential gotchas...

Expression Language primitive and inconsistent with other languages. The workaround is to use the script task that allows either VB or C# but using those inside of a dataflow severely degrades performance.
Limited native scalability - Direct support for multiple server/clustered installation/processing requires at least the 2016 version but I haven't yet tested this feature so I'm leaving this in as a constraint for now.
Flat file connectors are overly difficult to build and maintain - Changes in columns and file layout is cumbersome and problematic. Datatype detection is almost always wrong requiring manual settings for every column. Flat files that use quoted fields between delimiters don't work if a quote is included in the data - it can't find the field alignment and the data flow errors out. I know of no simple solution for this as it errors in the source before you can apply a cleansing function to it.
Default datatypes not always correct when reading from views. This can cause syntax errors in data flows and components such as union all. Workarounds are to explicitly convert in datatype conversion task or override the default metadata datatype.
Previous metadata often does not disappear when changing targets/sources. Tasks have the tendency to hold onto previous datatypes and lengths and not automatically pick up the changes. The tool cannot automatically adapt to metadata changes like some tools such as ADF.
Inconsistent data types for variables and parameters. Start with one set of datatypes coming from a database, combine with a completely different set of internal variable datatypes, another set with either Vb or C# variable datatypes when using script tasks, another set of datatypes when passing parameters to stored procedures, and yet another when applying SSIS expressions...and it's quite the mess in the end. You get it figured out eventually but it leaves you scratching your head asking why it has to be so difficult when it's all the same vendor's product. The C# and VB and database datatypes are a given but why can't the others follow one of those?
Confusing context/scope for variables to watch when running multiple levels of parent/child execution. Debug mode shows all of them at the same time and the context for each set is not intuitively obvious. For example you get list of each parent and child in the hierarchy of calls and its easy to mistake which package the variables relate to when viewing in the debugger.

10. Logging significantly impacts performance. You can customize logging however starting with 2016 version.

The Ugly

What's the future for SSIS?

Its only cloud capability is running it under the covers within SSIS-IR from ADF. The only decent monitoring tool for SSIS is BiXpress and it has now been deprecated! The writing is on the wall folks. The problem is ADF isn't architected to do a lot of small tasks efficiently like SSIS is. I have no way of testing this but based on my experience an attempt to re-engineer all our SSIS processes into ADF is likely to take our daily 6 hour process and turn it into couple of weeks. ADF just takes to long to move small amounts of data around. That leaves us limping by with SSIS and ADF in combination until such point someone provides a viable cloud alternative.

SSDT is still 32 bit!

Yup...and you thought this was the year 2022 and everything is 64 bit. Apparently Microsoft doesn't know that yet. Combine that with its tendency to not release memory and its not difficult to hit out of memory errors when doing SSIS development. But wait! There is finally hope on the horizon…VS 2022 is 64 bit now but no word on when SSDT/SSIS will be released for 2022.

So...

Here we go with more not-so-pretty "features"...

Development environment and deployment wizard becomes unstable with larger projects

It is not unusual to get "out of memory" errors IF you use the default deployment wizard which is 32 bit on even medium sized projects. However there is a 64 bit version that eliminates this issue but you have to realize that using it isn't the default.

SSDT (the development tool) keeps grabbing more memory as you open new solutions so you have to exit at least once a day to free up memory. SSDT is unstable if you open more than about 30 packages at a time (such as when you're applying framework code to a bunch of packages - you have to limit how many you do at a time).

Containers that help group tasks have several very annoying bugs. For example, sometimes if you attempt to resize the container it will make the diagram tool move about wildly and out of control. A task within a container sometimes becomes detached and you can't get it back into the container. This is common with sequence containers when you try to add a new task. The new task seemingly disappears but is actually behind the container. The workaround is to cut and paste it in but you may start to scream before you figure that out.

And if that's not enough, here's a very special feature for you to enjoy...If you change the "show annotation" on a precedence constraint when the constraint is using a package parameter, Pennywise the clown slaps you in the face, laughs and then SSDT dies. There is fortunately a workaround. You can make the constraint something generic like 1==1, change the show annotation again and then put the real constraint into it. In the end you walk away with satisfaction knowing you found a way to slap it back.

Prior to 2012 not recommended!

Prior versions had many issues including debugging instability with large parent-child package call volumes and .com locking issues when running many parallel threads. It's largest drawback however was it was WAY overly complicated with its configuration XML file method of passing data between packages. That said, it was still superior to ETL tools that require passing parameters via just files (such as Informatica)! But these issues were resolved with 2012 when they introduced project and package parameters and they also improved memory management for parent/child package calls.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

GaryMData Architect at a non-profit with 10,001+ employees

Report as inappropriate

May 5, 2020

The insight into running packages comes from the BiXpress Audit and Notification frameworks which are an extra cost per developer. But it's invaluable. And I would argue it gives you insight into what's running like no other tool on the market can. Its as if you were running a debugger in production as you can watch data values change in variables as it runs and data counts as the data flows run. And it handles all the error handling for you which is massive. It sends you formatted and informative email or text when something dies with where it died and why. There is some performance cost but you can turn off SSIS logging so its basically swapping logging methods and BiXpress is SO far superior to the built in logging of SSIS.

See all 6 comments

Buyer's Guide

Download our free SSIS Report and get advice and tips from experienced pros sharing their opinions.

Updated: February 2026

Product Categories

Data Integration

Buyer's Guide

Download our free SSIS Report and get advice and tips from experienced pros sharing their opinions.

Quick Links

Learn More:

Questions: