Microsoft Power Automate is an advanced automation platform offering a range of features, including AI-powered automation, robotic process automation (RPA), business process automation (BPA), digital process automation (DPA), and process/task mining. The platform aims to empower organizations to securely automate their operations at scale by leveraging low-code and AI technologies.
$15
per month per user
SSIS
Score 8.0 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
N/A
Pricing
Microsoft Power Automate
SQL Server Integration Services (SSIS)
Editions & Modules
Power Automate Premium
$15
per month per user
Power Automate Process
$150
per month per bot
Hosted RPA add-on
$215
per month per bot
Process Mining add-on
$5,000
per month per tenant
No answers on this topic
Offerings
Pricing Offerings
Microsoft Power Automate
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 Automate
SQL Server Integration Services (SSIS)
Considered Both Products
Microsoft Power Automate
Verified User
Anonymous
Chose Microsoft Power Automate
Microsoft Power Automate is defintitely more business user friendly and citizen developer friendly. It doesn't require knowledge of Javascript, etc. Just simple drag and drop interface.
I have evaluated Microsoft Power Automate against other workflow automation options, including Nintex, Joget, and custom-built solutions. Overall, Power Automate provided the best balance of integration, cost, speed, and governance for our needs. Power Automate is Low-code, …
We are using Microsoft Power Automate alongside other tools, always judging the automation scenario, necessities and limitations. Compared to UiPath e. g. Microsoft Power Automate does not offer the same customizing abilities. However it is much more advanced considering the …
In our experience, Microsoft Power Automate fails with throttling and became unusable to meet our client deadlines. Nintex did not experience throttling issues for us.
Power Automate can do many things that most platforms can't do as a 'citizen-developer' with no access to coding tools and deployment. It allows you to develop and deploy low/no-cost automation flows quickly. The blocks in Powert Automate do the API work for you, where you only …
SharePoint Designer was discontinued and was limited in functionality, being as old as it was. Nintex was powerful, but at the time we were using it, it was primarilly tied to SharePoint, and we wanted to do more outside of SharePoint as well. And Tibco Integration (Scribe) was …
Firstly, it came with organizational license, so it was available to everyone, for some of the automations that we're not able to do so when we took license for other tools it was more difficult and tedious to do hence, we had to shift back to Microsoft Power Automate. License …
Microsoft Power Automate is worlds ahead of Zapier in so many ways. The looping, DOM access, and flow controls are much better. I feel that accessing different data within previous connectors used in a flow is much easier in Microsoft Power Automate as well.
The Microsoft Power Automate have the browser based access which doesn't require any tool installation separately. Whereas for the Uipath, many dependencies are needed for the flows. We need to purchase the separate License for the UiPath but in case of the Power Automate, it …
I have only used Microsoft Power Automate as our organization is using microsoft ecosystem and i can access its features easily. With new features it is sufficient enough for my use as if now. I would recommend it for those who are in microsoft ecosystem to use it is capable …
I have many years of experience with Nintex applications and it stands up very well against Microsoft Power Automate. I hope Microsoft Power Automate can become the better workflow application. With the Integrated AI builder and continuous updates I expect they can become the …
Power Automate beats UiPath basically from a costing perspective. I prefer Power Automate over UiPath because of its different costing segments that make it way cheaper than UiPath.
SmartSheet provides a number of functions when it comes to dealing with and showcasing tabular …
User Interface and Ease of Use, Integration Capabilities, Bot Development, Cognitive Services and AI Integration, Scalability, Pricing, Community and Support. The most thing that Power Automate stands out from others is the Pricing models as it is way more cheap than Automation …
UIPath allows for automation of saving email attachments but the time required to create this automation is a great deal longer than Microsoft Power Automate.
Microsoft Power Automate is a Low-Code,No-Code approach making it easy for a beginner to learn and understand. The integration with microsoft ecosystem is an advantage. The cost is less when compared to uipath. There are pre built templates available and the AI integration is …
Microsoft Power Automate is the platform we can say very user friendly You need not to know the coding and programme you just need to enter the flow you wanted and you are set . You no need lengthy program and eventually no time is required. Very productive tool we are using …
Both are very similar. Azure is cloud based. It is easier for the organization who uses cloud based application. The SQL Server Integration Services is cost effective. Azure was more on the expensive side for our organization. Azure was a little complex, it needed special …
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
Fivetran, Stitch, and Etleap are all 1000x more modern than SSIS and 100x less aggravating. While those tools are mainly used to sync data rather than transform it, the ELT model works much better than the ETL model in most situations.
We just selected SSIS because we use SQL Server Management System (SSMS) to manage our database. As SSIS is a component of the Microsoft SQL Server there are no problems with integration and everything works perfectly. In addition, we don't have to learn how to use another …
Low-cost relative to other products - in fact, zero cost if one is considering the license cost as being for the database engine with Integration Services added on. It has a comparable range of functionality and performance and as such it's a 'no-brainer' to use SSIS over …
SnapLogic and Azure Data Factory are better than SQL Server Integration Services mostly because they are Integration Platform as a Service (IPAAS) services, whereas SQL Server Integration Services is an on-premise. So the basic differences such as, need a VPN to connect to the …
SSIS is similar to Alteryx and Informatica PowerCenter in a way because these are all drag-and-drop ETL tools with similar functionality. Alteryx is a step ahead because it has some advanced ETL functionalities including statistical calculations etc. and a better ability to set …
Alteryx Designer is easier to use for machine learning models. The functionality of drag and drop is the most valuable. It is a very user-friendly tool that can be understood easily. My teams also work with other solutions, such as Integration Services, and these solutions are …
I had nothing to do with the choice or install. I assume it was made because it's easy to integrate with our SQL Server environment and free. I'm not sure of any other enterprise level solution that would solve this problem, but I would likely have approached it with …
SAP Business Objects was a primary concurrent software against the MS SSIS but it has a more steep learning curve and requires additional investment into the SAP-related software infrastructure. With SSIS one can start easily with simple data extraction / DTL tools of Express …
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 …
I used the Pentaho Data Integration (PDI) ETL tool. The PDI ETL tool does not have a public user collection like the SQL Server Integration Services(SSIS) ETL tool. Therefore, you may not be able to find instant solutions for your problems. But it has advantages over the SSIS …
SQL Server is already in our wheelhouse so it only made sense to utilize the tools we already had available to us--SSIS, SSAS, & SSRS. Other non-technical users seem to be more comfortable using alternatives to SSIS. However, these alternatives are not as good as SSIS at …
These are all great products and, honestly, can move data faster. They include more enterprise features and have some great qualities about each. However, they all cost a lot depending on the implementation you need. With SQL Server Integration Services, you do not have any …
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.
It’s basically a free tool and it has more features than anyone would ever need. If you look online for answers for SISS packages you will find a world of information that can cover almost any situation for your business. This tool can be used in any business and it provides …
SSIS is a very basic, developer-oriented ETL tool and while it lacks many of the nice UX features of its competitors it is a powerful tool that comes as a part of SQL Server and, in the hands of experienced developers with domain knowledge, can meet most organizations' ETL …
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 …
SQL Server Integration Services does a good job for our SQL Server environments and was selected for that reason. For a SQL Server-only implementations, I would recommend SQL Server Integration Services. When we compared SSIS to other ETL providers against SQL Server, SSIS was …
Very useful RPA tools for automating processes with minimal coding and drag-and-drop functionality, with a wide variety of triggers, including scheduled time-based triggers and activity-based triggers, such as modifying a file/list in SharePoint to run a Power Automate flow. Very easy-to-use UI with native integration with every Microsoft product, and a very low automation failure rate for deployed workflows.
Ideal for daily standard ETL use cases whether the data is sourced from / transferred to the native connectors (like SQL Server) or FTP. Best if the company uses MS suite of tools. There are better options in the market for chaining tasks where you want a custom flow of executions depending on the outcome of each process or if you want advanced functionality like API connections, etc.
Power Automate is a great product that has a vast array of options on how to use it. Your imagination is the only hurdle with using Power Automate as there is no limit to what can be done with the system. It has brought a lot of value to our business through the use of custom systems, connectors, and streamlining processes.
SSIS is responsible for running core business processed managing core business data. It can be managed, improved and expanded using minimal internal resources. It is also able to support all of our current data infrastructure. Replacing SSIS would be time consuming and costly with no apparent ROI.
Power Automate features a clean and intuitive user interface that allows users to create, manage, and monitor workflows easily. The UI is designed to be accessible to both technical and non-technical users, with drag-and-drop functionality for building workflows. Power Automate supports integration with a wide range of Microsoft and third-party applications. This flexibility in integration allows users to automate workflows across various systems, enhancing overall productivity and efficiency.
It is easy to learn, works great on many features, but needs improvement on ETL troubleshooting and performance monitoring functionality. Great tool on Microsoft stack. it is great with simple, structured datasets. Once logic gets fancy like nested conditionals complex joins, reusable transformations, versioned logic …SQL Server Integration Services (SSIS) packages become hard to read and harder to maintain. Source control is painful. Errors can be cryptic Logging takes effort to set up well Debugging in production is limited.
Raw performance is great. At times, depending on the machine you are using for development, the IDE can have issues. Deploying projects is very easy and the tool set they give you to monitor jobs out of the box is decent. If you do very much with it you will have to write into your projects performance tracking though.
both Community support and Microsoft official support typically respond to (and resolve) reported issues in a VERY expedient manner, usually going above and beyond for education and bugfixing. I have been thoroughly impressed with the level of support I had been provided in the past.
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.
after reviewing the main features of Power Automate, the Microsoft trainer focused on some of our real life use cases implementation, from simple to more advanced.
although it was productive, it is more difficult to stay focused and in a 7 hours a day online training (including screen share issues and the fact that the trainer just can't precisely show the exact location of your mistake)
I was part of the migration of classic SharePoint workflows and Nintex workflows. We didn't spend much time learning the new platform because of its user-friendly interface and intuitive drag-and-drop functionality. We have mostly O365 E1 and E3 licensed users, so they can participate in our Citizen Development program and utilize Power Automate to build day-to-day business processes.
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
I have evaluated Microsoft Power Automate against other workflow automation options, including Nintex, Joget, and custom-built solutions. Overall, Power Automate provided the best balance of integration, cost, speed, and governance for our needs. Power Automate is Low-code, rapid development, minimal maintenance, faster changes, and iteration. Compared with Nintex, Power Automate has a strong workflow designer, lower licensing and operational costs, a separate vendor ecosystem, but Power Automate has Native Microsoft 365 integration, included or incremental licensing, and a strong roadmap with AI and Copilot.
Both are very similar. Azure is cloud based. It is easier for the organization who uses cloud based application. The SQL Server Integration Services is cost effective. Azure was more on the expensive side for our organization. Azure was a little complex, it needed special training to use it. Azure was not accurate with complex data.
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.