MS SharePoint / SQL refers to Microsoft Sharepoint, a web-based collaborative platform, being used in tandem with Microsoft SQL Server to provide business intelligence analytics and reporting. They can provide BI content such as data connections, reports, scorecards, dashboards, and more.
N/A
Tableau Server
Score 8.0 out of 10
N/A
Tableau Server allows Tableau Desktop users to publish dashboards to a central server to be shared across their organizations. The product is designed to facilitate collaboration across the organization. It can be deployed on a server in the data center, or it can be deployed on a public cloud.
$12
Per User Per Month
Pricing
MS SharePoint / SQL
Tableau Server
Editions & Modules
No answers on this topic
Viewer
$12.00
Per User Per Month
Explorer
$35.00
Per User Per Month
Creator
$70.00
Per User Per Month
Offerings
Pricing Offerings
MS SharePoint / SQL
Tableau Server
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
MS SharePoint / SQL
Tableau Server
Features
MS SharePoint / SQL
Tableau Server
BI Standard Reporting
Comparison of BI Standard Reporting features of Product A and Product B
MS SharePoint / SQL
7.3
66 Ratings
11% below category average
Tableau Server
8.4
95 Ratings
3% above category average
Pixel Perfect reports
7.547 Ratings
9.129 Ratings
Customizable dashboards
7.363 Ratings
7.094 Ratings
Report Formatting Templates
7.056 Ratings
9.081 Ratings
Ad-hoc Reporting
Comparison of Ad-hoc Reporting features of Product A and Product B
MS SharePoint / SQL
7.1
61 Ratings
12% below category average
Tableau Server
7.8
95 Ratings
3% below category average
Drill-down analysis
6.450 Ratings
8.095 Ratings
Formatting capabilities
7.961 Ratings
8.093 Ratings
Integration with R or other statistical packages
6.236 Ratings
8.059 Ratings
Report sharing and collaboration
8.158 Ratings
7.089 Ratings
Report Output and Scheduling
Comparison of Report Output and Scheduling features of Product A and Product B
MS SharePoint / SQL
7.5
66 Ratings
9% below category average
Tableau Server
7.2
91 Ratings
13% below category average
Publish to Web
7.459 Ratings
8.085 Ratings
Publish to PDF
7.955 Ratings
7.084 Ratings
Report Versioning
7.555 Ratings
8.070 Ratings
Report Delivery Scheduling
7.145 Ratings
8.077 Ratings
Delivery to Remote Servers
7.438 Ratings
5.19 Ratings
Data Discovery and Visualization
Comparison of Data Discovery and Visualization features of Product A and Product B
As I mentioned in my previous answers, MS SharePoint is very useful as a shared drive for the organization and is very easy to manage. It also helps us import data from SharePoint directly into PowerBI for creating reports. According to my understanding, only share link features should be improved.
Whole funnel and specific channel performance from upper to lower funnel metrics. The ability to view full channel performance for some time, such as weekly, monthly, or quarterly, has truly been monumental in how my team optimizes specific channels and campaigns. Daily performance tracking is a bit overwhelming, with load times and having to refresh specific live views over time. It can be challenging to do so at times, as extensive dashboards take much longer to load.
It's good at doing what it is designed for: accessing visualizations without having to download and open a workbook in Tableau Desktop. The latter would be a very inefficient method for sharing our metrics, so I am glad that we have Tableau Server to serve this function.
Publishing to Tableau Server is quick and easy. Just a few clicks from Tableau Desktop and a few seconds of publishing through an average speed network, and the new visualizations are live!
Seeing details on who has viewed the visualization and when. This is something particularly useful to me for trying to drive adoption of some new pages, so I really appreciate the granularity provided in Tableau Server
Tableau Server has had some issue handling some of our larger data sets. Our extract refreshes fail intermittently with no obvious error that we can fix
Tableau Server has been hard to work with before they launched their new Rest API, which is also a little tricky to work with
This was a long-term buy-in from a corporate perspective, to remain in the SharePoint space. Migration is certainly possible, which is good for planning and having options further out. At this point, the only planned migration is to eventually move the architecture up to SharePoint/SQL 2013. At that point, we will be able to leverage some greater efficiencies, some enhanced content design and management features, and some more current social features. It is well worth a full consideration in any shop looking at a new implementation of or migration to SharePoint (although you will probably be considering 2013 versions or beyond in those discussions), but the platform should be a strong competitor to any alternatives. Realizing the capability of a fully-branded and customized website was not part of the original choice for the architecture at Lincoln, but seeing it implemented and functioning now with this capacity far beyond original expectations has certainly cemented plans to continue using it.
It simply is used all the time by more and more people. Migrating to something else would involve lots of work and lots of training. The renewal fee being fair, it simply isn't worth migrating to a different tool for now.
I gave this rating due to MS SharePoint being a big help with our userbase. We have a lot of users that are just old enough to not have much technical skills or they have been in this industry long enough to where they haven't really needed to utilize much technology. MS SharePoint helped us move beyond that barrier without too many bumps and bruises.
Tableau Server takes training and experience in order to unlock the application's full potential. This is best handled by a qualified data scientist or data analytics manager. Tableau user interface layout, nomenclature, and command structure take time and training to become proficient with. Integration and connectivity require proper IT developer support.
Our instance of Tableau Server was hosted on premises (I believe all instances are) so if there were any outages it was normally due to scheduled maintenance on our end. If the Tableau server ever went down, a quick restart solved most issues
While there are definitely cases where a user can do things that will make a particular worksheet or dashboard run slowly, overall the performance is extremely fast. The user experience of exploratory analysis particularly shines, there's nothing out there with the polish of Tableau.
I've only had to call in to support on one occasion but they were able to work though our issue and find a solution that did fully resolve the issue in a timely manner. I can't always say the same about support from other companies so it was a refreshing change to have support that did help.
We have consistently had highly satisfactory results every time we've reached out for help. Our contractor, used for Tableau server maintenance and dashboard development is very technically skilled. When he hits a roadblock on how to do something with Tableau, the support staff have provided timely and useful guidance. He frequently compares it to Cognos and says that while Cognos has capabilities Tableau doesn't, the bottom line value for us is a no-brainer
In our case, they hired a private third party consultant to train our dept. It was extremely boring and felt like it dragged on. Everything I learned was self taught so I was not really paying attention. But I do think that you can easily spend a week on the tool and go over every nook and cranny. We only had the consultant in for a day or two.
The Tableau website is full of videos that you can follow at your own pace. As a very small company with a Tableau install, access to these free resources was incredibly useful to allowing me to implement Tableau to its potential in a reasonable and proportionate manner.
Implementation was over the phone with the vendor, and did not go particularly well. Again, think this was our fault as our integration and IT oversight was poor, and we made errors. Would they have happened had a vendor been onsite? Not sure, probably not, but we probably wouldn't have paid for that either
At the time of the two large projects, SharePoint was the enterprise solution so we were required to use that. We have since lobbied the enterprise teams to review and consider Atlassian Confluence and were successful. Confluence is cheaper than Sharepoint which is why we wanted to bring that in. The enterprise has now made Confluence an enterprise solution as an alternative to SharePoint. After using both I think SharePoint has many more add-ins than Confluence. It has much more customization ability than Confluence. SharePoint is not good for mobile readiness. Confluence is so there is a difference that might lead you to Confluence over SharePoint. I would also say that SharePoint is very document-centric and that Confluence has better KM than SharePoint does. even with the use of SQL Server. We were told that we could not use Google Drive even though it had features we liked.
Today, if my shop is largely Microsoft-centric, I would be hard pressed to choose a product other than Power BI. Tableau was the visualization leader for years, but Microsoft has caught up with them in many areas, and surpassed them in some. Its ability to source, transform, and model data is superior to Tableau. Tableau still has the lead in some visualizations, but Power BI's rise is evidenced by its ever-increasing position in the leadership section of the Gartner Magic Quadrant.
Tableau does take dedicated FTE to create and analyze the data. It's too complex (and powerful) a product not to have someone dedicated to developing with it.
There are some significant setup for the server product.
Once sever setup is complete, it's largely "fire and forget" until an update is necessary. The server update process is cumbersome.