It is basically hosting the backend of our application that we write as a software development company. We're moving our educational timetabling software, which was historically an on-premise installation, to a cloud-based service offering for customers.

It is pretty much version-less in the sense that we are using whatever is presented to us and available. We are purely using the cloud-based services from Azure hosted in the cloud, which obviously and technically is version-less to some degree. We are using SQL Azure, app services, Application Gateway, key vaults, and storage solutions within Azure. It is relatively simple but sufficient for our needs at the moment.

We predominantly don't use the GUI interface. We are using Terraform as our infrastructure and code provider to manage and maintain all of the Azure components that we are using. They're offering all the integration and providing it through the APIs.

It is simply our relational database.

We're slowly progressing through the delivery of our production system or landing zone in the cloud. Nothing is in production yet.

We primarily use the solution for its Data Lake and Data Warehouse, in both cases for our customers.

We are using it for an application in two different models, the PaaS model and the SaaS model. One is the product, so we are using it as a SaaS model. We are using the other one simply as a PaaS model.

For its deployment, we are sort of using the highest model in which one instance has only VM and the SQL installer on it. Another instance is simply using SQL Azure.

Azure has multiple use cases. Organizations can use it for hosting infrastructure, for example. There are cloud services that you can utilize. The main purpose of the cloud is that you don't need to set up your own data center, and then you can just use the cloud platforms provided by Azure or AWS, or any other cloud. They all serve the same purpose.

As consultants, we deploy this solution to our customers both on cloud and on-prem. Most of our clients buy the solution as an application package which requires a database. If they are a "Microsoft shop," I recommend they use SQL Server. I'm the development manager and we are customers of Azure.

I work for a consulting firm which uses the technology marketing projects from Microsoft and other IT vendors, re-routing the product, and creating a technical and architectural guide;  basically I work on the consulting assignments. I am a lead consultant in one of the leading IT companies in India and I've been implementing bridges and consulting in an architectural support role. I've been using Azure as a stack and that's where my proficiency is. We're partners with Azure. 

The solution is primarily used as a database.

We're using it for scalability. Everything is on Azure SQL for us. It is an enterprise application data warehouse, so all our applications are on this. It is useful for entire data warehousing. It is also good for microservices applications. We have its latest version.

We use it also for database management, as a database engine.

We use it for different projects - mainly when we have lots of data and the customer can't afford to pay the license for SQL Server, which is not cheap. That's the main reason we use MySQL or Postgres or other databases. 

We use it for benefits management in the healthcare domain. 

We are in infrastructure development. We are using this solution with Power BI to consume the data.

We are creating on top of this SQL server. It will be consumed by Power BI for the customers, where they can customize their reports. 

We have multiple use cases for this solution, and it really depends on the application team requirements. Our analytics team uses it. We also use it for database migration.

We provide managed services using SQL Azure to our end-clients. The price of services is fixed, and we manage the resources according to their needs.

SQL is basically a relation database, it can be used for any key-value related data models. Anything which is a table and column-based can be used. If you are an already existing SQL customer or a document tester worker, then I think it is common to go for SQL or Oracle. More present, you have Cosmos DB, it can be used as both SQL and NoSQL databases. This is the database that we are exploring today, and what we are using more.

Our core business is to make mathematical models for production and solutions. We don't develop or use software. The data comes with the Excel format stored in SQL and we write complex queries about the data and run it in our models. Our data is not sensitive and it's a matter of having a server for storage. I'm a software engineer.

I use SQL Azure strictly for active data rescue.

All of my work is stored in the Microsoft Azure Cloud.

I am working on a special product with another person — it's a secret product, so, unfortunately, I can't talk about it.

We are deploying a few server-based applications, and we are using the Azure SQL database.

We use a relational database management system and 90% of the projects I've worked with have used SQL Server. We are partners with SQL Azure. 

It is a transactional system. We use it to visualize financial transactions, such as cash in, cash out, in real time.

We are using it for business intelligence and analytics.

I'm an end-user. I'm a business analyst, so I'm using SQL Azure to do analysis.

We normally use it for development and other services. We have on-premises as well as cloud deployments, but it is mostly deployed on the cloud.

We use this solution to store data MODS that are going to be consumed by Power BI.

We are using it for processing financial transactions. We have its latest version.

We are using SQL Server both on Azure and in a Spark environment, on-premises.

We use it as a backend product. We are using the Managed Instance and the SQL Database.

I'm in charge of the development of our IT solution and I am an implementer of Azure. 

We are using it for a database.

I have used SQL Azure for the backend tier application. If the customer has the flow change application with an application service, they will use the backend. I always suggest using SQL Server and Azure.