Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
N/A
Tableau Cloud
Score 8.0 out of 10
N/A
Tableau Cloud (formerly Tableau Online) is a self-service analytics platform that is fully hosted in the cloud. Tableau Cloud enables users to publish dashboards and invite colleagues to explore hidden opportunities with interactive visualizations and accurate data, from any browser or mobile device.
My work environment uses both Tableau Online, MicroStrategy & SSRS in parallel. Tableau is much closer to the SSRS in terms of visualization tool where as MicroStrategy is an enterprise data modeling and reporting tool.
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.
If you're using Tableau as the primary BI tool, then Tableau Cloud is well suited to publish and share the results with a wide(r) audience. It is well suited for various degrees of self-service proficiency, from pure consumers of analytical work to more advanced users who can use web editing for smaller or larger adjustments, and even for desktop power users who will publish their work to Tableau Cloud. It has many good ways to organize the content and make it easily accessible via search, favorites, folders, collections ("playlists for your data"), or history ("recents"). It might not be ideally suited if there are many on-prem sources to be used (even though there are options to connect them) or if you have very special requirements regarding custom server setup, which is limited in a shared cloud environment like Tableau Cloud.
Tableau Online is completely cloud based and that's why the reports and dashboards are accessible even on the go. One doesn't always need to access the office laptop to access the reports.
The visualizations are interactive and one can quickly change the level at which they want to view the information. For example, one person might be more interested in looking at the country level performances rather than client level. This is intuitive and one doesn't need to create multiple reports for the same.
The feature to ask questions in plain vanilla English language is great and helpful. For quick adhoc fact checks one can simply type what they are looking for and the Natural Language Programming algorithms under the hood parse the query, interpret it and then fetch the results accordingly in a visual form.
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.
Based on comments from our clients, I awarded it this grade. Non-technical customers frequently compliment us on the ease with which they can utilize Tableau Online. Usability is rarely a source of contention amongst our customers. Few complaints have come from me as a user of our internal products.
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.
I have not had any issues that require customer support from Tableau at this time, which speaks well to Tableau. I have taken an online course with Tableau and it was very professional and well done, so based on that I would assume a similar level of quality for their customer service.
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
In determining whether to go with Tableau Online versus Alteryx, two important factors stood out in determining our go-to solution. First, while Alteryx is an impressive tool for data cleansing, it did not stack up in terms of data visualization capabilities. Tableau, on the other hand, provided us everything we needed in terms of visualizing our data and analytics. The second factor is cost. Well neither solution would be considered cheap, Tableau was the more cost effective solution for our needs.
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.
