We integrate SQL Data Warehouse with our infrastructure, leveraging its strong integration with Power BI. The solution's cloud-based nature facilitates easy integration with our system, providing significant advantages over other solutions like Google’s. I rate it an eight.
Microsoft Parallel Data Warehouse is beneficial from a data analysis perspective. It has been in the market for a long time. It is a very stable and robust product for the on-premise version. I rate it a nine out of ten.
Team Leader at a tech services company with 201-500 employees
Real User
Top 20
2023-08-11T08:01:00Z
Aug 11, 2023
All of the components related to the pipeline are included in Synapse. We have some ETL tools based on Data Factory and other advanced functions based on Databricks. Not all of the functionality is included in Synapse. It makes no sense to have the product without all of the functionality. It is tricky to manage the storage mode of the data because if we don't read the documentation and don't create a good distribution of the data, we will have problems in the performance. If we do it, we will have no problem. Overall, I rate the solution an eight out of ten.
Octopus Deploy holds the deployment part of the solution. In our company, we develop solutions, and we can deploy them with Octopus Deploy. In our team, we have eight developers, and we can do the deployment at the same time, but Octopus Deploy does the deployment one by one, in the order starting from the first person who applied for the deployment. Regarding ETL tools, I have used SSIS and some experience in OBIEE. I have experience with multiple other solutions, including some from Microsoft. I have heard of Informatica, but I am not really sure how good it is overall. Considering that I have just started using Azure and everything is shifting to the cloud, I will recommend Microsoft Parallel Data Warehouse since it is easy to use and feasible. Overall, I rate the solution an eight out of ten.
Learn what your peers think about Microsoft Parallel Data Warehouse. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
BI/Data Warehouse Analyst at a healthcare company with 501-1,000 employees
Real User
Top 20
2023-03-09T22:03:22Z
Mar 9, 2023
I am an end-user. I'd rate the solution seven out of ten. I like that, with Microsoft, I can access the cloud easily. However, it would be ideal if the solution could offer more features, like DB2.
Our organization has a partnership with Microsoft right now. I'd rate the solution a nine out of ten. I do find that, when it comes to comparing it to Oracle and other tools, there are some better things available on other products. Oracle, for example, manages a large set of data, so, and it is more optimized and a bit faster.
Senior Software Engineer at a tech services company with 1,001-5,000 employees
Real User
2020-08-30T08:33:18Z
Aug 30, 2020
We're just a customer. We don't have a business relationship with the product. I'd rate the solution eight out of ten overall. It's never given us issues in terms of scaling or stability. Technical support is quite good. It offers some great features.
System Administrator at a university with 501-1,000 employees
Real User
2020-08-27T10:31:46Z
Aug 27, 2020
For a small-sized company like ours, I really recommend this product. It can handle a big workload. I would say other products could not be better than Microsoft for small businesses with a lesser budget. On a scale from one to ten where one is the worst and ten is the best. I would rate Microsoft SQL Server Parallel Data Warehouse as a seven-out-of-ten.
EDRMS Practice Lead at a tech services company with 51-200 employees
Real User
2020-05-04T05:12:00Z
May 4, 2020
We have had a good experience working with this tool. If you don't have a problem with memory and have good processors, then you won't have an issue. However, depending on your needs, you may want to go check out other tools. I would rate the tool as an eight out of 10.
Senior Principal Consultant at a tech services company with 1,001-5,000 employees
Consultant
2019-12-15T05:58:00Z
Dec 15, 2019
This is a solution that has good performance and I recommend it. The support from Microsoft is also another thing that makes the Parallel Data Warehouse a good option. The biggest lesson that we have learned from using this solution is that customers are most interested in a quick project turnaround time, which is something that Parallel Data Warehouse provides. This is a good solution but there is always room for improvement. I would rate this solution a seven out of ten.
Team Lead at a computer software company with 10,001+ employees
Real User
2019-12-12T07:48:00Z
Dec 12, 2019
My advice for anybody who is implementing Microsoft Parallel Data Warehouse is to be aware of how big the data is. You have to be sure of how to secure and take care of the data. You have to think about scalability. I would rate this solution a seven out of ten.
BI Developer at a healthcare company with 51-200 employees
Real User
2019-12-09T10:58:00Z
Dec 9, 2019
My advice for anybody who is implementing this solution is not to overload your server with all of the data that you don't use on a day-to-day basis. It is very easy to pull the data that you need whenever it is required. You will have to decide how to store the data and how easy it is for your client to send new data. Neither of these things should be difficult to do, even for newcomers to SQL. Sometimes, you will have to have a senior person demonstrate something basic, like how to pull data, and then people usually pick it up. I would rate this solution an eight out of ten.
Senior System Analyst at a tech services company with 1,001-5,000 employees
Real User
2019-12-05T06:53:00Z
Dec 5, 2019
My advice to anybody who is implementing this solution is to design the databases as well as they can because it is difficult to make changes in the future. It is also important to have a time field in your data in case you want to use it in the future as a reference. This is a good solution but all software can be improved and made better. I would rate this solution an eight out of ten.
Microsoft Dynamics Specialist at a computer software company with 51-200 employees
Real User
2019-11-20T05:39:00Z
Nov 20, 2019
On a scale from one to 10, I rate this solution a nine. In the future I would love to see a slightly better automation engine, just for the data integration layer, to make it slightly easier for end-users or junior developers to get involved in incremental updating. The biggest part that we battle with in terms of costing, and explaining to people why it takes so long to develop some of those things, is just to get the data into the actual data warehouse and automating that. It's purely an integration layer to actually get the data into the data warehouses. People need to do their research very well to understand the terminology and the technology when they speak to people that are technically inclined, because there's a lot of miscommunication in terms of what they expect from the program and what's delivered at the end of the day. The biggest lessons I've learned through the years are that Microsoft is probably the largest research company there is. So people should stick to people that know what they're doing, and Microsoft definitely has some very, very capable people designing these products. And that's probably why I've stayed with Microsoft so long. I've actually tried out a few other suppliers, but I always go back to Microsoft.
The traditional structured relational data warehouse was never designed to handle the volume of exponential data growth, the variety of semi-structured and unstructured data types, or the velocity of real time data processing. Microsoft's SQL Server data warehouse solution integrates your traditional data warehouse with non-relational data and it can handle data of all sizes and types, with real-time performance.
I would recommend SQL Server. It is very useful. I'd rate the solution nine out of ten.
We integrate SQL Data Warehouse with our infrastructure, leveraging its strong integration with Power BI. The solution's cloud-based nature facilitates easy integration with our system, providing significant advantages over other solutions like Google’s. I rate it an eight.
Microsoft Parallel Data Warehouse is beneficial from a data analysis perspective. It has been in the market for a long time. It is a very stable and robust product for the on-premise version. I rate it a nine out of ten.
I recommend the product to others. Overall, I rate the product a ten out of ten.
All of the components related to the pipeline are included in Synapse. We have some ETL tools based on Data Factory and other advanced functions based on Databricks. Not all of the functionality is included in Synapse. It makes no sense to have the product without all of the functionality. It is tricky to manage the storage mode of the data because if we don't read the documentation and don't create a good distribution of the data, we will have problems in the performance. If we do it, we will have no problem. Overall, I rate the solution an eight out of ten.
Octopus Deploy holds the deployment part of the solution. In our company, we develop solutions, and we can deploy them with Octopus Deploy. In our team, we have eight developers, and we can do the deployment at the same time, but Octopus Deploy does the deployment one by one, in the order starting from the first person who applied for the deployment. Regarding ETL tools, I have used SSIS and some experience in OBIEE. I have experience with multiple other solutions, including some from Microsoft. I have heard of Informatica, but I am not really sure how good it is overall. Considering that I have just started using Azure and everything is shifting to the cloud, I will recommend Microsoft Parallel Data Warehouse since it is easy to use and feasible. Overall, I rate the solution an eight out of ten.
Overall, I rate Microsoft Parallel Data Warehouse a seven or eight out of ten.
I give the solution an eight out of ten.
I am an end-user. I'd rate the solution seven out of ten. I like that, with Microsoft, I can access the cloud easily. However, it would be ideal if the solution could offer more features, like DB2.
I rate Microsoft Parallel Data Warehouse eight out of 10. I would recommend it.
Our organization has a partnership with Microsoft right now. I'd rate the solution a nine out of ten. I do find that, when it comes to comparing it to Oracle and other tools, there are some better things available on other products. Oracle, for example, manages a large set of data, so, and it is more optimized and a bit faster.
I rate this solution a five out of ten. I would advise anyone using this solution to find a good DBI.
We're just a customer. We don't have a business relationship with the product. I'd rate the solution eight out of ten overall. It's never given us issues in terms of scaling or stability. Technical support is quite good. It offers some great features.
For a small-sized company like ours, I really recommend this product. It can handle a big workload. I would say other products could not be better than Microsoft for small businesses with a lesser budget. On a scale from one to ten where one is the worst and ten is the best. I would rate Microsoft SQL Server Parallel Data Warehouse as a seven-out-of-ten.
We have had a good experience working with this tool. If you don't have a problem with memory and have good processors, then you won't have an issue. However, depending on your needs, you may want to go check out other tools. I would rate the tool as an eight out of 10.
I am not comfortable with the Microsoft Parallel Data Warehouse at the moment. I would rate this solution a six out of ten.
We use the on-premises deployment model. I'd rate the solution eight out of ten.
This is a solution that has good performance and I recommend it. The support from Microsoft is also another thing that makes the Parallel Data Warehouse a good option. The biggest lesson that we have learned from using this solution is that customers are most interested in a quick project turnaround time, which is something that Parallel Data Warehouse provides. This is a good solution but there is always room for improvement. I would rate this solution a seven out of ten.
My advice for anybody who is implementing Microsoft Parallel Data Warehouse is to be aware of how big the data is. You have to be sure of how to secure and take care of the data. You have to think about scalability. I would rate this solution a seven out of ten.
My advice for anybody who is implementing this solution is not to overload your server with all of the data that you don't use on a day-to-day basis. It is very easy to pull the data that you need whenever it is required. You will have to decide how to store the data and how easy it is for your client to send new data. Neither of these things should be difficult to do, even for newcomers to SQL. Sometimes, you will have to have a senior person demonstrate something basic, like how to pull data, and then people usually pick it up. I would rate this solution an eight out of ten.
My advice to anybody who is implementing this solution is to design the databases as well as they can because it is difficult to make changes in the future. It is also important to have a time field in your data in case you want to use it in the future as a reference. This is a good solution but all software can be improved and made better. I would rate this solution an eight out of ten.
On a scale from one to 10, I rate this solution a nine. In the future I would love to see a slightly better automation engine, just for the data integration layer, to make it slightly easier for end-users or junior developers to get involved in incremental updating. The biggest part that we battle with in terms of costing, and explaining to people why it takes so long to develop some of those things, is just to get the data into the actual data warehouse and automating that. It's purely an integration layer to actually get the data into the data warehouses. People need to do their research very well to understand the terminology and the technology when they speak to people that are technically inclined, because there's a lot of miscommunication in terms of what they expect from the program and what's delivered at the end of the day. The biggest lessons I've learned through the years are that Microsoft is probably the largest research company there is. So people should stick to people that know what they're doing, and Microsoft definitely has some very, very capable people designing these products. And that's probably why I've stayed with Microsoft so long. I've actually tried out a few other suppliers, but I always go back to Microsoft.