What is your primary use case for Microsoft Parallel Data Warehouse?

For the last 10 to 12 years, I've worked as a data engineer on different projects, and in some of them, we have used Microsoft Parallel Data Warehouse. It's something that I've worked on and off for quite some time, but not something that I work with on a daily basis.

These are all very custom development for the customers. I work for my customers as a consultant, so whatever platform the customer has, we provide services on that platform. We are platform agnostic. My personal preference is Microsoft Parallel Data Warehouse, and I'm doing some consulting work on that, and actually hands-on work also. I'm very pro Microsoft because I think Microsoft products are highly intuitive and are widely used. The integration capability is good, and it integrates pretty easily with multiple ways of doing something.

I use Microsoft Parallel Data Warehouse ( /products/microsoft-parallel-data-warehouse-reviews ) for the logistics area related to the transportation of the company.

I use Microsoft Parallel Data Warehouse to construct and manage a data warehouse. I mainly write SQL queries to manage the data.

We use it to build our data warehouse and databases, and everything in the back end.

We use the product for data analytics purposes.

We can use the solution for financial, banking, insurance, or retail sectors.

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

I use it at the office to access data.

In my company, we use Microsoft Parallel Data Warehouse in some of our projects, including loading the data of multiple data locations in France to employed data warehouses.

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

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.

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.

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.

We primarily use the solution for data.

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 are primarily using the solution to convert to different dashboards and to collect all of the metrics and data.

In the past, our use case for the product was just to collect data from different data sources. Now, we are trying to build websites and the business intelligence layer above the SQL Data Warehouse.

We provide this solution as a service to customers. Sometimes, it is just used as a data warehouse. However, a couple of our customers use the data warehouse to collect information from everywhere, e.g., from their subsidiaries, such as electric or petrol companies. We are also developing some dashboards using the data warehouse. Sometimes, you are using Microsoft BI, but most of the time, you are using Qlik. It depends on the customer needs at the end of the day. Most of our limitations until this moment have been on-premise. There is some sensitive information, like the billing system for an entire country's electricity. However, because of the current circumstances with COVID-19, we are discussing with them how to move it to the cloud. Mostly because of the regulation that any government data cannot be hosted on a cloud, we need to host it on a local cloud at the moment. We cannot use AWS or similar things as of now. While we do have local cloud vendors that we are working with, this is something in progress.

This is a solution that we implement for our clients. We provide end-to-end development, maintenance, enhancement, testing, and support. Everything is done by us.

We primarily use the solution to build up our server analytics.

I am a consultant and I assist in implementing this solution for our clients. The projects that we are working on right now are related to finance, banking, and government.

I am using the Microsoft Parallel Data Warehouse for working with information services and datasets, creating reports. It is used primarily for our historical data, but we do some in real-time also. We can receive data weekly, nightly, or even hourly.

The primary use cases for this solution are for recording and transactions.

I have mostly worked with analytics, so I normally use SQL to put in data for analysis. I have worked on building dashboards as well.

We use this solution for keeping track of sales, goods, times of shipping, and other information. It is used for our KPIs.

I work for a Microsoft partner. We're one of the Gold partners, so we implement on their databases. We are also Dynamics 365 specialists, and I'm a Business Intelligence consultant, so I do SQL, Power BI, Azure SQL, SQL Data Warehouses, and a few others.