I used it for a project thesis for my school project.
Software Engineer at a educational organization with 501-1,000 employees
It is well-structured and provides good performance
Pros and Cons
- "I like its performance. It is well-structured and offers a lot of practical options. Because of the visual design of the product, it is very easy to find icons and other visual elements. It took me more than two weeks to understand how it works. I had an intensive training session to understand it, which was enough. It was not hard to understand how it works."
- "I am a researcher. For people to be able to research a solution, there should be at least a free trial. Just advertising a product or saying that this product is better doesn't work. I would strongly recommend providing a lot of free trials and trainings. This will also help Microsoft in having more users or customers. Oracle provides some free trials. You can just go for a free trial and use your database online, which is very good."
What is our primary use case?
What is most valuable?
I like its performance. It is well-structured and offers a lot of practical options. Because of the visual design of the product, it is very easy to find icons and other visual elements.
It took me more than two weeks to understand how it works. I had an intensive training session to understand it, which was enough. It was not hard to understand how it works.
What needs improvement?
I am a researcher. For people to be able to research a solution, there should be at least a free trial. Just advertising a product or saying that this product is better doesn't work. I would strongly recommend providing a lot of free trials and trainings. This will also help Microsoft in having more users or customers. Oracle provides some free trials. You can just go for a free trial and use your database online, which is very good.
For how long have I used the solution?
I have been using Microsoft Azure SQL Data Warehouse for three months.
Buyer's Guide
Microsoft Azure Synapse Analytics
November 2024
Learn what your peers think about Microsoft Azure Synapse Analytics. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
How was the initial setup?
It was ready when I started to use it. I just had to do my project.
What's my experience with pricing, setup cost, and licensing?
Its price could be better. It was a school project, and I got it for free. If I try to pay through my company, it is a little bit more expensive as compared to Oracle.
Which other solutions did I evaluate?
I am also using an Oracle solution. Oracle has been in the database field for a longer time, and it provides you more familiar terms that the users understand. When users start to work with an Oracle solution, they are more familiar with the terms. They just need basic training to understand it, but with Microsoft Azure SQL Data Warehouse, they have to be a little bit more experienced. In order to understand this product better, they have to know how other Microsoft products work.
What other advice do I have?
It is a powerful asset if we can use it and learn more about it. If Microsoft can give some free training sessions for students and amateurs, it would be helpful in knowing more about this product from inside.
I would rate Microsoft Azure SQL Data Warehouse an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Project Manager at a tech services company with 5,001-10,000 employees
Good analytics and integration with Power BI, but the ETL capability is far behind other products
Pros and Cons
- "The most valuable feature of the solution is the analytics and that it can connect with Power BI."
- "I would like my team to be able to build pipelines that integrate with the Azure Data Factory."
What is our primary use case?
We primarily use this solution for source analytics and procurement.
What is most valuable?
The most valuable feature of the solution is the analytics and that it can connect with Power BI. I found it quite interesting and very compelling in terms of detail within a single stack.
What needs improvement?
I would like my team to be able to build pipelines that integrate with the Azure Data Factory. Some of the best-in-class ETL products that are available in the market, such as Informatica ETL, are far more mature than this solution.
For how long have I used the solution?
We started implementing projects with Microsoft Azure SQL Data Warehouse about six months ago.
What do I think about the stability of the solution?
This is a stable product.
What do I think about the scalability of the solution?
Scalability is good and we haven't had any issues.
We have approximately 150 users. We are stable at the moment but we will expand our usage as we get more data.
How are customer service and technical support?
We have contacted Microsoft support twice, but I do not have much experience with them.
Which solution did I use previously and why did I switch?
In addition to Azure SQL Data Warehouse, we work with the version that is on-premises.
We are also working with Oracle Data Warehouse and we plan to continue using both of these solutions.
How was the initial setup?
The initial setup is straightforward.
What about the implementation team?
We implement this solution for our customers.
What other advice do I have?
If you are using Microsoft products, such as Office 365, then this solution is good because it can take the data from multiple sources.
This is a good product, but when you compare to Oracle Data Warehouse there are differences in scalability, high availability, and implementation.
I would rate this solution a seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Microsoft Azure Synapse Analytics
November 2024
Learn what your peers think about Microsoft Azure Synapse Analytics. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
BI Consultant at a tech services company with 11-50 employees
Straightforward installation, beneficial dedicated SQL pooling, but performance could improve
Pros and Cons
- "The integrated workspace in Microsoft Azure Synapse Analytics where everything comes together, such as Power BI and Data Factory, is very good. Additionally, the ability to do dedicated SQL pooling is a benefit."
- "In the future, Microsoft Azure Synapse Analytics could improve the performance, there are other solutions that are better, such as Databricks."
What is our primary use case?
Microsoft Azure Synapse Analytics can be used for analytics and brings together data integration.
What is most valuable?
The integrated workspace in Microsoft Azure Synapse Analytics where everything comes together, such as Power BI and Data Factory, is very good. Additionally, the ability to do dedicated SQL pooling is a benefit.
What needs improvement?
Microsoft Azure Synapse Analytics can improve querying. I have recently used Microsoft Azure Synapse Analytics to connect to the Delta Lake file and I have noticed some issues. It has not been able to read the latest version of the Delta Lake file and I have found this to be a disadvantage that they can improve.
In the future, Microsoft Azure Synapse Analytics could improve the performance, there are other solutions that are better, such as Databricks.
For how long have I used the solution?
I have been using Microsoft Azure Synapse Analytics for approximately six months.
What do I think about the scalability of the solution?
On the client's side, there are approximately 100 users of this solution.
How are customer service and support?
Have I reached out to Microsoft technical support in a few instances and we have raised a couple of tickets. A couple of agents have been knowledgeable, but not everyone is.
How was the initial setup?
The installation of Microsoft Azure Synapse Analytics was easy. It was not complicated, but I have not explored the VNet Injection or the Private Endpoint though I think it would be straightforward.
What's my experience with pricing, setup cost, and licensing?
We are on a monthly payment plan for the use of Microsoft Azure Synapse Analytics.
Which other solutions did I evaluate?
We have done some comparisons between Microsoft Azure Synapse Analytics in many areas, such as processing queries, versus Databricks. We have found Databricks to be better in performance.
What other advice do I have?
I would recommend this solution to others. The client that I am working for, their preferred database is Synapse.
I rate Microsoft Azure Synapse Analytics a seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Director, Consulting, Technology Services at a financial services firm with 1,001-5,000 employees
Easy to scale out and scale down services and relatively straightforward to install, but needs Managed VNet and more compatibility with SQL Server
Pros and Cons
- "The ability to scale out services on-demand and scale them down when they are not required is most valuable. You are in control of your expenditures, and you are also in control of the horsepower that you need. That's a major advantage."
- "The major challenge that we're seeing with Azure Synapse is around security concerns. The way it is working right now, it has Managed VNet by Microsoft option, similar to the implementation of Azure Databricks, which may pose a concern for financial institutions. For managed environments, the banks have very strict policies around data being onboarded to those environments. For some confidential applications, the banks have the policy to encrypt it with their own key, so it is sort of like Bring Your Own Key, but it is not possible to manage the resources with Microsoft or Databricks, which is probably the major challenge with Azure Synapse. There should be more compatibility with SQL Server. It should be easier to migrate solutions between different environments because right now, it is not really competitive. It is not like you can go and install SQL Database in some other environment. You will have to go through some migration projects, which probably is one of the major showstoppers for any bank. When they consider Synapse, they not only consider the investment in the actual service; they also consider the cost of the migration process. When you scale out or scale down your system, it becomes unavailable for a few minutes. Because it is a data warehouse environment, it is not such a huge deal, but it would be great if they can improve it so that the platform is available during the change of configuration."
What is our primary use case?
We mostly provide cloud data warehousing platforms for major banks in Canada. What we're trying to do is to create a standard platform environment that is compliant with the regulatory requirements imposed by the government and financial overseeing institutions for the banks. We help them to onboard the lines of business to these platforms and migrate the existing workloads to the cloud platforms.
What is most valuable?
The ability to scale out services on-demand and scale them down when they are not required is most valuable. You are in control of your expenditures, and you are also in control of the horsepower that you need. That's a major advantage.
What needs improvement?
The major challenge that we're seeing with Azure Synapse is around security concerns. The way it is working right now, it has Managed VNet by Microsoft option, similar to the implementation of Azure Databricks, which may pose a concern for financial institutions. For managed environments, the banks have very strict policies around data being onboarded to those environments. For some confidential applications, the banks have the policy to encrypt it with their own key, so it is sort of like Bring Your Own Key, but it is not possible to manage the resources with Microsoft or Databricks, which is probably the major challenge with Azure Synapse.
There should be more compatibility with SQL Server. It should be easier to migrate solutions between different environments because right now, it is not really competitive. It is not like you can go and install SQL Database in some other environment. You will have to go through some migration projects, which probably is one of the major showstoppers for any bank. When they consider Synapse, they not only consider the investment in the actual service; they also consider the cost of the migration process.
When you scale out or scale down your system, it becomes unavailable for a few minutes. Because it is a data warehouse environment, it is not such a huge deal, but it would be great if they can improve it so that the platform is available during the change of configuration.
For how long have I used the solution?
I have been using this solution for two years.
What do I think about the stability of the solution?
Generally, it is stable. We all heard about the Active Directory issue earlier this week, but it was not related to Synapse. It was related to the Azure platform.
What do I think about the scalability of the solution?
Its scalability is good. The only thing is that when you scale out or scale down your system, it becomes unavailable for a few minutes. Because it is a data warehouse environment, it is not such a huge deal, but it would be great if they can improve it so that the platform is available during the change of configuration.
How are customer service and technical support?
We're working with banks, and they have great support because Microsoft has multiple representatives closely monitoring each account. Whenever there is an issue, they're being proactive. They're making a lot of money out of it. Most of the banks, on average, spend between 30 to 50 million a year on Azure. They're pretty large accounts, and Microsoft has dedicated people supporting everything related to Azure.
Which solution did I use previously and why did I switch?
We deliver platforms to different banks. Some of the banks go with Synapse, and some of the banks go with Snowflake. Overall, these are two major alternatives available right now.
There are multiple differences in terms of the support of different workloads. When one of the banks made a decision to go with Snowflake, the major reason for it was the support for the multi-cloud environment. The major pro of Synapse is the service, and the major con is that when you decide to move out of Synapse, you would have to rewrite the entire thing, whereas, with Snowflake, it would be just simple migration to different cloud providers.
How was the initial setup?
It is relatively straightforward as long as you understand what you're doing.
What about the implementation team?
You don't really need to maintain it. That's the entire point of the cloud. You pay for it to be maintained.
We do deal with monitoring and other similar things, but most of the activities are automated. Overall, it doesn't require a lot of labor around it. We're delivering the platform as infrastructure as a cloud, so everything is going through the pipeline.
What's my experience with pricing, setup cost, and licensing?
It goes by the usage, and there are some limits. Synapse goes by particular pricing, and it is expensive. Both Azure Synapse Analytics and Snowflake are pretty expensive. They don't have standard pricing. They deal with each customer differently.
What other advice do I have?
For working with Synapse, you need to have an understanding and knowledge of the product to take full advantage of it. Synapse has a lot of features in terms of scalability, such as resource management, distribution, and partitioning. There are a lot of things that you need to consider when you go for it. It is not a simple database that you put in there, and it is running itself.
I would rate Microsoft Azure Synapse Analytics a seven out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Director of Data Analytics Practice at a computer software company with 501-1,000 employees
Data retrieval and warehousing that is scalable and flexible, and the documentation is good
Pros and Cons
- "The most valuable feature is performance gains."
- "I would like to see them provide the ingestion of images."
What is our primary use case?
The primary use case is for the fast retrieval of data, which is in the data warehouse on-premises and migrating it to the cloud.
What is most valuable?
The most valuable feature is performance gains.
The scalable nature of the data warehouse on the cloud, and the flexibility that you get, and important features.
What needs improvement?
I would like to see them provide the ingestion of images.
For how long have I used the solution?
I have been using this solution for more than three years.
It's a production that keeps changing and we are always using the latest version.
What do I think about the stability of the solution?
This solution is quite stable. It's in the cloud and we have not faced any issues.
What do I think about the scalability of the solution?
This solution is scalable.
How are customer service and technical support?
Technical support was not needed because of all of the documentation available.
How was the initial setup?
The initial setup is straightforward.
What's my experience with pricing, setup cost, and licensing?
All of the prices are available online.
What other advice do I have?
My advice would be to move your on-premises data warehouse to the cloud. Move it there faster, as you can get more performance gains and it's also a robust infrastructure.
I would rate this solution an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Data Platform Architect at APN Promise
Scalable and comprehensive, with easy Microsoft integration
Pros and Cons
- "Fills the gap between big data and classic data warehouses."
- "Comes with a pretty steep learning curve."
What is our primary use case?
My primary use case of this solution is as a data warehouse.
What is most valuable?
The most valuable feature of this solution is its filling of the gap between big data and classic data warehouses. As a solution, Synapse allows you to do almost everything.
What needs improvement?
An area for improvement would be advanced analytics. The product also comes with a pretty steep learning curve, which could be improved. In the next release, I would like an improvement in internal security, which currently doesn't work at all.
For how long have I used the solution?
I've been working with this solution for about two years.
What do I think about the stability of the solution?
Initially, the product had some issues with stability, but these seem to have improved with time.
What do I think about the scalability of the solution?
Scalability is one of the main advantages of this solution.
How are customer service and support?
Tech support is ok but more difficult tickets can take a long time to solve.
How was the initial setup?
The setup was complicated because the data must be organized differently from the classic SQL database. There are also different techniques for query performance and managing caches, which makes the process more complicated.
What's my experience with pricing, setup cost, and licensing?
Synapse is a very costly solution, and other products are available for less.
What other advice do I have?
One of the main pros of Synapse is the ability to work with the classic data warehouse and the big data. Another is the ability to use the Spark engine for preparation. Before implementing this product, consider whether it will provide the results you want. If you are already using Microsoft products, Synapse is easy to integrate. I would score this solution as eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Enterprise Solutions at Celebal Technologies
Scalable, easy to use and set up with an intuitive platform that integrates well with Power BI
Pros and Cons
- "They are available on the Cloud, and the platform is very intuitive."
- "It needs strong support for social media, internet data, and native support for NoSQL."
What is our primary use case?
We are service providers for our clients.
My clients primarily come from the enterprise segments, such as manufacturing, retail, pharmaceutical, and industrial. Most are supported by a large ERP solution like SAP.
Some of our clients are mid-size and others are large enterprise companies, some of the largest in India.
What is most valuable?
Some of the most valuable features would include Familiarity for practitioners like us and also familiarity for the businesses. SQL servers have been around for several decades and there are many who are familiar with SQL servers, such as SSIS and SSRS.
They are available on the Cloud, and the platform is very intuitive.
It integrates very well with Power BI, which I would rate as the best self-service BI. All the data warehouses eventually end up in BI or Machine Learning.
Instant Apps that are more integrated rather than desperate components. You need to get different components engineered together, and with SQL everything comes together.
Instant Apps is a combination of your Spark compute platform, your SQL data platform, and your object storage. It's a platform that is integrated all together.
It's easy to work with a faster turnaround time on my project deliveries.
Also, the integration with Power BI self-service is much, much easier and familiar.
You can have several SQL servers, they have large .NET artifacts that combine various components together very well.
What needs improvement?
What I would like to see more and more of in Azure is its support for IoT and streaming media information.
It needs strong support for social media, internet data, and native support for NoSQL. At this time, it works very well with the structured data
Stability could be improved.
Technical support is very good, but could also be improved.
For how long have I used the solution?
My company has been working with SQL Data Warehouse for approximately three and a half years, and I have been working with this solution for one and a half years.
What do I think about the stability of the solution?
In the last six months, there have been a couple of incidents. We have experienced som outages. One of our clients was in a blackout for a couple of hours. Most of the clients in India have experienced outages also. They were restored, so I refer to them as glitches.
What do I think about the scalability of the solution?
In principle, it's a limitless, serverless solution. As long as your region has resources, you can go on expanding. We have not had any problems with scalability.
Microsoft Azure comes integrated with Databricks as a Machine Learning platform, it's highly scalable.
How are customer service and technical support?
Technicals support engages very well. We have account managers in place who correspond with technical support.
The technical support team has a good relationship with our Account managers.
If we have an issue, we advise our account managers and present the ticket, they contact Technical support and resolve the issue very quickly.
If however, I have to contact Microsoft technical support at the backend, they are not very knowledgable. They have a good understanding of their products, but most of the time they struggle with that.
How was the initial setup?
The initial setup is easy. The learning curve for Microsoft platforms is very low. An engineer with very little experience would be able to complete the initial set up with ease.
It has a quick turnaround time. We have completed the deployment in weeks.
For a BI project scheduled for six months, within the first month we would have completed the data warehouse installation, and the remaining five months would be for building the content, the data pipelines from the sources, the semantic models, and the BI.
When you compare it with other solutions that take months to get your sandbox running or to get your development running.
What's my experience with pricing, setup cost, and licensing?
They are cost aggressive, and it integrates well with other Microsoft tools. For example Downstream and Teams.
What other advice do I have?
We use the serverless platform as a service, that is only available with Microsoft Azure.
You don't have to hire experienced engineers to set up and implement the solution, saving you money, because it is very intuitive and the turnaround time is very low compared to other data warehouses. I would put it in par with solutions such as Redshift and BigQuery.
It's very modern, easy, and intuitive.
Most of the services are cheaper than other vendors.
This definitely falls into one of the top three or top four solutions and platforms in the world. I would definitely recommend it. If someone should ask me if they should use Microsoft Azure SQL Data Warehouse, I would say yes.
Personally, I don't see one great solution that exceeds in all aspects. Every solution has some good points and I think they have very beautifully found their strength and they're building upon it.
When asked what would best suit me, I would assess their environment requirements and could easily recommend any of the top four, being AWS Redshift, Google, Big Query, and Microsoft Azure.
I would rate this solution an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
President at a tech company with self employed
Good analytics, and has good technical support
Pros and Cons
- "I have been working with Microsoft, and they have been very helpful."
- "If I'm looking for something good in the cloud, I would want it to have better standard connectors."
What is our primary use case?
We use Microsoft Azure Synapse Analytics for analytics.
What needs improvement?
If I'm looking for something good in the cloud, I would want it to have better standard connectors.
For how long have I used the solution?
I have been working with Microsoft Azure Synapse Analytics for two years.
We are up-to-date with the latest version.
How are customer service and support?
I have been working with Microsoft, and they have been very helpful.
Which solution did I use previously and why did I switch?
It's the only product I've used. I'm not sure what's wrong or what could be done better.
What's my experience with pricing, setup cost, and licensing?
I don't know about the price, but I'm trying to get a sense of the cost. I believe having a good comparison would help.
What other advice do I have?
This is the only product I've ever used, as such, it's extremely difficult for me to say anything about it. For example, if I needed a bike, and now I have one and am riding it. If you ask me some questions, it's difficult for me to say, "Oh, I really missed this one on my first bike," unless I've ridden a few bikes. I'm not sure why everything is the way it is. I had a need, and I'm only using it now.
I'm trying to understand what else is out there and how it compares to what is out there.
I am able to use it. If I am able to use it, I would rate Microsoft Azure Synapse Analytics an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Microsoft Azure Synapse Analytics Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Product Categories
Cloud Data WarehousePopular Comparisons
Azure Data Factory
Amazon Redshift
AWS Lake Formation
Oracle Autonomous Data Warehouse
SAP Business Warehouse
IBM Db2 Warehouse on Cloud
Buyer's Guide
Download our free Microsoft Azure Synapse Analytics Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- What are the benefits of having separate layers or a dedicated schema for each layer in ETL?
- Which solution do you prefer: KNIME, Azure Synapse Analytics, or Azure Data Factory?
- Which is better - Azure Synapse Analytics or Snowflake?
- How does Amazon Redshift compare with Microsoft Azure Synapse Analytics?
- Which ETL or Data Integration tool goes the best with Amazon Redshift?
- What are the main differences between Data Lake and Data Warehouse?
- What are the benefits of having separate layers or a dedicated schema for each layer in ETL?
- What are the key reasons for choosing Snowflake as a data lake over other data lake solutions?
- Are there any general guidelines to allocate table space quota to different layers in ETL?
- What cloud data warehouse solution do you recommend?