Looker Studio is a data visualization platform that transforms data into meaningful presentations and dashboards with customized reporting tools.
$9
per month per user per project
MS SharePoint / SQL
Score 8.2 out of 10
N/A
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.
Looker Studio is well-suited for those wanting to analyze web/site data and performance quickly. It is simple enough to learn/use for quick report-building or drilling into data. Looker Studio is easier to use/understand than the GA4 console and thus has a better UI/UX. It is an efficient tool for fast, simple data needs—especially for team members with limited analytical capabilities and knowledge.
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.
It is the simplest and least expensive way for us to automate our reporting at this time. I like the ability to customize literally everything about each report, and the ability to send out reports automatically in emails. The only issue we have been having recently is a technical glitch in the automatic email report. Sadly, there is almost no support for this tool from Google, but is also free, so that is important to take into consideration
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.
Google Data Studio has a clean interface that follows a lot of UX best practices. It is fairly easy to pick up the first time you use it, and there is a lot of documentation on line to help troubleshoot, if needed
As stated in numerous slides before, asking the same question, SharePoint is the ideal software when working in a fast-paced, team-oriented environment. It is very easy to share large files (PDFs, documents, blueprints) and collaborate with team members inside and outside of our base office.
I give it a lower support rating because it seems like our Dev team hasn't gotten the support they need to set up our database to connect. Seems like we hit a roadblock and the project got put on pause for dev. That sucks for me because it is harder to get the dev team to focus on it if they don't get the help they need to set it up.
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.
The free version of Looker Studio is still better than the leading enterprise-embedded BI tools, despite its weaknesses. The leading embedded BI platforms have terrible visualizations that can be spotted a mile away. They are also primarily locked to a grid, making it very hard to fully customize. The price point is also a major deterrent, since users end up paying for lots of features they might never use. Looker Studio has weaknesses on the blending and modeling side, but we've been able to get by via connection to GBQ and transformation done in dbt.
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.