Microsoft Power BI is a visualization and data discovery tool from Microsoft. It allows users to convert data into visuals and graphics, visually explore and analyze data, collaborate on interactive dashboards and reports, and scale across their organization with built-in governance and security.
$10
per month per user
SSIS
Score 7.4 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
N/A
Pricing
Microsoft Power BI
SQL Server Integration Services
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Microsoft Power BI
SSIS
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Microsoft Power BI
SQL Server Integration Services
Considered Both Products
Microsoft Power BI
Verified User
Contributor
Chose Microsoft Power BI
Both do a good job from a presentation layer. I feel that PowerBI has better data modeling capabilities, and Tableau has a slight edge on the visualizations and end-user experience. Power BI is more attractive to most of our B2B clients, and Tableau is more attractive for B2C …
Manager, Business Intelligence, Research and Analytics
Chose Microsoft Power BI
The primary reason why we selected Power BI is cost. Most enterprises have some sort of Microsoft or SQL Server licensing in place. Adding Power BI and the Microsoft infrastructure is a low-cost barrier to an existing license. Most other products came at a much higher price …
As mentioned earlier it is free of cost and easy to learn as it is part of the Microsoft suite product. It blends well with ETL package tools such as SSRS and SSIS. It is also easy to distribute the dashboard to users of Office 365. It is a a complete Microsoft product which …
I personally prefer SSIS. There are items that each do better than the others, but the ease of use of SSIS, along with its extensibility to 3rd party, ability to write any code required in the tool, and uses the same IDE for the MS BI suite (more of an issue if you're not a …
When looking to evaluate different options, we looked first to the experience and software we had in-house that would accomplish the job. When assessing alternatives outside we were looking for the tool that would offer the most flexibility.
SSIS and Denodo differ in their approaches to ETL and Data integrations. SSIS is more affordable from a cost and licensing perspective (if you have Microsoft licensing), but Denodo is no slouch. If you go with Denodo, you are not creating data, there are pros and cons to …
SAP Data Services is a very good tool and overall its easier to use than SSIS, but SAP is at a much higher price point than Microsoft. Microsoft can be a good fit for businesses of any size, but SAP tends to be a better fit for larger businesses.
Has significantly improved collation of data and visualisation especially with business across Europe. Has given me the ability to see the Site availability at the click of a button to see which Site is in the "money" and seize opportunities based on Market data
As I mentioned earlier SQL Server Integration Services is suitable if you want to manage data from different applications. It really helps in fetching the data and generating reports. Its automation make it very easy and time efficient. It works well with large database as well. But it doesn't work well with real time data, it will take some time to gather the real time data. I would not recommend using it in a real time/fast-paced environment.
Options for data source connections are immense. Not just which sources, but your options for *how* the data is brought in.
Constant updates (this is both good and bad at times).
User friendliness. I can get the data connections set up and draft some quick visuals, then release to the target audience and let them expand on it how they want to.
Connection managers for online data sources can be tricky to configure.
Performance tuning is an art form and trialing different data flow task options can be cumbersome. SSIS can do a better job of providing performance data including historical for monitoring.
Mapping destination using OLE DB command is difficult as destination columns are unnamed.
Excel or flat file connections are limited by version and type.
Microsoft Power BI is an excellent and scalable tool. It has a learning curve, but once you get past that, the sky is the limit and you can build from the most simple to the most complex dashboards. I have built everything from simple reports with only a few data points to complex reports with many pages and advanced filtering.
Some features should be revised or improved, some tools (using it with Visual Studio) of the toolbox should be less schematic and somewhat more flexible. Using for example, the CSV data import is still very old-fashioned and if the data format changes it requires a bit of manual labor to accept the new data structure
Automating reporting has reduced manual data processing by 50-70%, freeing up analysts for higher-value tasks. A finance team that previously spent 20+ hours per week on Excel-based reports now does it in minutes with Microsoft Power BI's automated Real-time dashboards have shortened decision cycles by 30-40%, enabling leadership to react quickly to sales trends, operational bottlenecks, and customer behavior.
SSIS is a great tool for most ETL needs. It has the 90% (or more) use cases covered and even in many of the use cases where it is not ideal SSIS can be extended via a .NET language to do the job well in a supportable way for almost any performance workload.
SQL Server Integration Services performance is dependent directly upon the resources provided to the system. In our environment, we allocated 6 nodes of 4 CPUs, 64GB each, running in parallel. Unfortunately, we had to ramp-up to such a robust environment to get the performance to where we needed it. Most of the reports are completed in a reasonable timeframe. However, in the case of slow running reports, it is often difficult if not impossible to cancel the report without killing the report instance or stopping the service.
It is a fantastic tool, you can do almost everything related with data and reports, it is a perfect substitutive of Power Point and Excel with a high evolution and flexibility, and also it is very friendly and easy to share. I think all companies should have Power BI (or other BI tool) in their software package and if they are in the MS Suite, for sure Power BI should be the one due to all the benefits of the MS ecosystem.
The support, when necessary, is excellent. But beyond that, it is very rarely necessary because the user community is so large, vibrant and knowledgable, a simple Google query or forum question can answer almost everything you want to know. You can also get prewritten script tasks with a variety of functionality that saves a lot of time.
The implementation may be different in each case, it is important to properly analyze all the existing infrastructure to understand the kind of work needed, the type of software used and the compatibility between these, the features that you want to exploit, to understand what is possible and which ones require integration with third-party tools
Microsoft Power BI is free. If I didn't want to create a custom platform (i.e. my organization insisted on an existing platform that I *had* to use), I'd use Microsoft Power BI. For any start-up or SMB, I'd just use Claude & Grok to build it quickly, also for free. Would not pay for Tableau or Sigma anymore. Not worth it at all.
I think SQL Server Integration Services is better suited for on-premises data movement and ADF is more suited for the cloud. Though ADF has more connectors, SQL Server Integration Services is more robust and has better functionality just because it has been around much longer
Without this, we would have to manually update a spreadsheet of our SQL Server inventory
We would also have poor alerting; if an instance was down we wouldn't know until it was reported by a user
We only have one other person who uses SQL Server Integration Services , he's the expert. It would fall to me without him and I would not enjoy being responsible for it.