Azure Analysis Services delivers enterprise-grade BI semantic modeling capabilities with the scale, flexibility, and management benefits of the cloud. Azure Analysis Services helps transform complex data into actionable insights. Azure Analysis Services is built on the analytics engine in Microsoft SQL Server Analysis Services.
N/A
Looker
Score 8.2 out of 10
N/A
Looker is a BI application with an analytics-oriented application server that sits on top of relational data stores. It includes an end-user interface for exploring data, a reusable development paradigm for data discovery, and an API for supporting data in other systems.
We would have many technical issues and glitches with previous similar providers but found that Azure Analysis Services can simply handle our workload and memory better. I remember we lost an account due to cloud issues not fully saving or corrupting some files. Granted, this is rare with any cloud but haven't had that issue with the same load of memory with Azure Analysis Services.
Quick dashboards from Google Sheets - Easier to do the graphs than in Google Sheets - Operational dashboards to be used in the day-to-day work - It is good both for retrospective data and to do a pulse check of the current status - Better for not giant amounts of data and not multiple data sources. - If you need a lot of graphs to be displayed on the same page, it can be a bit glitchy during configuration (then the use works fine).
Providing role based access or we can say privilege based on the role to the user if it is integrated with Azure active directory and hence securing the access to sensitive data.
We use to run different type of analytics services to get the better result which is hectic if done manually or with human efforts.
We also use to collect bulk of data with the help of this tool and run customized test cases for better efficiency of result and better decision making. The result are very crucial and helps in taking big decision.
It supports different or we can say heterogeneous database vendors like the Oracle, SQL, and hence make the task easy.
Filtering - you can filter across different dimensions and metrics to get a more specific "cut" of data
Refreshing - data automatically ingests into Looker which allows reports to be updated and backfilled in real time
Conditional Reporting - you can leverage Looker's reporting features to flag when a given metric or KPI falls below or above a specified threshold. For example, if you had a daily sales benchmark in a SAAS organization, you could use Looker to flag whenever daily sales falls above or below the benchmark
Microsoft Azure Analysis Services is very costly solution and in that price we can get some better business intelligence tool with lot more of capabilities
The dashboard or we can say user interface is complex and need time to understand and gain expertise in order for proper working.
It needs continuation monitoring which is sometime a big task.
Sometime, the tool shows unusual behavior and become unstable, so we need to clear temp files for proper functioning.
Looker is less graphical or pictorial which makes it less attractive
Consumes a lot of memory when there are multiple rows and columns, impacts performance too
At times when we download huge chunks of raw data from Looker dashbords, the time taken to prepare the file is enormous - The user fails to understand if Looker has frozen or if the data is getting prepared in the background for downloading. In turn, user ends up triggering multiple downloads
We've been very happy with Looker so far, and all teams in the organization are starting to see its value, and use it on a frequent basis. It has quickly become our accessible "source of truth" for all data/metrics.
Looker is relatively easy to use, even as it is set up. The customers for the front-end only have issues with the initial setup for looker ml creations. Other "looks" are relatively easy to set up, depending on the ETL and the data which is coming into Looker on a regular basis.
Never had to work with support for issues. Any questions we had, they would respond promptly and clearly. The one-time setup was easy, by reading documentation. If the feature is not supported, they will add a feature request. In this case, LDAP support was requested over OKTA. They are looking into it.
The best thing about it is the ability to create a query and drill down the data to a more granular level when needed. The best thing about Azure Analysis Services is. It provides secured access anytime from anywhere, it also provides REST API for this, which is very easy to use, and it provides video tutorials for beginners means you get the whole package of learning and implementation!!
Looker is an off-the-shelf, free tool for Google business users. Other than the internal cost of time to build, we had no costs to set up what we needed to do. Knowledge sharing internally and using templates greatly reduced this cost, making the overall cost very low.
Allowing others to self-serve their own analytics and connect it to Looker simply and easily has helped unblock the central data team so they can instead focus on validated dashboards whilst stakeholders manage their day-to-day analysis themselves. Countless engineering hours have been freed up by not having to manage every user permission for each BI tool; we have a BYOBI approach; Bring Your Own BI
Creation and management of a semantic layer (LookML =Looker Modeling Language ) allows peoples sandboxes and production databases to become clutter free. Minor adjustments, conditional fields, and even some modelling can all be done in LookML which doesn't need oversight or governance from the central data team.
LookML, specifying drilldown fields and their sub-queries, as well as generally creating dynamic parameters with Liquid are all great features, but can have a steep learning curve. it may take some time to understand how to create this middle layer correctly, or even pose a risk of inheriting complex code from another source which can be unmaintainable if it becomes too big. Some level of governance is recommended if Looker is used by a large number of editors.
