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.
Blue Prism Cloud is an ideal cloud automation solution for organizations with a significant number of remote workers or geographically disparate teams since its accessible from any web browser. It is also beneficial for organizations that need to quickly outsource part of their process automation without having to purchase additional software licenses and equipment.
However, Blue Prism Cloud is less suited for companies that have large volume data processing needs as its base cost may quickly become prohibitive in those situations. Additionally, this solution may not be suitable for organizations that need more complex solution-specific configurations since its integration options are limited.
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.
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
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.
Usability wise the Blue Prism tool can be utilized to its 100% which include the control room, schedulers, work queues, Release managers, studio for process and object development, we use all the features in blue prism and is well suitable for the development and deployment, All the system are wisely controlled and connected the same SQL database and all the data can be accessed with ease and all the things can achieve in the systematic order.
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.
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.
Support is good and now with time online support in other forums is becoming available as well. Blue Prism support in itself is also good. Documents and blogs can help to find the solution. Since it's relatively new, sometimes if I'm stuck it can take time to find the solution or connect to their team.
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 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
Better User Interface.Better customer service.Easier to learn and use. But has greater risk compliances. Less preloaded automation. Less editing features and a big no while working on big projects. Fluidmesh is better in pricing and better management of multiple projects but I believe Blue Prism is perfect for beginners and small-scale companies.
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.
For a level of medium projects, Blue Prism performs well, and the speed of execution is good. In our organization, we are applying for medium projects, where we can increase the workforce of our employees.
Blue Prism's Client Server Architecture is good, because we need such a feature to implement automation.
When it comes to pricing, I personally feel that it is costlier.
