The setup is straightforward so is rated an eight out of ten. 

The initial setup was a bit difficult.  There was a faulty management style that we created, but we were able to replicate it subsequently because you can do a number on each of the management styles.

Installation is easy. It has been changed the way it is being done. Once you do that, it's okay.

The initial setup of SQL Azure is simple because it is in the cloud. There is not a lot to set up. If you do it manually, it can take five minutes. If it is done through DevOps pipelines, such as TerraForm, then it could take twenty seconds.

I rate the initial setup of SQL Azure a nine out of ten.

I would rate my initial setup a nine out of ten, where one is difficult and ten is easy. So, the setup is easy. 

The product's initial setup phase is very easy.

The product's setup phase can be completed in a couple of clicks.

The solution is deployed using Azure's cloud services.

The initial setup is very easy. Anyone who understands SQL can set up the solution.

SQL Azure is easy to set up because it's already part of your cloud infrastructure. You don't need to do any installation.

Setup is straightforward. You just create an SQL Server instance account on Azure, and then you can create SQL databases. It's very easy to create tables and procedures. I mainly use the SQL data buckets inside Visual Studio. From there, I deploy databases to Azure from Visual Studio.

In Azure, deployment takes minutes. It's easy.

The installation was easy. They have a tool to assist with the migration of your old database to SQL.

The initial setup is pretty easy. Our team is interested in working for Azure and other Microsoft products. We don't require much support from Microsoft for setup.

Deploying SQL Azure is easy. It takes only one engineer to deploy.

The initial setup is complex.

We had to do some data collecting and we had issues with having redundant databases, meaning we had to do some synchronization between the databases. We did the integration of the networks and handled the clustering on top of the components of SQL. At the beginning we faced some issues, especially getting the servers to talk to each other. We needed to do some workarounds, but ultimately we were successful.

I rate SQL Azure eight out of 10 for ease of setup. In the worst-case scenario, deployment takes a few days. A couple of employees could do it easily. Usually, it's an admin and a developer. 

It was straightforward.

The initial setup can be straightforward if you properly configure the product and utilize scripts effectively. Once the script is ready for cloud deployment, executing it is next. The solutions architect sets up the basic infrastructure using infrastructure as code principles. It involves carefully selecting resources, such as VMs and app services, and configuring them according to your requirements. Additionally, one needs to manage security aspects like opening and closing firewalls, which can introduce complexities to the setup process.

The initial setup used to be a bit complex, but now it's much easier. I would rate it eight out of ten.

The initial setup is very straightforward. 

The initial setup is straightforward. 

It is easy. We only use one account, a Microsoft Azure account, and we can pull all templates from there. It's got an easy user interface and admin interface which makes implementation straightforward. All you have to do is deploy all the scenarios. After that, it will take some time and flexibility to understand the environment.

It takes six hours to finish all the setup, including completing the installation of SQL and integrating with Genesis.

The initial setup was easy for about five hundred users and it required just a couple of managers.

Installation for this solution is very easy, but you'll need to be a certified installer to find the setup easy.

The initial setup of Azure SQL is of a medium level of difficulty. We need some expertise in installing, configuring, and deploying Azure SQL.

The initial setup is straightforward. The designing process is involved in the deployment. 

I rate the initial setup of SQL Azure a nine out of ten.

The initial setup is very straightforward. It's not complex at all. For us, it did not take more than one or two hours. It was quick to deploy. 

We only need one person on hand for deployment and maintenance. They are a developer. 

Setting up SQL Azure is easy. Even I can do it. 

Its installation is very easy. We can easily move from one pool to another pool in Azure. It takes just one to two minutes.

The solution's initial setup was straightforward. I rate the process an eight out of ten. It took one or two days to deploy it. Since it is cloud-based, we followed the standard Azure mechanism.

The setup was pretty straightforward. The networking aspect was non-intuitive, and it was probably the biggest stumbling block when we initially set it up.

It's not complex and, in actual fact, it's easy. Ready made set-ups are available any time.

The initial setup is straightforward and only took one day.

We started with just a simple client-server kind of application. Right now, we are basically in the full-phased data lake solution of Azure. So, it is in the design and architecture stages. When it is finalized, then we will implement a full-blown solution on Azure.

You don't have to install it because it is on the cloud.

It is straightforward, but if you're migrating data from SQL Server, it is quite time-consuming and not so easy.

The initial setup of SQL Azure is difficult and complex. I have to use a lot of certificates, private keys, and public keys to establish a connection.

It depends on which area you're coming from. If you're using the GUI, it's relatively simple. Understanding what your needs are sometimes is a bit more complicated. Understanding the availability of things like Elastic pools took us a little bit of time to get our heads around but, otherwise, it is pretty simple. They could provide some use cases for this.

It is hard to provide the deployment duration because it wasn't just Azure on its own that we were having to deal with. We were taking our on-premise product and converting it. Preparing the infrastructure and doing it via the likes of Terraform took us probably about three months overall, but that was more about getting up to speed on the tools to do it, as opposed to individual components such as SQL.

The initial setup was incredibly easy. Moving from a standard tier to a business tier is not so easy and the documentation isn't so clear the presence of the read scale out copies.

You don’t have to install the product on the cloud platform. You receive a login with pre-pared software installs. Custom requirements need to be implemented or requested.

The initial setup depends on the requirements but is easier than the on-prem SQL.

The initial setup for the solution is easy. It takes around 10 to 15 minutes to set up the solution. The deployment of the solution is straightforward.

Our implementation was straightforward and carried out internally. We have 10 users of this solution, the majority are in production and engineering, with a couple in software engineering. 

The initial setup is pretty easy. The deployment took about a day.

The solution’s initial setup is straightforward.

The initial setup is straightforward. I rate is as eight out of ten.

The implementation of SQL Azure is simple.

Setting up SQL Azure isn't complex.

The initial setup of this solution is usually complex, especially for an enterprise customer. This solution is tailored to specific customers, which is why complexity varies.

The typical deployment takes six months.

The initial setup is more complex than it is straightforward.

The easiest deployment requires an hour. If you have a one-by-one project that consists of migration and replication, it can take several weeks.

The initial setup isn't complex. It's pretty straightforward. However, it does take a long time to provision and manage everything. It can take a couple of hours typically to deploy the solution.

The initial setup is straightforward and the installation is simple.

It only requires you to get a subscription. Once you have downloaded it, you can create it as a resource and you can already use it.

The number of members required to maintain this solution is dependant on the server.

The setup can be a bit of a challenge until you get used to it. Once you have familiarity with it, setup is okay and takes about 30 minutes. 

The initial setup was straightforward. It took less than one day for deployment. I have a lot of experience, so it might take others three or four days to complete a setup. You only need one person for deployment and maintenance.

We don't install it. We just use it. It is my understanding that in Azure we don't install anything. We go on Amazon or Microsoft and make a machine. There's no installation.

It is too easy. Initially, the database engine itself takes an hour, and that's it. Tuning it is another matter, but tuning is anyways a difficult task in itself.

I haven't had any complications setting up SQL Azure.

The initial setup was very straightforward. It's online, so I didn't need to install anything. I just had to choose options and activate them. 

The initial setup was quite straightforward.

The initial setup was very complex. It is hard to explain, but the problem is when you have more than one service. We have only one service but the solution has multiple capabilities. 

The deployment team installed the solution on one machine at a time, so it took very long. I chose a big database and within less than nine minutes I was able to collect data. So that was much faster.

The setup is super straightforward. I don't really find that question useful, or at least as useful as, "What is it like incrementally adjusting the design of the database?"

This is where Microsoft's eco-system further outshines the alternatives. Again, this is a much longer discussion, but it's folly to choose a platform, and even a technology, without considering the lifecycle of changes.

In an agile world, you have to ask how you are going to get that data tier to respond efficiently and within business requirements and tolerances.

The configuration was straightforward.

The solution is very easy to set up.

If you're going into a cluster with multiple width or multiple SQL Servers, deployment becomes a little more tricky. In general, though, the initial setup is relatively easy. 

It is easy. I'm busy setting up another one now.

It takes some time to get accustomed to the Azure portal and to navigate through its tools and options. You can also connect directly from the SQL Server Management Studio. It is fairly easy to configure the proper parameters for connection. Once you are connected, it is transparent for any experienced SQL Server DBA or SQL developer.

The initial setup is straightforward and I don't find it complex.

It was easy to install. There was not much challenge with the setup.

The initial setup is easy.

The initial implementation is straightforward. There are a few click-throughs and you have ready to use infrastructure. It usually takes five to ten minutes. Even less.

The solution is a cloud product. You don't need to install anything. There is no installation process to deal with.  

The implementation process only takes a few hours with Azure, however, they do need to make the process a bit better. The upside is you don't have to scroll through everything manually as you do with an on-premises deployment. It's not overly complex.

The initial setup is straightforward and the deployment is very easy because it's a UI based migration. There's no hard coding. I believe deployment takes maybe two or three hours to get the environment set up and to be able to start exploring. We had one person  responsible for deployment and we have three or four people dealing with maintenance in a company of close to 200 people. 

The initial setup is very easy. It's extremely straightforward.

The initial setup is straightforward. It took approximately one week to complete.

The initial setup was straightforward. Deployment takes about one hour.

The initial setup was straightforward. It was not a big deal. It took a few minutes for features like .NET.