Our company uses the solution for on-premises production and PR. We sync data from the database service to our on-premises SQL server. 

Our primary use case is creating management-related items for SQL for the development of a variety of items we are working with.

While we have a trader client or warehouse management, we use SQL Azure because the volume of trading activity keeps changing. Maintaining on-premises solutions or infrastructure for this is difficult, as the user demand can fluctuate significantly throughout the month. For example, at the end of the month, there is a high volume of orders and data as traders push their orders to their incoming entries. This can cause the user demand to spike and then drop off again. Hence, we need a flexible infrastructure that can scale up and down to meet the changing demand.

I am using SQL Azure for migrating existing SQL Databases into the cloud. 

I work for a service-based company that helps businesses migrate their applications to the cloud. So, we're implementers. We help with the migration process. 

We primarily use Azure SQL when migrating data from legacy systems to the cloud based on customer preferences. If customers are looking for an Azure solution, we often recommend a Dedicated SQL pool based on their specific requirements. This allows them to store their data in cloud storage services and access it easily through the database.

Scalability is a feature associated with SQL Azure. The primary use cases of the tool are for the retail sector where there are transactions, specifically high peak transactions during Black Friday or month ends, where people go on a spending spree after their salaries get credited to their bank accounts. Different sets of transactions have a few peaks during the month, especially during festivals or marketing events. When it comes to transactions in the retail sector, there can also be low peaks during the middle of the month. To address the high and low peaks in transactions, SQL Azure has a feature that can scale automatically to support a period involving a high level of transactions. Similarly, SQL Azure can automatically scale down to support fewer transactions. Whenever SQL Azure scales up, you need to pay the additional or premium fees associated with the extra use due after the product scales up. When the tool scales down, the cost reduces automatically, and you only pay according to your subscription.

We use the solution to create a relational database for a client. They were running SQL on-premise and wanted to migrate to Azure and create a single data warehouse.

I'm using SQL Azure mostly for database purposes, including data modeling, data architecture for business applications, and also for Data Lake.

We use SQL Azure to store our relational data. Whenever I have complex relational data with consistency requirements, I use SQL Azure Database.

I'm currently working in a small startup. There are just two people using this solution now: a developer and myself. I'm working as a technical consultant and an architect.

We are using this solution for analytics and business intelligence.

The solution is deployed on-prem and on cloud. The cloud provider is Microsoft.

There are tens of thousands of users. In my market in Poland, there are maybe 1,000 using the application based on the solution.

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. 

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 customers in the bank sectors use the solution for their websites. Our private customers use the solution to customize their applications on the cloud because they do not want to buy separate hardware. Some of our customers also have their on-premise SAP hosted on Azure.

We use SQL Azure to integrate the on-prem resources with the cloud. It creates a replica of our database in the cloud. We have more than 50 users.

Our primary use case is for content management and publishing offsite for external users. We also use it as the intranet to get the largest professional view of the SharePoint version.

About 25 people in my office use SQL Azure. Including customers, there are about 400-500 people.

We have a lot of stuff that is still on-prem, and we're only sticking our toe in the water with SQL Azure. For what we're doing, it is a simple database. We haven't yet put any of our harder stuff on Azure.

SQL Azure is in the cloud. So, it has to be the latest version. It is version agnostic.

We use the product to extract data and present it for warehouse reporting.

I'm currently involved in setting up pipelines on Azure for data extraction from a source to a target destination within specific time intervals. The goal is to automate the process of moving data efficiently.

The solution is used for a lender's business application. 

This is one of the applications where we are supporting in production.

If we are using SQL STL, it is a manual process. If we use STL Azure, we will import all the templates from the Azure cloud or Microsoft cloud. There are already pre-defined templates and pre-defined procedures in Azure. We will be using those instead of manual processes. Azure is helping us to be more flexible and handle time scaling.

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

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.

Our primary use case of this solution is to host our databases and it is fulfilling our requirements.

We use Azure SQL serverless or with virtual machines.

Azure SQL is used mostly by my clients for ETL.

 We use it for supporting an application from another platform to Azure.

We are using SQL Azure for databases that are hosted in Microsoft Azure.

We decided to implement some forms for different purposes. We needed to implement it on-premises, so we did this on Azure to support the data from the forms implemented on a SQL server, and on Azure on several databases. It's very easy. 

We use SQL Azure for what we call an inspection round. Inspection rounds are mainly used by an inspector in the field to check the compliance of the equipment, like if a given machine doesn't have enough instrumentation. 

In any kind of plant, there is an inventory of assets. Most companies have an inspector who goes to the field to check the condition and record some indicators. The results of the inspection are recorded in our software. All the data from the inspection round is stored in our database in Azure. That is what we use the Azure database for.

We created a custom PaaS. It's not a pre-built device in the cloud. Azure components like SQL Azure and a web server are combined to create this solution. Our SQL performs better in that space than a readymade device.

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

We use the solution as a customer database for travel desk applications.

It is simply our relational database.

We use SQL Azure for the SAP application, an accounting software that facilitates transactions between different departments. The financial trends we run on SAP are supported by SQL, which is the back end of that application.

The primary use case is to pass services for applications of some customers, where they have maybe the front end in dot net and another language, and SQL service in Azure.

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.

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 for benefits management in the healthcare domain. 

We have HR applications including a lead system and also traveling expenses. We're using SQL for items like that.

SQL Azure is used for the replication of a CRM database. if get information from this database and try to replicate it on other servers and other systems. I'm getting the transactional data information.

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.

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

We use the public cloud model of this solution. 

The solution is used to manage our databases in the cloud.

We usually work on a valuation basis. When a customer wants to get on to our cloud, we suggest SQL Azure to them.

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.

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

Our primary use case for the solution is for applications. We get many applications in the environment, and most applications use Microsoft SQL, Azure SQL, and DBs, and a few use Postgres SQL. So primarily, the focus is to connect with the DB team and have a specific expert in the SQL environment.

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.

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

We offer this solution as part of a bundle to our customers for which we offer technical services. We are aiming to have a centralized marketplace.

We have experience with hybrid, on-premises, and public cloud deployments. We have a complex environment and are slowly transitioning to this solution. Our production environment is the only one that we're putting into Microsoft Azure. For security reasons, we still have some systems on-premises.

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

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. 

I use the solution for database maintenance. 

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

I primarily use it for accounting and ERP solutions.

The solution is primarily used as a database.

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.

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.

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 am a consultant and some of my clients use this solution for their database.

SQL Azure is a platform, as opposed to a product. You do not select a specific version. It has very little administrative ability, such as the ability to back it up, but it offers much more comfort for the user.

Our primary use case for SQL Azure is to operate our database.

We use this product to implement solutions for clients, so the use case can vary. For example, we built a web-based application for a government environmental protection agency. They issue permits to prospective applicants looking to site factories and other business facilities.

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. 

We are using it for business intelligence and analytics.

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

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.

It's a platform that we leverage for multiple uses. There isn't a specific primary use case for the solution.

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.

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. 

I primarily use the solution for continuous integration and continuous delivery.

I primarily use the solution to study SQL.

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.

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