Microsoft Azure Synapse Analytics Reviews

Our primary use case for Azure Synapse is as a data warehouse, for creation of data pipelines. It allows login into to one central workspace, manage our databases, and the entire warehouse. We can embed business intelligence (BI), using Power BI. This allows us to show visualizations all in one central place.

I think potential areas to improve on could be performance and if they offered a decoupled compute from storage kind of service that would be nice. But I don't think that is possible as it's a fundamental change in the underlying architecture and Microsoft won't make that decision easily. 

We have been using Microsoft Azure technology for the last 4-5 years, including Synapse.

As Synapse is hosted on the Azure cloud, it's very stable. 

The Azure Synapse service is highly scalable. 

The initial setup is very straight forward. Azure Synapse offers you one workspace where you can do everything, creation of your data warehouse, ETL pipelines using Azure Data Factory, Create storage and data marts. Also use Power BI for visualization. 

Before Synapse was available, all of these was offered as separate services and this is how a data warehouse was constructed. Synapse is one layer on top of this where we make use of one single workspace to initiate and manage the entire set of services that you need for creating and managing your data platform - Data Warehouses and marts using SQL Warehouse, ETL pipelines using Azure Data Factory, Data Lake using Azure Blob Storage, and it offers server-less SQL - meaning you can run queries without having to initiate an SQL database or SQL data warehouse instance. It also offers Spark compute to process non-structured data.

We are a Microsoft partner and have setup and built Azure Synapse based solutions for our manufacturing, energy and healthcare clients. We are very customer centric and build and manage solutions based on our clients needs. We recommend what the best technology stack is for them. 

If I hosted a Microsoft setup on premise, I would need to invest in licensing for different tools and services, SQL server, SSIS, SSRS, Power BI or SSAS. Compared to this if you use Azure Synapse, the return on investment is very high. You get rid of your hardware, licensing and you move to a subscription based pay as you use model. Your operational costs reduce and your optimization increases. Capital expenditure absolutely diminishes and you move to an OpEx model. 

Finally, the overall management of it is simplified as compared to on premise. This of course leads to high RoI. 

Azure Synapse is best for people who are already invested in Microsoft technologies, in particular those who already use Microsoft data warehousing services, including MS SQL-Server based data warehouse technology. For them, migrating to Azure is very straight forward and Synapse adoption stays easy. 

With Azure Synapse, there is no database installation, no licensing cost, no hardware setup, everything is available as a cloud service, you then pay for the service, pay only for what you use. 

With regards to pricing, as I said you pay for what you use. The amount of data you store and compute power contributes to your pricing. If I use Azure's blob storage, the pricing depends on how much I use. If I utilize Azure Data Factory, pricing depends on how much data I process through the ETL pipelines and so on.

For some customers we recommend Snowflake, for others Azure Synapse or Google BigQuery. In one of our cases we are building a solution with both Azure Synapse and Snowflake. 

We have approximately 20-25 team members with knowledge of Azure Synapse service capabilities. 

With regards to deployment and maintenance, an Azure Synapse based solution may need anywhere between 3-15 people. This depends on what type of warehouse and analytics you want to create, the number of reports and visualization. Typically a small team size would be of 3-4 people and a large team size would be of around 12-14 members.

The solution offers great flexibility and the resource availability is quite good. It's abundant in the market. 

The initial setup is very simple.

The only concern for us is the cost part. When it comes to the implementation and the support and maintenance, we see high-cost implications.

Of course, it varies from use case to use case. Before we get into the implementation part, we have to validate the pros and cons of the architectural components as part of the design and development. Once that's clear, then we'll go for implementation. We might get into technical glitches, however, there are multiple ways to work around them by putting in the right architectural component, which can solve the problem. There is always a workaround.

We've had a couple of interactive sessions with Microsoft already. We have already recommended that they need to strengthen their presence in the data governance part, the data quality part, and then the metadata management, for example, data lineage. We need more data governance to give the flexibility to handle these data quality issues.

It would be great if they update their data features. 

We have been working with the solution for the past one and a half years.

The solution is mostly stable, however, we do experience glitches here and there. We do have solutions that ultimately correct the issue.

Azure cloud is very scalable and allows this product to scale as well. We can scale horizontally and vertically.

Technical support is so far, pretty good. It's solving the problem now. Some other clouds are coming in, such as AWS or Google Cloud. They'll eventually be much more competitive in terms of comparatively.

We have used hybrid architecture also. We used the storage part and we have used Snowflake also. Everything is available in one place so that the connectivity issues are solved and you get one component talking to everything. 

It's a very simple setup. it's not overly difficult at all. 

In terms of maintenance, it depends on the scope of coverage and other things. If it is a 24 by 7, we need a set of 14. Depending upon the service coverage and scope coverage, you'll need a certain amount of people. Even that depends upon the scope of the work also. Does the setup require monitoring, for example, or enhancements? Basically, it depends upon the type of contact, and what we get into the AMS projects in terms of the team composition.

While we do not have a business relationship with Azure, we are trying to become partners. 

Most of our implementations happen on Azure itself. Wherever we go, we take the solutions and we go to the other customers and we propose them. We tend to recommend this solution.

I'd rate the solution seven out of ten. There is a scope for improvement. Eventually, as they come across different case by case, they'll enhance things. Currently, what I see here is the data governance part is missing here from a development life cycle point of view.

Microsoft Azure Synapse Analytics differs from the old traditional on-premise business intelligence operations, where it's set up to do real-time analytics. For example, with IoT devices. Instead of having patients come to the hospital and do their operations, the hospitals will give patients an IoT device and you can monitor the patients in real-time using Microsoft Azure Synapse Analytics.

The point of the solution is to integrate the business into the analytics or vice versa. In the hospital example above, traditionally analytics is to tell us what happened. We look at reports to see what has happened. Microsoft Azure Synapse Analytics puts us more on the spot by telling us what's going to happen. Rather than what did just happen.

Microsoft Azure Synapse Analytics could improve its compatibility with Visual Studio. One of the challenges for people moving from an on-premise to a cloud solution, such as Microsoft Azure Synapse Analytics, is that you're constantly working in a browser. There are people that have been working for decades on desktop applications. For them to start working in a browser, it's quite a change. Allowing people to work and do their work inside Visual Studio than in the browser, would be a large advantage.

I have been using Microsoft Azure Synapse Analytics for approximately one year.

Microsoft Azure Synapse Analytics is created out-of-the-box to be scalable. That was always the struggle of Analytics and BI Teams you had to spend $2 million to receive the server with RAM and disk space needed to use this type of solution. Microsoft Azure Synapse Analytics will scale automatically behind the scenes. Which is one of its main powerful features.

We have many people using the solution. The data engineer, who is moving data around and brings data in. The data scientist and the IoT developer. There are different areas in Microsoft Azure Synapse Analytics for each role.

I have not used the technical support from Microsoft Azure Synapse Analytics, but I worked with the developers at Microsoft who were top-notch. 

In my proof of concept project, I would simply email Microsoft directly and they were really responsive. The ticketing system on the Azure platform is very good. You just click open ticket, and they will get back to you quickly.

There are not many books on Microsoft Azure Synapse Analytics but there are tutorials and all that information online. However, the tutorials on Microsoft's site are enough to get you started.

The setup of Microsoft Azure Synapse Analytics is different than anything we've used on-site. It is different from the Analysis Services five years ago. However, even though it's different, the setup is easy.

One of the benefits of Microsoft Azure Synapse Analytics is that you shouldn't have to do any maintenance. It's all done behind the scenes. There is a serverless feature, where it'll expand and add RAM and add resources as needed. You have to be careful with the cost.

There's no license required for Microsoft Azure Synapse Analytics. the model is more of a use-based system. You got to pay for computing power and disk storage. Everything has different units and is kept backed up. Microsoft Azure Synapse Analytics uses storage units(SU). This is how everything's computed for cost.

My advice to those wanting to use this solution is to start small to get an understanding of how it operates.

I rate Microsoft Azure Synapse Analytics a nine out of ten.

We use this solution as a data warehouse. Power BI allows us to visualize the data while analyzing data from the data lake through Serverless. We have not used too much of the pipelines within the Data Factory because we have an isolated Data Factory for that.

This is a stable solution with many functionalities.

The only issue that we have run into with the solution's performance is with regard to concurrency.

We would also like to see faster response times from support.

I have used this solution for three years.

The stability of this solution is good.

The solution is scalable. We currently have fifty to sixty people working within it and, now that we are using Serverless more often, we are planning to have more people working with it.

Support is good but they could be a bit faster replying to our tickets.

The initial setup was straightforward.

We had one admin complete the initial setup in ten to twenty minutes.

Price varies by use-case. You pay for the database itself in addition to any consumed data within Serverless plus other fees if you use the Data Factory that is inside.

I would recommend others to use this product but urge them to understand that it is more of a technical database used to prepare data as opposed to serving it.

I would rate this solution a seven out of ten.

The product is easy to use. 

One potential area for improvement could be the availability of an on-premises data lake implementation, as the product is currently only implemented in a cloud environment. 

Additionally, the possibility of integrating data from multiple sources could be beneficial. 

We have used Microsoft Azure Synapse Analytics for approximately three months.

The platform's scalability is similar to that of SQL databases. It requires developing components, implementing services, and performing other related tasks.

The initial setup process is straightforward. 

My advice would be to remain open to learning new things, particularly because working with Synapse Analytics requires a shift in mindset from traditional tools like SQL Management Studio to newer tools and approaches.

I rate it an eight out of ten. 

We encountered data processing and transformation issues while working with Apache Spark languages for the product. This particular area needs improvement. 

The product's error messaging could be friendlier. Additionally, the monitoring process using Azure ML SDK and Python should depend on the data for the results. Along with the documentation, they should provide essential training for proficiency in CLI. It will help in better monitoring.

We have been using Microsoft Azure Synapse Analytics for two years.

The product is expensive.

I rate Microsoft Azure Synapse Analytics a seven out of ten. It is a fantastic product; we are satisfied with its features and performance. However, there could be more information available about the platform.

The most valuable aspect of this Microsoft Azure Synapse Analytics is its consolidation of technical support from Microsoft, and its ability to securely host large quantities of data within the cloud environment. The overall ability to manage and maintain Big Data within the cloud provides a heightened level of efficiency, reliability, and support from Microsoft. This results in a superior user experience and an increased level of value for the end user.

There may be some challenges in terms of connecting with Virtual Networks (VNETs) to Microsoft Azure Synapse Analytics.

I have been using Microsoft Azure Synapse Analytics for approximately one year.

The stability of Microsoft Azure Synapse Analytics is great. It offers a high level of performance.

The scalability of Microsoft Azure Synapse Analytics is good.

The support from Microsoft Azure Synapse Analytics is excellent.

There is a steep learning curve to do the implementation.

I rate the initial setup of Microsoft Azure Synapse Analytics a seven out of ten.

The entire Microsoft Azure ecosystem is well connected and Microsoft has done well with the features.

My advice to others is to try out the solution, do your homework and research, and set up a POC environment.

I rate Microsoft Azure Synapse Analytics an eight out of ten.

We use the solution for integration to enable the data to reuse it in the power gap.

I like the simplicity of the integration of the data and the variety of the language you can use to integrate that.

It offers a straightforward setup.

The solution can scale.

Its stability is good.

There are some limitations. The filing can be improved. Some improvement in the filing is necessary. It needs some kind of growth in the filing development in order to reuse some activities.

I'm pretty new in the company. I started in January. However, they have been using this tool for two years.

The stability is great. There aren’t bugs or glitches and it doesn’t crash or freeze. It’s reliable.

The solution is scalable.

We have about 20 people using the solution in our company.

I haven't had any contact with technical yet, so I cannot evaluate their level of service.

The solution is easy to set up initially.

I’m not sure how much the solution costs.

We buy direct from Microsoft. Our company may be partners with them.

As Microsoft Azure Cloud, it only has one version. I don't know if there is a version number. 

I would advise users to start loading the data beforehand and understand very well how the tool works and how it's useful. That way, you can evaluate the best solution. Sometimes you need to start to load data and review all the alternatives in the solution.

I’d rate the solution a nine out of ten.