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
QlikView
Score 7.9 out of 10
N/A
QlikView® is Qlik®’s original BI offering designed primarily for shared business intelligence reports and data visualizations. It offers guided exploration and discovery, collaborative analytics for sharing insight, and agile development and deployment.
N/A
Pricing
MS SharePoint / SQL
QlikView
Editions & Modules
No answers on this topic
QlikView
Custom
per user
Offerings
Pricing Offerings
MS SharePoint / SQL
QlikView
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
On an perpetual license basis, based on server plus number of users.
Contact vendor for pricing.
The MS Sharepoint offers a more robust toolset for document storing and searching, using the file metadata. Also, it provides a support for workflow process, it can trigger action when a documents is added, changed etc. Sharepoint seems also better in versioning the documents. …
A simple and important scenario well suited is that you can configure alerts to notify you when the production server fails. another best feature is the report server is the central component of reporting services. For me something less appropriate is that the admin must ensure optimal performance for farm operations, they recommend that you install SQL Server on a dedicated server that does not run other farm roles and does not host databases for other applications.
Sales data validations have helped manage our justifications in the past, especially with regard to new product development and new business introduction. It has also been helpful in identifying trends with business impact and direction specific to quarter and monthly sales from ERP data as well as decisions to purchase equipment of staffing based on run rates and product demand.
One thing that can get out of hand is data output - if you aren't careful in your query, you may be overloaded with data dumps and drown in the amount of info you have to filter through. This is a user caution, not a comment on the software itself.
We found that QlikView can be a bit slow in supporting some forms of encryption. It is web-based and we needed to upgrade all of our server to not support the older SSL and TLS 1 protocols, only support TLS 1.2 and TLS 1.3. However, QlikView could not run with TLS 1.2 and TLS 1.3. We had to wait over six months to get a version that would handle the newer TLS versions.
There are so many options with QlikView that you can get lost when developing a visualization. There are still items I have not yet figured out, such as labeling a graph with the name of a selected detail item.
QlikView works by pulling the data it is going to use for visualization into its database. I am a security reviewer and I need to make certain that PII and PHI is not pulled by QlikView for a visualization, otherwise this could become a reportable indecent.
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.
Ease of use, ability to load from pretty much any data source. today I created an application that loaded time sheets from excel that are not in a table format. With Qlik's "enable transformation steps" I was able to automate loads of multiple spreadsheets and multiple tabs easily. Could not do that with any other tool.
SharePoint is very complex. This makes usability somewhat difficult from an IT perspective. An IT generalist will be able to pick it up and run with basic tasks. More customized functions would require significant specialized training and therefore limit what a standard user would be able to achieve. From an end user perspective, it's pretty straightforward to use.
QlikView is very easy to implement. The installation is very straight forward. QlikView has several different data connectors that can connect to different data sources very smoothly. The user interface to build the reports is very easy to understand. This helps to have a smaller learning curve. Something very helpful is that QlikView is a browser application for the end users. So, you don't need to install any applications on the user's computer.
It's been fantastic in terms of Premier Support so far. If there is an issue and if you report if the product has an issue, they will act upon it immediately. In some cases, if you design/develop something using the platform, Microsoft appreciates it and... publishes it on their public website. But you have to wait for some time if it is a non-Premier Support issue as you may experience delays.
My experience with the Qlik support team has been somewhat limited, but every interaction I have had with them has been very professional and I received a response quickly. Typically if there is a technical issue, our IT team will follow up. My inquiries are specific to product functionality, and Qlik has been very helpful in clarifying any questions I might have.
My team attended, but I cannot myself rate, but I think it was good as they've successfully launched a training program at our company themselves for users. It was 3-4 day training.
Training was as expected. The demo environments tend to be more fully featured that our own environment, but the training was clear and well delivered.
"Implementation" can mean a few things... so I'm not sure that this is the answer you want.... but here it goes: To me, implementation means: "Is the user interface intuitive and can I produce meaningful reports with ease?" On that score, I'd say YES. The amount of training required was minimal and the results were powerful. The desktop implementation is a simple, "blank" interface just waiting for your creativity. The pre-populated templates give you a reasonable start to any project -- and a good set of objects to "play around with" if you're just getting started. Finally, note that the "implementation" I used was baked into QuickBooks 2016 Enterprise -- called "Advanced Reporting"..... That integration makes it ultra useful and simple.
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.
The only other vendor product that I have worked with that provides a similar experience to Qlikview is Tableau. I would recommend Tableau if your use case is to build a fixed dashboard. You can share reports for free without needing to buy additional licenses. I would recommend Qlikview if your users are looking for a more interactive experience. They can create new objects to represent the data which can't be accomplished as easily in Tableau
I've installed SharePoint in many different industries and each industry has seen greater collaboration among their teams both locally and nationally. The ability to collaborate more efficiently has reduced the need to have employees centrally located.
Companies which have used SharePoint in a end user training portal have had great ROI, since they can create the content once and share with all their users who subscribe to their training service. The web content management aspect of SharePoint is a very helpful feature.
Generate quick reports for requirements that don't require complex calculations. ROI was fine, but Tableau software was much more intuitive for non-technical users on our team
When putting Qlikview reports side by side with Tableau, we ended up delivering Tableau reports since they were quicker to generate and required no technical expertise
