Microsoft Azure Synapse Analytics Reviews

We run our finance and supply chain jobs using SQL BW, and we visualize our data loads on Power BI. We are using SQL Data Warehouse for data warehousing.

In terms of cost savings, we don't need specialization in skills as advanced as Teradata. We used to pay extensive licensing fees for Teradata, which we no longer pay. Azure Synapse has provided scalability and ease of use, especially when looking at performance tuning and optimization.

Our data is available on-premises, so we are extracting the data from our private on-premises servers and Azure databases.

I like SQL post, which is for storage and distributed computing. Another good feature is the copy activity.

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.

Our company uses the solution to mine generous amounts of data for customers. We are partners with Microsoft and are totally dependent on the solution. 

Synapses are very good and can deal with petabytes of data. 

The solution has far better synapse analytics than Redshift. 

The solution handles single or complex items within a second. 

Power BI is a great management tool that has email in the synapse itself so you can move regulations. 

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. 

I mainly use it to run queries, deploy servers, and make connections across data. I help clients with data warehousing and analytics.

It's quite quick for querying, even with large datasets, and it's scalable. It's also flexible to use, so it's easy to update and get data quickly without wasting time.

We use Synapse to build views for our data warehouse. It is the place where we get our reports and views. We ingest data into our SQL Servers and Azure SQL, then build all our reporting views within Synapse.

I'm the cloud architect, and I have a two-person DevOps team plus another enterprise architect. Five people are using the interface at any given time. 

Synapse makes it easy to integrate and onboard data from other Microsoft and Azure sources. The interface is familiar because we were using Azure Data Factory before Synapse. It made the transition even easier because the Synapse interface is exactly the same. 

The good thing about Synapse is the scale factor. It can handle a lot more volume of data compared to Azure SQL. There is Azure SQL, and there is a SQL Data Warehouse, which is now called Synapse. SQL is for smaller databases, and SQL Data Warehouse (Synapse) is for larger databases. Performance-wise, if you process a huge amount of data, SQL Data Warehouse is good due to its parallel processing capability. It's scalable. 

The setup is pretty simple. 

It's stable. 

In Azure, when you do the scaling up, it is not totally simple. It takes time to scale up. It actually kind of rebuilds the database behind this when you scale. If I am utilizing 1,000 of what they call the Data Warehouse and you need 1,200, there is downtime required.

There is a limit on the number of concurrent queries to around 125 for Azure Synapse.