The initial setup was fine and straightforward.

The migration process related to Microsoft Parallel Data Warehouse has been going on for a month in my company. We have multiple labs, of which it was possible to load the data in 47 labs. With one lab, it took almost a week to load the data since the data count was in millions, due to which it initially failed multiple times, creating a huge issue for us. It's all done right now, but we have faced issues in the past.

In our company, we created new databases in the new SQL Server. We replicated the databases, and then we got the data from there.

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.

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.

The initial setup is okay, but that can also be improved. They could integrate the solution into Visual Studio into SQL Server and get things done. Deploying the packages requires going through an interface in SQL Server and then going through Microsoft Visual Studio instead of doing it directly from SQL Server. The deployment does not take that much time, but it will take a little time.

Maintaining the solution is easy. At some point, you could do something, and it could break, but I can find the logs, find the error, work on it, and resolve things.

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.

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 setup is very easy. The deployment takes one day. The deployment has a lot of steps. We need one or two engineers to deploy and maintain the tool.

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

The initial setup is straightforward. There is a lot of help available to assist with each step, so it's pretty easy.

The deployment took longer than expected because of continuous improvement and upgrades that were needed for the projects. Once we started and got a handle on how this solution could benefit our projects, we had to incorporate those new ideas. In total, it took between one and a half and two years to deploy.

The initial setup is really easy. We don't need to do anything major. The deployment takes a few minutes.

The number of people required to deploy the tool depends on the number of environments we have. Usually, one architect is enough to deploy the product.

I was not part of the initial setup, although I assisted with linking our ERP systems to SQL and that is pretty straightforward. There was not much complication in terms of linking the data and how it was being stored.

I find this setup of this solution to be simple, but that is based on fifteen years of working with it.

The initial installation and setup were easy and we did not have any issues. The deployment was completed within hours.

The initial setup was quite complex. The time deployment takes will depend on all the components they specify. We've had deployments that took a couple of weeks, and we've had deployments that's been spread out over multiple years, because we cover 60 countries, in six continents.

I think the initial setup was easy. I think you have to count the time that it would take to deploy in days rather than weeks.

The dedicated team where I work built the setup and we deployed this product by ourselves within your company.  

The initial setup was straightforward as it is an appliance. The Microsoft support team work closely with us. We always do it in collaboration with the vendor team and thus ensure we get the best out of our investment. The project team is involved during the initial setup process, and thus optimal installation is ensured.

If everything is available, such as information knowledge sources and connections, I can have the solution deployed in five days.

The initial setup is definitely complex.

We are not always aware of where the data comes from because it is distributed. Sometimes the data is fine and sometimes it needs to be set up. Once it is configured then it runs fine in parallel.

The length of time for deployment depends on the size of the data and whether we were also implementing a data warehouse or a data mart. When I was implementing this solution and copying data, it took between six and eight months. That is end-to-end with everything finished.

If it is a small data mart then it may only take a month.

The initial setup is not difficult. It is easy and we are fine with that.

The initial setup was complex. It was fairly challenging to migrate from SQL server to PDW.

The initial setup was straightforward. We had a knowledgeable team working on the implementation. Deployment took about six to eight weeks.