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.
User interface is easy to use, and in some ways better than Toad. The left hand side shows all databases, and you can drill down to instance, storage, schemas, tablespaces, and performance views. The right hand side displays the details of the selected object.
This is the best tool if you want to manage multiple RDBMS platforms in a single tool using the same familiar interface. Other third party tools can do it also, but it's not nearly as integrated as this, and may require additional plug-ins installed. DBArtisan excels at this, and can perform cross-platform data migrations easily.
It has different DB analysts, which can help diagnose issues with performance, optimize storage, detect fragmentation, and plan for capacity growth. For almost any action you want to take, you can generate the DDL for preview, and/or schedule it to run at a specific time.
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.
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.
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
It has a positive ROI on our organization. It's better than OEM and SQL Developer. Although the license could be expensive, it is perfect for large organizations, especially with multiple RDBMS platforms.
Most features are redundant between DBArtisan and Toad. I would not recommend using both if you already own one of them. Just download the trial for the one you're not using, and see what works best for your organization.
DBArtisan is great for DBAs and would be my personal preference. Toad is good for developers and DBAs alike but I feel like sometimes the interface is too busy and too clumsy to use.
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.
