Microsoft Parallel Data Warehouse Reviews

We primarily use Data Warehouse for our business intelligence platform Qlik, which sits on top of it. Data Warehouse is a middleware product. Our users work with Qlik, and our data architects are using SQL Server. It mostly feeds the data to the Qlik cloud product. 

Very few people are directly using the Data Warehouse. It takes data from other source systems, transforms it, and serves it up to be analyzed in Qlik. Depending on how you look at it, we have around 120-130 indirect Data Warehouse users, but maybe only three or four.

I like Data Warehouse's data integrity features. Data integrity is what databases are made for as opposed to spreadsheets. 

I would like the ability to do more real-time type updates instead of batch-oriented updates. 

I have been using Parallel Data Warehouse for a year, but I've been working with SQL Server for around 30 years.

Data Warehouse rarely goes down on us.

The scalability is good. Eventually, we will move our on-premise SQL database into the Azure cloud, but we're not there yet.

Setting up Data Warehouse is relatively straightforward if you know SQL. For maintenance, we have three or four data architects, whose roles are fluid between database management and business intelligence.

I don't know how much Data Warehouse costs, but it isn't too expensive. We have the hardware, so it's just the Microsoft SQL license. 

I rate Microsoft Parallel Data Warehouse eight out of 10. I would recommend it. 

We primarily use the solution for data. 

Everything about the solution is great. The admission tools, their BI tools, and data warehousing tools are all good.

The solution has been reliable. It's stable. 

You can scale the product well. 

The implementation process is great.

Its interface is good. 

The tools are very good, efficient, and easy to work with.

I don't have any need for new features. 

We'd like to see it be a bit more compatible with other solutions. 

It could be faster. Right now, Oracle is a bit quicker in comparison. We'd like the solution to handle a larger amount of data faster. 

I've been using the solution for about five to six years.

The performance and reliability are good. We find it to be very stable. There are no bugs or glitches. It doesn't crash or freeze. 

The scalability of the product is great. It's easy to expand. 

It's quite efficient in all the features that we're currently using it extensively. It's giving more and more function. et cetera.

Thousands of users currently using this product. For example, our clients are normally banks and the users are in the thousands. They normally use it each and every day.

I've never used technical support. Mostly I will Google questions to get help. I've never had a problem so big I had to call technical support for this.

I have used Oracle and I've used IBM Db2. I switched due to the job I had. Their new tool was SQL Server.

The initial setup is quite straightforward. It's not overly complex or difficult. We didn't have any issues implementing it. 

It's very easy to use. You just follow the simple documentation and the setup is not more than 30 minutes.

I'd rate the process a five out of five in terms of ease of implementation.

I do not track ROI. A different part of the organization might follow this. 

I'm not sure of the licensing costs of the solution. 

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. 

We have almost 20 years of historical data and use this solution to maintain the cube data. It ensures we don't lose the data.

We have ownership of our data, and it keeps everything on-premises, so we have complete control over our data.

The performance could be improved because the query is slow if we don't optimize it. And even if we optimize it, sometimes it still runs very slow.

It is deployed on-premises. 

It is a stable solution. 

It is scalable but takes some effort.

I rate this solution a five out of ten. I would advise anyone using this solution to find a good DBI.

We use the product for data analytics purposes.

Microsoft Parallel Data Warehouse provides good firewall processing in terms of response time.

Sometimes, the product requires rolling back to its previous version during a software update. This particular area could be enhanced. 

We have been using Microsoft Parallel Data Warehouse for five years.

It is a very stable platform. However, we have to roll back to the previous state in a few instances while updating the software. I rate the stability an eight out of ten.

We have more than 1000 Microsoft Parallel Data Warehouse users in our organization. It is a scalable platform.

The technical support services are good and depend on the service level agreement.

The deployment process is straightforward once the domain is ready. However, the complexity might arise when populating the data into the system. It requires two or three managers, engineers, or administrators to deploy and maintain.

We implement the product with the help of our in-house team.

They offer an annual subscription. The pricing depends on the size of the environments.

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.

The product handles reporting, data collection, and sharing, and serves as a database for applications.

Data collection and reporting are the tool's valuable features. 

SQL installation is pretty tricky. Its scalability and customer support also should be improved.

I have been using Microsoft Parallel Data Warehouse for more than 10 years. 

The solution is stable.

Currently, 54 individuals in our company use it.

My interactions with customer service have not been quite satisfactory. The customer service team should possess a higher level of knowledge.

The installation process can be time-consuming, and it does require some level of experience. For instance, understanding mixed mode and working with Windows logging, especially for beginners using the solution, might pose some challenges. The deployment process takes a bit longer, but it's manageable. However, comparing it to installing SQL, both tasks are relatively straightforward. Two people are required for deployment.

The solution was implemented in-house. 

Our clients use Microsoft SQL Server Parallel Data Warehouse to create a separate database and build a data warehouse model. However, they do not use the appropriate product built into Microsoft SQL Server Parallel Data Warehouse for business intelligence. Instead, they create another database, link the model there, move the data from the online transaction database to the data warehouse to create a business intelligence database, and install a reporting tool on top of that. This is what our client does. We have experience with this process, as we are often the ones they call to transfer data from one database to the other, tune the database for performance, and create reports using a reporting tool.

In recent years, we have not been heavily involved with warehouse projects. Most of the time, we are involved with integrating different systems from different vendors. It is not possible to use one enterprise system to solve all of a company's problems, so they usually have three or four big systems and have difficulty integrating them. We spend most of our time creating integrations and transferring small chunks of information from one system to the other. When it comes to our house and business intelligence projects, they are usually limited to reporting; people just want to collect data, aggregate it, and view it from some reports. These days, Microsoft SQL Server Parallel Data Warehouse is the most commonly used tool for our clients with Power BI. However, the cost of Power BI is expensive, so the project often does not take off. I believe the biggest problem is that these business intelligence tools are usually too expensive.

The UI is very simple and functional for my clients, most of the clients that use the solution are not experts. They have fairly limited knowledge of computer usage, and they can create things with this solution. Microsoft Parallel Data Warehouse is very easy to use. 

The solution is expensive and has room for improvement.

I believe the cost is the biggest issue. In Brazil, money is not easy to come by, and paying for this stuff is difficult. Most of my clients are moving to the cloud and purchasing some of the infrastructure there, but it is expensive and they don't always get the economic benefits the cloud can offer. They are creating the infrastructure from the cloud and paying a lot of money for it, and other costs are becoming problematic. Power BI is just one example. The process is the biggest barrier here, and sometimes lack of professional knowledge is also an issue. It is hard to find companies that really know what they are doing. The project I am involved in now is creating a data lake in the cloud for a big client. They hired another company, not mine, to create the project, but when we started the meetings I discovered that the big company they hired doesn't really know what they are doing and is still searching for professionals.

I am currently using the solution.

A license is required to access Microsoft technical support. Some of our clients use the support and it is fine.

Technical support is an additional fee and is expensive.

The solution is expensive.

I give the solution an eight out of ten.

On any given day, we use Microsoft Parallel Data Warehouse to create an enterprise data warehouse for our customers.

Microsoft Parallel Data Warehouse integrates beautifully with other Microsoft ecosystem products. The solution makes it easy to build the code and maintain it. At the same time, you get enough resources in the market if you have any queries or need support for the ecosystem.

The feature updates on the on-premise solution come very slowly, and it would be great if they came faster.

I have been working with Microsoft Parallel Data Warehouse for the last ten years.

Microsoft Parallel Data Warehouse is a fairly stable solution.

I rate Microsoft Parallel Data Warehouse a nine out of ten for stability.

Apart from a few use cases that we are not able to do, the solution's scalability is fairly decent.

I rate Microsoft Parallel Data Warehouse an eight out of ten for scalability.

With Microsoft support and the ecosystem built around it, you can typically find help for your issues.

Positive

Microsoft Parallel Data Warehouse's initial setup is fairly simple. I rate the solution an eight out of ten for ease of initial setup.

A complete end-to-end setup of Microsoft Parallel Data Warehouse, which includes setting up the firewall and ensuring all the compliances and security features are met, could be a week-long activity. However, spinning up the resources is hardly a day's activity.

Organizations with a huge data size typically require Microsoft Parallel Data Warehouse. No small customer would like to go and invest in such an infrastructure. The solution's pricing is fairly decent for organizations with huge data sizes.

Overall, I rate Microsoft Parallel Data Warehouse a seven or eight out of ten.

We primarily use the solution for the integration of data with different sources and with historical data. We can put all of this into a company database once it is integrated. 

It's very helpful at a database level. It provides a lot of good integration potential.

It performs very well overall.

The interface is fine.

The product does offer different packages. 

The tools on offer for handling the integration are very helpful. 

I like the product and its performance. I don't have any notes in terms of improvement. 

It could offer more development across the solution. We do find DB2 to be a bit more robust. It needs more flexibility and features.

I've been using the solution for five to six years. 

The performance is very good. It is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. 

The solution can scale well. We're able to use it well even with clusters.

I've also used DB2. 

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.