Microsoft Power Automate vs. SQL Server Integration Services (SSIS)

If you are in a team that needs to develop automated solutions but have no coding experience and no access to a developer, Power Automate is one of the best places to start. It is incredibly flexible and likely has triggers and actions that can connect with your platforms, especially if you use the Microsoft stack. Additionally, using webhooks, you can connect to many different endpoints to get systems working together.

Incentivized

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.

Incentivized

• Sending confirmation email to clients and user once the flow is triggered.
• Fetching or Dumping files from one location to another if the flow is triggered.
• Schedule flow helps to send alerts and triggers the flow at a specific interval of time to carry out the required task.
• Power Automate also be used to convert any file format to a specific file format and save it to the required location

Incentivized

• Standard ETL use cases for daily loads
• Loading incoming data from Vendors which is placed on FTP and adding them to the SQL Warehouse
• Creating outgoing data files and writing them to Vendor FTPs
• Easy Active Directory integration for seamless connections to SQL Server
• CI/CD by hosting the code on visualstudio.com

Incentivized

• I REALLY wish I could just drop in a block of python or PowerShell code sometimes. The visual low-code things are great for moving around data but sometimes it would be faster if I could just tap out some code.
• The DOM (Document Object Model) is not entirely apparent and takes a lot of trial and error, and sometimes it's even different between different connectors. I would love to be able to just see the path to access some specific variables from earlier processes.

Incentivized

• 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.

Incentivized

The tool is very useful when used with its various native connectors, taking great advantage of the integration between the components and systems of the Office365 universe. However, its cost is still high, and automation using more advanced components containing AI resources becomes unfeasible for some companies. Due to the financial crisis that many companies are currently experiencing, investment in automation systems or tools is taking a back seat.

Incentivized

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

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

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)

Incentivized

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.

Incentivized

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

Incentivized

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 better one in a few years.

Incentivized

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

Incentivized

I have not done any participations

Incentivized

Microsoft's professional services provide hands-on support throughout the implementation lifecycle of Power Automate.This includes initial setup, configuration, integration with existing systems, testing, and deployment. They ensure that workflows are correctly designed, optimized for performance, and aligned with security best practices.

Incentivized

• It has encouraged everyday users to get a feel for low code no code without the detailed technical programmings skills
• This has encouraged the use of Power Automate to replace what was once an excel filled with complex macros and VBA!
• It has significantly saved time for someone like myself from chasing people for information and now I can create an auto alert using PA

Incentivized

• 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.

Incentivized