Installation is simple. I handled the installation alone, and we performed the entire deployment in DevOps. You need at least a five-person team to manage and maintain the solution 

The setup is quite easy and similar to Jira. 

The initial setup is not complex. It's pretty simple and straightforward. 

There was a pool of DBAs that maintain all the Data Warehouse on-premise and cloud. There were hundreds of databases, and this is just one of the databases added to that list. The DBA team is comprised of five to six DBA team members.

It is fairly simple. It is a fairly simple tool to set up. It is all just clicking buttons. There is nothing overly complex to the initial setup process.

In terms of maintenance, it is a cloud product. So, the updates happen behind the scenes.

The setup of Microsoft Azure Synapse Analytics is different than anything we've used on-site. It is different from the Analysis Services five years ago. However, even though it's different, the setup is easy.

The initial setup is easy using the infrastructure code. The deployment takes a maximum of a day to complete as we conduct a POC enrollment before the setup. It helps us understand the process. Later, we develop it in the production environment.

If the person has a general understanding and some basic knowledge of the subject, setting it up shouldn't pose a significant problem or challenge. I would rate the setup an eight out of ten.

There are multiple teams, each with their individual setups, while the overall backend configuration and maintenance tasks are handled by a dedicated team. This team might be a global team consisting of more than twenty members who manage these responsibilities.

I would rate my experience with the initial setup an eight out of ten, where one is difficult, and ten is easy because it is quite easy to set up. It is a user-friendly tool; even a new user can find a workaround. 

I have not seen any complexity related to the setup. It is quite easy. It took a couple of minutes to set up. 

I don't think it's very complex to implement. We have our own expertise. We have our own IPs to set it up and therefore it's not really complex. It takes a week to ten days to have everything up and running. 

Typically, a pool of six or seven people should be good enough in terms of handling deployment and maintenance. Usually, it's comprised of a mix of managers, admins, engineers, and/or developers.

The initial setup is easy. It does not take much time to deploy the solution. 

The initial setup of Microsoft Azure Synapse Analytics is easy.

It's a very simple setup. it's not overly difficult at all. 

In terms of maintenance, it depends on the scope of coverage and other things. If it is a 24 by 7, we need a set of 14. Depending upon the service coverage and scope coverage, you'll need a certain amount of people. Even that depends upon the scope of the work also. Does the setup require monitoring, for example, or enhancements? Basically, it depends upon the type of contact, and what we get into the AMS projects in terms of the team composition.

I rate Synapse Analytics eight out of 10 for ease of setup. I've set up Synapse so many times in various environments that it's seamless. I have no issues with the product at this point.

We did extensive research and a POC before implementing Synapse Analytics. It took us a couple of days to deploy, including the POC. We had to separate our groups and stuff like that. The second step was to leverage templates for creating the environment. Everything is automated now. If want to do this again, I don't have to go to the portal. I can run it from a template. 

The initial setup took us two weeks at the beginning and now we can do it in less than one week.

The initial setup of Microsoft Azure Synapse Analytics is straightforward.

It was very complex, but we have grown out of it now. We have at least six environments only on Synapse.

I would rate the initial setup a seven out of ten. The initial setup was good.

The initial setup is complex and I rate it a four out of ten. 

The initial setup was straightforward.

The solution is easy to set up initially.

The initial setup was straightforward.

The initial setup for Microsoft Azure Synapse Analytics is straightforward because Azure makes it very easy. Any Azure solution is very user-friendly, but you just have to know how to use the solution, and that's it. Setting up Microsoft Azure Synapse Analytics is not that complex if you're knowledgeable.

The setup was complex the first few times but we figured out the best way to do it for our mid-sized customers. The setup could be made easier. 

I rate the initial setup of Microsoft Azure Synapse Analytics a seven out of ten. 

The initial setup of Microsoft Azure Synapse Analytics is simple. It's a managed service in Microsoft Azure, you only need to search for it and install it.

The initial setup is straightforward. We can have the dedicated SQL up and running within 15 minutes.

The initial setup is very straight forward. Azure Synapse offers you one workspace where you can do everything, creation of your data warehouse, ETL pipelines using Azure Data Factory, Create storage and data marts. Also use Power BI for visualization. 

Before Synapse was available, all of these was offered as separate services and this is how a data warehouse was constructed. Synapse is one layer on top of this where we make use of one single workspace to initiate and manage the entire set of services that you need for creating and managing your data platform - Data Warehouses and marts using SQL Warehouse, ETL pipelines using Azure Data Factory, Data Lake using Azure Blob Storage, and it offers server-less SQL - meaning you can run queries without having to initiate an SQL database or SQL data warehouse instance. It also offers Spark compute to process non-structured data.

The initial setup is simple, and I would rate it at ten out of ten.

I'd rate it a nine out of ten in terms of the setup. It has a GUI, which is awesome. Its deployment duration varies based on the case to case. We have quite a few SMEs for deployment. 

It doesn't require many people for maintenance.

It is a straightforward setup. It's easy and not overly complex. I have not measured how long it actually takes; however, I can say the implementation is convenient. My administrator handled the setup. I did not handle it directly myself. 

There is a steep learning curve to do the implementation.

I rate the initial setup of Microsoft Azure Synapse Analytics a seven out of ten.

The initial setup of Microsoft Azure Synapse Analytics is straightforward. The full process took a couple of weeks when we started and finished.

Because I was not familiar with the solution beforehand, the initial setup was quite complex. I had to learn a lot in the beginning stages. I'm grateful that there is help to be found in the Microsoft forums, however, and there are also options to study for certifications that help you learn how to use the platform properly.

The initial setup is straightforward. It's a matter of connecting to your visual studio or management studio.

The initial setup is easy if you have information about analytics visualization and data warehousing. It's easy enough to install and configure the blade. It takes one day to deploy the solution.

The initial setup was straightforward, and I would rate the experience as 4.5 out of 5.

The initial installation is straightforward. There is a lot of documentation provided by Microsoft making it very easy to get started.

The documentation is good, but if you cannot find the right documentation and the right steps, then the initial setup can be hard. I would rate the initial deployment at seven out of ten.

This solution is deployed on the cloud, and it took half a day to deploy it. I configured the data lake storage, created the workspace, and added users and user rights. Building pipelines is a straightforward process.

The initial setup is not too straightforward. It's rather complex. We had to get some outside assistance.

The deployment process took us about three months. It was a while.

The initial setup is very easy.

You couldn't be a novice really and follow it.

As long as you were using the tools already, it's pretty straightforward. 

They do have resources you can contact.

You could have one or two of your team join the Microsoft groups and learn more that way as well. 

There is a lot of planning and setting the right people in motion to work with it.

The initial setup is straightforward.

In the initial setup, to make it really easy I have, for instance, just a plain Excel sheet retrieving information in and one information system which brings in live data giving you a good starting point. It is not a really hard setup, to do it is quite straightforward. In the Netherlands, there are some major players concerning electronic client dossiers and electronic patient dossiers. Once you go through the complexity once you can then re-use it for a different customer.

The deployment just takes approximately two hours. It is the testing and the acceptance, and what to get out of the product, that is going to take a longer period of time. This could take up to a couple of weeks to a couple of months.

This solution is relatively easy to set up and use. The time it takes to setup depends on the complexity of your environment. If you want to complete a basic setup, it only involves a few clicks. In a production environment for a complex setup, it's it takes some time to complete the configuration. 

It's a complicated product.

The initial setup for me was straightforward, but I have a lot of experience. I think that for some people who are less experienced it would be complex.

It's not just the documentation on what version you need to have and what pricing. It is really difficult.

You have to read a lot to understand what you are doing.

The initial set up was not very complex. It was easy to install this product.

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.

I did not handle the initial setup. That was handled by another party. Therefore, I don't have any insights into the process or how easy or difficult it was to implement. 

The initial setup is very complex compared to other products. It takes weeks to deploy.

The initial setup wasn't complex. It was okay. It wasn't complex at all.

To set it up within full compliance with our cloud infrastructure team, I'd say maybe two weeks after beginning our testing. I'd say the team wasn't a hundred percent devoted to setting it up as they had other things to do. So I'd say I'll give it two weeks to be realistic for a large organization.

It's hard to gauge the difficulty or simplicity of the setup. For our company, we were learning the processes as we were doing it. In that sense, it was challenging due to the fact that we had to learn and then do. After a period of time, we were able to get comfortable.

Configuring this solution was easy.

The solution takes longer to set up than I would like. There are a lot of questions that need to be addressed with the customer, and this can draw out the process. 

The initial setup is very straightforward. It only took five minutes to set up.

The initial setup was very straightforward. It took only five minutes to set up.

The initial setup is not difficult. If you have access to the subscription you can start using Azure Data Warehouse and being to create the services. There are security features also. You can give someone full access, and you can set access for others too. Developers will need access so that they can develop it out. It's a pretty straightforward process.

The initial setup is pretty straightforward. It has been a long time since we first implemented this solution, but since that point, we have created a custom handbook that we can follow in order to set it up.

The initial setup is very straightforward. It's not overly complex. A company shouldn't have any issues with the initial setup or implementation. You don't need deep technical insights to have training.

You can create a floor space in an hour. That's no problem. Afterward, you have to work with the data and do a few more things in terms of configuration, however, it's not hard.

The initial setup is complex. It's not straightforward.

In many ways, implementation is a never-ending process, as there are always things to improve. In a few months, most of our people are familiar with the product and have a good sense of the basics, however, there's always more to do.

The initial setup is straightforward.

It was ready when I started to use it. I just had to do my project.

The initial setup is straightforward.

It is relatively straightforward as long as you understand what you're doing.

The initial setup is straightforward.

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.

The initial setup is straightforward and takes around two hours. 

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.

The initial setup is not complex at all. It's pretty straightforward. I'm not that technical, and I was able to handle it.

The initial setup is straightforward. The requirements are very clear, and there is not much of a problem when you're doing it.

One of the recent upgrades we have done that included high-availability, loading the data, and setting everything up, took about a month and a half.

The initial setup is straightforward.

The initial setup of this solution is straightforward, with no issues.

The deployment took about three and a half months, although the time was not because of Azure SQL. It was our ETL tools that we used in-house during the deployment.

We have one cloud engineer, somebody from Microsoft that helps us from time to time, and someone from TPC who assists with the maintenance.

We installed Datawarehouse in a couple of minutes. However, the configuration based on our data models took time. It can take us weeks because that's where our optimization sits. Just tuning the parameters can take several days' at a time. 

It is complex. There are too many products that we need to involve in its setup, such as data factory and machine learning, and they're integrated so intricately. You need to have quite good skills to work with this. You would need a partner. You cannot do it yourself. The deployment usually takes a month.

The initial setup was really easy and straightforward.