What is your primary use case for SQL Azure?

We have a web application that we deploy on Azure, and we use SQL Azure as a database to store the data.

My main use case for SQL Azure is for a self-reading application related to portfolio management. In this application, users can have portfolios designed and managed based on recommendations from their brokers. These recommendations are sent to users, and if consumed, they get executed and added to their portfolios, which can be easily maintained through mobile applications. This involves using Kafka for messaging and execution.

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.

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.

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

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

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

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 the solution as a customer database for travel desk applications.

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

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

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.

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 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.

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

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 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.

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

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.

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.

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.

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

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 are deploying a few server-based applications, and we are using the Azure SQL 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.

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 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 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.

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.

The solution is primarily used as a database.

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

We use it for benefits management in the healthcare domain.

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.

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.

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

I'm in charge of the development of our IT solution and I am an implementer of 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.

It is simply our relational database.

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 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 it as a backend product. We are using the Managed Instance and the SQL Database.

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.

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 using it for a database.

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.

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

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

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

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.

We use the public cloud model of this solution.

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

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.

I primarily use it for accounting and ERP solutions.

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

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.

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.

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

I primarily use the solution to study SQL.