What is your primary use case for SQL Server?

My usual use cases for SQL Server include everything, as it functions as both a data warehouse and OLTP system, among many other applications. SQL Server serves both OLTP and OLAP purposes since the scope of what I do is quite broad.

For SQL Server, we use applications for transactional operations, reports, and financial applications. Financial applications are a primary use case. Reporting Services is the best use we have with SQL Server, particularly for processing and generating financial reports. We only use it for reports, while we utilize another tool for dashboards.

My experience with Microsoft products is very good. In my job, we are working with reporting services. We have emulated SSRS server from on-premises server to the cloud, and now the server is running on the cloud. The first one is very good, and all the products that we have running are okay for us. Another product from Microsoft that we are working with is Visual Studio 2022, and we also have projects with Visual Studio 2017. Additionally, we are working with business intelligence products projects; we have development projects to extract information from our databases and then produce new reports or new information using DTS or ETL projects with the integration services project. We are using SQL Server as the database for all the applications that we have. SQL Server is a good solution for me. It's easy to use, and I appreciate SQL Server Management Studio because it is user-friendly and has good performance. The services and patches are very easy to install, and I don't have any problem with the SQL Server database.

Most of my clients are looking for a solution within the cloud on Azure and SQL Server databases. It is very cost-effective and scalable, meeting all requirements for small to medium-sized enterprises. I generally do not deal with big enterprise organizations that need large data warehouse solutions, however, it fits the needs of those with small to medium data volume requirements.

I use SQL Server for its user-friendly interface and cost-effectiveness compared to other databases like Oracle.

We use SQL Server to query our database for specific reports we need to write for our clients.

We use SQL Server to host our ERP system. It serves both as the underlying database and server application software. This database solution handles all our ERP calls.

We use the solution as the backend for the application.

We do backups or restore or query tables to create the views, create some triggers to send the attachment report files, and to report on data.

We use the solution to install different databases.

Most of our clients use SQL Server as a back-end source.

We use the solution for continuous integration, including CI/CD integration.

We extracted data from SAP and stored it in SQL Server. We created a connection between the Data Services Server and the SQL Server. If anything went wrong, there were SQL Server experts who took care of everything. So, we extracted data from our ERP system and stored it in SQL Server.

The solution is used as our backend database for our in-house applications.

We use it for warehouse data management, as well as for statistical reports. It facilitates tabling and query processing while supporting multiple database operations.

We use the solution to provide the database layer for multiple applications.

This is the main database for our financial system. I'm the IT manager and we are customers of SQL server.

We use this solution to store our data and for running queries, simple select queries that enable me to create the views I need and report from those views. I'm an ESM specialist and we are customers of SQL Server.

It has all of our data. Our company sells contracts when you buy a car. We sell aftermarket insurance for the tyre, wheel, ding, dent, windshield, etc. When somebody buys a contract, we capture all of that data into a legacy database PostgreSQL, and my task is to incorporate that into our financial platform using T-SQL. So, I write queries, procedures, and views. I use SSIS, and I use SSRS. My job is to get the data into our financial system so that we can process claims, payments, cancellations, and refunds. In terms of its version, we're up-to-date. We have version 2019.

We use SQL Server for developing systems.

We are using SQL Server for data processing.

It is for supporting our custom applications. We have a number of custom applications that we use that have SQL embedded. I am using the version before the latest one.

All our databases are using Microsoft SQL. It supports our application, such as HR and finance.

SQL Server is only running in China, it is not connected to our site. We have some PCs running on Windows 7, but it is not supported.

We developed a product for banks and we store the data in SQL Server.

We use SQL Server for storing all our company information, such as ERP, customer applications, and our wealth management systems. All of our data is stored in SQL Servers.

I'm a web developer, and I use SQL for the backend.

We do data warehousing on it. We have databases on it. A lot of our applications use it for transactions and data. We're using version 2019. We're trying to migrate to 2021 because 2023 is not yet that stable.

We use the solution on FastAutomate, our core product, to store the aggregated data from different nodes. It resides on the server that's handling the agents. We also use it for different organizations for development. Therefore, we use it for development mainly.

SQL Server is our primary database for identity access management.

I have SQL Server running in an on-premise environment, but we are testing it out on the cloud. We are trying out using APIs to access a database. SQL Server creates a lot of opportunities for us. While some of the larger companies have Oracle, SQL Server is more common in Peru. I'm responsible for administration and implementation, including configuration and data replication.

I use the client, however, I can also use the server, the Microsoft SQL Server Studio. I can use both, both the client and the studio. We connected Automation Anywhere to the DB. Our reporting tool is also connected to that DB. Our financial application is also connected to the DB and some other databases too as well as some of our APIs.

I am an integrator of this solution and my customers use this for ETL and reporting.

This application is used as a contact center and would be great for banks.

We are an independent software vendor and users of this product. I'm a company founder.

We are a solution provider and SQL Server is one of the products that we implement for our clients. People use SQL Server primarily for business intelligence. If you have Navision or Dynamics AX, and you need a data warehouse to be able to improve the performance of your business, then that is what our company does. For this review I will describe one of our clients. They are a large company that owns convenience stores, and they do several billion euros a year in business world wide. The convenience stores are located in large travel hubs like airports, train stations, office buildings, and large supermarkets. Everyone who flies/travels a lot has shopped in their stores. In Romania, they have 300 stores and sell between 300,000 and 500,000 items a day across the network. This customer is very mature and we have provided a lot of features. The most important is forecasting. When the store manager comes to the store in the morning they receive an order proposal dashboard from us. We will have taken the data from the close of business the night before, then built a forecast for the manager to help decide what to order the next day. This a very important application. We are able to calculate the orders across the network better than the ERP can. Another use case has to do with the actual items in convenience stores. They sell products such as cigarettes, drinks, sandwiches, magazines, and more. In Eastern Europe, there's still a high percentage of people that smoke cigarettes, and what you want to do, as a retailer, is negotiate your contracts with the large vendors. There are people called buyers, and they sign contracts with the major suppliers. Our use case provides a tablet with a very rich dashboard to show everything that is going on between the buyer and the vendors that they buy from. In those negotiations, especially when dealing with very larger vendors, you sell millions of euros of goods, such as cigarettes, each year. The goal is that you are trying to get the vendor to give you a lower price. At the same time, the vendor is trying to get you to pay a higher price. That's business. In that discussion, the person with the best data gets the best price. Naturally, it's a high-conflict discussion and you have to have a way of taking out the conflict and replacing it with a more logical, rational argument. The person with the best data wins the argument and gets the best price. That capability is worth a lot of money. Although only a dozen people use it, it's one of the top applications used by that customer.

We use it for the banking database. It is for banking software, accounting software, and human resource software that we develop to run our bank. In our production environment, we are using SQL Server 2014 Enterprise, but we also have an installation of SQL Server 2019 for our development environment.

SQL is our main data store for enterprise applications, all applications that we have in the organization.

We're using SQL Server for database work.

I use the SQL Server for backups and for creating databases and a lot of other stuff. I also use it to shrink data and some stuff like this.

We are using it for storing important data.

We have a few transitional systems in our large company that we maintain with Microsoft SQL Server.

We use the product as a database, a data tool for everything.

We are using it for various applications.

Our use case is creating data warehouses using the SQL Server database. The solution is deployed on-premises and on public and private clouds.

All of our .NET applications and some of our third-party applications require a single server database, AutoCAD, and things like that. Our custom apps are the largest estate of databases. In our production environments, we're on version 17. I've worked with the most recent version but not in a production environment.

We primarily use SQL Server for reporting.

We primarily use the solution as a backend server. There are a few applications of the Oracle product for our data sitting on the SQL Server as well.

We primarily use the solution to store databases.

While we were still using the solution, we employed version 2008, which is a bit on the old side. We basically used the solution for hosting the database for Sage ERP.

We primarily use SQL Server as a database management system. This solution is deployed on-prem.

We have a large amount of information and data. We are using a lot of business models for our menu mix.

We are business consults. We use SQL Server to ensure that critical applications remain operational by performing BCM activities across application and database servers.

SQL Server is used for storing data.

SQL Server can be used for managing and storing information. I have a lot of databases with more than one terabyte of information and we use technology, such as Stretch database to switch out the information to Azure databases with this type of technology.

This client, specifically, is using it for Dynamics NAV. I don't know what they're calling it today. Microsoft changes the names all the time, 365 NAV Dynamics. This is ridiculous. We're using it for that, and we have more of a niche CRM database called Tour de Force. It's owned by a company called White Cup. They own a bunch of companies, and it sits on Microsoft SQL, as well.

We're primarily using the solution for our health record system.

SQL Server is the database for the transactional database that is being used. The solution can be used for the BI, the data warehouse part as well, but mostly I have seen it used for the transaction data being stored by the DBMS part of it.

We use SQL Server to manage and store information.

I am a professional and I use this SQL Server in different companies. One of the companies I worked for was in the automotive industry. They had automobile products which they developed the SQL Server and database. At that time it was the first time I used SQL Server. I have also used Suprema which is a biometric system that also had an SQL Server. Our main products for data we have used SQL Server. However, my main application is developed on Oracle and MySQL, not any other database solution. All of our systems use this solution, it can control security, data management, and integration.

We manage backups for our customers, so we are not developers and we don't use SQL to provide a service. We are a managed service provider focused more on IT support and SQL configuration. So we don't use SQL as a product by ourselves. Instead, we provide instructions for how to back up SQL and do maintenance on it for our customers who need a SQL server for their CRM and ERP products. Their products need to have a SQL server to use in order to use their services. So we handle the maintenance for our customers.

We provide support services to clients. We find that some of our clients are running the latest system while others are still on Windows 2016, others are moving to 2019. Some other clients take time to upgrade. If I interact with five clients, I'll basically be in five different environments. Our use case for the SQL Server is for transaction processing. We store all the transactions that occur. For example, if you now purchase something from the point of sale, all the information about the good you are purchasing gets stored on the SQL Server. When you perform a transaction that information is stored at the bank that owns the point of sale and perhaps even your bank, where your money is will be stored in a SQL Server. All the people in all of the organizations, which are involved in the process use SQL Server. If your transaction goes through my server, I store part of the transaction there, and if I have to route that transaction to Visa or Mastercard, they have their own SQL Server, and they also store the transaction up until you get receive your goods at the particular merchant. Almost everyone in that transaction stores the information on their respective Microsoft SQL server.

We are consultants and users of this solution and we deploy both on cloud and on-prem. The primary use case of this solution is for its Health Check feature. I'm the company owner and CIO.

We use SQL Server as a database management system for all of our projects.

We use Microsoft SQL Server as our main database. We implement our solutions to the client site, providing the machines and the SQL Server license depending on their requirements. The SQL Server is being deployed on-prem. Most of our clients are from the pharmaceutical industry. If there is a physical database, they want a self-hosted server always on-premises. However, the market is slowly adapting to cloud servers. Scalability and security have increased, so now people are going with cloud servers like AWS, Azure, and Google Cloud. Most of our clients are hosted on-premises and they have their own server, so we don't go with any cloud server. However, we are planning to move ahead with cloud servers for many of our clients.

We use SQL Server as a database solution.

We are using SQL Server for our financial application package.

We use the latest version. Most SQL Server applications come with package applications from the shelf. This means that when one buys an application, most of these applications work with SQL Server as a basis. They add SQL Server as a database to applications which come with it that one buys. As such, I don't see many people developing new applications with SQL server.

It's a normal DMS, so it can be used everywhere you want to use any RDBMS or relational database. It's for normal transactions.

The main use of this solution is to control and manage data storage information.

We used SQL Server to store all of our lab data on the database. We had a front-end application that needed SQL in the background for archiving all the laboratory data.

SQL Server can be useful for a lot of businesses and enterprise solutions. SQL Server is very powerful and useful when you need to store, retrieve, process, and analyze a large amount of data. In my organization, almost everyone uses SQL Server. That's about 10 people using it.

We primarily use the product for internally developed applications. There's some business intelligence and data warehousing used as well as some financial information.

We use SQL Server as a relational database mostly for the application backend activities and integrations.

We set up SQL Servers for developers who develop applications for data mining. Our clients are generally small or medium-sized businesses. There's also a SQL Server Express that many software vendors use to support their applications. That gets installed often—usually as part of the application installation.

We do data warehousing, and our clients are mainly large commercial Insurance providers in the United States.

The solution is primarily used as a relational database. It's a great option for anyone who needs to still use a database.

We only use it as a logging solution. We use it as logging for processing our database. It holds records for some systems and so on. That's it.

We have hundreds of databases that are using SEL Server and there may be other capabilities.

We are using SQL Server for internal development projects.

We are using SQL Server to build and store our whole company's data in our data warehouse.

SQL Server is our main database solution. For example, we use it for our contact center software.

We use this solution as our database.

Despite the core database is not SQL Server in my working company, SQL Server is widely being used as the backend for many in-house applications and customized applications like Solarwinds.

We have used it in a variety of ways, including for e-commerce deployments.

We use the solution as a database for saving and managing data and applications.

We use the solution for managing our database functions.

We are using the latest version. We can use the solution for the same application. On the database side we have Microsoft SQL and on the operating system side we have 2019.

Usually, we use a lot of the vendor software, like ManageEngine, and stuff like that. They use Postgres, however, I prefer to use Microsoft's SQL server. We have a couple of servers and we integrate that information into it. I can run reporting and analysis off of that.

We use a tool called Tosca for automation and all the automation artifacts we are saving are on the SQL Server.

We primarily use the solution mainly for databases on all types of applications.

We use SQL Server for database management.

We use SQL Server for web application and website development.

The solution is an RDBMS and can be used to simplify customers' requirements for a back-end database. The main function of the solution is to store information from front-end users.

This solution is part of the ERP that we have for application. We use it for many purposes, such as POS in-store cash registers for enterprise companies.

We use this solution to manage our database and store information. I use another platform for more specific needs. Within our organization, there are roughly 10-12 employees using this solution.

Our primary use case is for SQL Server is data warehousing and business intelligence.

We are using SQL Server for the backend of our SAP and are planning on moving to a cloud version soon.

I have been working on SQL Server for installations, configuring for developers, and for creating backup jobs from the MBF files.

The solution is a part of a product. We use it for our database, among other items.

We use SQL Server for collecting and storing our data.

We are a company that possesses data relating to the banking and telecommunications sectors. We use the solution to organize all data received from subscribers and customers.

We primarily use the solution for our banking database.

The solution is used for database management.

SQL Server is enterprise database software. It provides the back end for any number of different applications, including web applications, and other types of internal applications, and software-based applications. It also provides a back end for enterprise backup tools. It's incredibly diverse in terms of its use case.

The solution can be used for a host of applications.

We're using it for our on-premise servers, and we have the latest version of SQL Server. We use SQL Server for the database for Microsoft Navision. We also use it for the Track-It application that helps users in logging in their IT requests. We also manage all the IT inventory through Track-It. It does automatic auditing and traces online IT equipment.

We are using it for accounts payable and accounts receivable automation. We make accounts payable and accounts receivable solutions, and we're using SQL Server as one of the building blocks.

We develop software for another company. We mainly develop on-premises solutions. We use this solution with our accounting ERP software. Our product is called Orchida ERP and we have many clients in Egypt who are using this software. Its database is SQL Server. We mainly work in ERP. We currently have a small project in SharePoint for Microsoft, but 80% of our work is with Orchida ERP We have our software with SQL server for 20 years. Our software will not work without SQL Server. We provide consultancy in installing this solution for our clients.

Microsoft SQL Server is a database application, meaning it acts as the backend system for help with the backend data repository system. It concerns itself with every activity that happens at the front end of the database in Microsoft SQL Server. ERP Microsoft solutions is one reason that the SQL server has compatibility. The management of Microsoft SQL Server is actually quite easy. It has a GUI interface and enables a person to do whatever is required at the command line level. It functions as a repository for storing one's data in the relational database.

We use the solution for nearly all of the services we provide that utilize Windows Server. We use it to provide continuous service and in respects of our mail server.

I primarily use the solution for the development of various applications, database connections, that I need for projects. I just use it myself, for assignments. I am a student and am studying the product.

We use SQL Server with Sage products. It is used by our finance team and also human resources.

It is used for many things. We primarily use it for our two-tier and three-tier applications.

We use the product for information systems. This is a must both for us. We use it for our Enterprise Portal.

Our primary use case is for data mart and data warehousing. My company is a service company and we provide the professional services for deployment of BI solutions. We are customers of SQL Server and I'm head of data analytics.

I primarily use it to extract some configuration information for my product - in order to understand how the configuration is done for my base product.

It is used for everything under the sun. We're currently using it for a health pass for a medic aid information management system. It is also used by companies in banking and retail. We are using SQL Server 2014 on Windows Server 2012 platform, and we also have SQL Server 2016 on Windows Server 2016 platform. I have primarily worked on the hardware, but I am now also working in the Amazon AWS cloud.

I use this solution as our data warehouse. We use the reports, data analysis, and for connecting our databases to multiple resources.

We use it for both database services and analysis services.

We are a product-based company, and we use it as part of our product. It is deployed in a public cloud and on-premises.

We primarily use the solution for data storage. We use it for its data warehouse, BI services, and AI.

I use the solution for analytics and reporting.

Typically, the SQL Server is used in many, many ways. We primarily use SQL Server when there is a data requirement for our projects. Typically there are uses around where you are creating a database. I've yet to store the data in our RPA server. We need MS Excel through Microsoft. Any sort of RPA process where you require data through housing data or using a database, you need an SQL Server.

It's a database that we use for our commercial applications, and our ERP sits on it.

There are many applications between Microsoft and SQL. Most are in the legacy direction, but some are more modern databases with those application requirements. We have used it for multi-purposes such as back-office products applications and cloud office environments.

We are a solution provider and this is one of the products that we implement for our clients. It can be used for different things such as data warehousing and online transactional processing (OLTP). This is a product that I have never used in production, however.

SQL Server is used as database software. People who are using .NET and Windows-oriented tools prefer SQL Server.

I am an IT professional, I write services for my clients. I provide support services for SQL, firewalls, and operating systems. IT infrastructure support in general is what I provide.

I use SQL Server for .NET. We have ERP software in the background and we use the SQL Server for its creation.

We use the solution for managing database information from our clients and for testing database access.

The solution is primarily used for studying data and statistics. We have some services that we are monitoring and keeping records and doing reports, and we use it for that.

We use this solution for data warehousing and products to the platforms developed by the company.

It is used for the backend database for our ERP system and the document management system. We are using its latest version.

We primarily use the solution for recording transactions and information related to the reservation of a service.

We use this solution to analyze the profitability of sales. Within our organization, there are roughly 30 people using the analysis services solution from the Business Intelligence side.

We are using this solution as a database. The main purpose is as an SQL Server.

We developed a product that is using five or six databases supported on SQL Server.

We use SQL Server to import data from different source systems. Depending on requirements, you act as the resource and can schedule jobs in the Azure environment. The server can be stopped when not required so there's no cost when it's not being used. We make use of the pipeline to put the data into the SQL Azure environment and extract it to the server. I'm the associate manager.

My background is primarily in software development, and I use SQL Server among other tools in that capacity. SQL Server was one of the main databases in my previous company, and it is used for storing data from different applications.

We are primarily using the solution for pulling data and analysis. In the auto industry, are the dealer management systems for which there is kind of portals from which the dealers are maintaining information can have access to retail data, bookings, and details surrounding individual customers. We are fetching data and using it for analytics purposes, basically.

We use SQL Server to process a lot of data. We are using versions and 2015 and 2018.

We use SQL Server for database integration as we sometimes use queries to take information from the database. For example, if I need a couple of information that is archived or not indexed, I will inform the SQL Server team to help.

We use SQL Server for our internal applications.

We primarily use the solution as a relational database system.

We use this Relational Database Management System for Line of Business systems, including Enterprise Resource Planning, Data Warehouse, Web Applications, and Business Intelligence. Solutions are procured, built, and enhanced in the REIT industry, FMCG ERP, distribution and warehousing, manufacturing systems, knowledge workers such as workflow and portals, web applications, custom developments areas, enterprise reporting and analytics for internal reporting, and decision support systems. Integration solutions provide robust integration to various and disparate third-party systems.

We use SQL Server for our application data. As a government agency, all of our data is stored in our environment on-premises.

We use SQL Server to store, retrieve, and manage data.

Our server projects are mostly related to SQL Server, and we're using it. All our healthcare projects are using the SQL Server, and we're able to load millions of data without any issues.

The solution is our main database and stores our data at the organization. We're a Microsoft shop. That's why it's the main database. We have licenses for the servers. The only reason I'm using that is that that's what we have. However, I don't actually like working with it.

We primarily use the solution for non-management processes.

We primarily use the solution as a database for business operations.

The .NET applications use SQL Servers on a very large scale. Basically, about 80% or 90% of the database platform is on SQL Server. We are working on version 2019, but we are also now working on the cloud databases. Our goal is to stay away from versions. We are going to go version-less and move to Azure SQL or managed instance, which is version-less. This way we won't need to worry about any upgrades or any version changes because Microsoft is going to take care of these things. We will always have the latest and greatest version.

I handle the banking software. We have another software called City Life, a life insurance package. We develop those packages - the banking package and the life insurance package. We have almost 70 - 80% of the market share in our country. I also use and love Delphi. We develop in that language. The backend is SQL Server at this moment and we are researching how we can move from SQL Server to some other open source solutions.

We are a company that produces stock market analytics data and we are working on creating an alerting system for our customers. We use Microsoft SQL Server in our development and I have a lot of experience with it. In my development role, I store about two gigabytes of data every month.

We use the solution for many tasks. We use it as a data warehouse. However, we also use it for workflows and processing jobs.

Currently, I'm moving to another set of projects. One is for a small company that supports a client and is building on a different surface on the SQL server. The cloud that is used is essentially Amazon AWS.

We have a few use cases. They range from temporary storage to long-term storage to backup systems. We're using the full versatile suite for the product currently. It's not just a stand-alone system.

We are using this solution for application databases and data warehouses.

We primarily use the solution as a WAP server and we have it on-premises.

We are using this solution for business websites.

The primary use is to maintain my database client.

We use it mostly for integration into an ERP system. We also use it for our internal development of products.

We are a software development company. Most of our developers use SQL Server. We plan to continue using this solution in the future. We use SQL Server for relational database management. We have a variety of customers who use it in the government sector and in the tourism sector.

We are using SQL server for both transactional and analytical purposes, and for storing the data.

ERP Database. Using the SQL queries, the user can quickly and efficiently retrieve a large number of records from a database. In standard SQL, it is very easy to manage the database system. It doesn't require a substantial amount of code to manage the database system. Long established are used by the SQL databases that are being used by ISO and ANSI. Using the SQL language, the users can make different views of the database structure.SQL has a difficult interface that makes few users uncomfortable while dealing with the database.

We use on-premises, standalone deployment of SQL Server for our own CRM database. There are around seven to eight users in our company.

In my role as faculty, I would use it to facilitate having a database with all the teachers needed that are equivalent to Oracle as a database for a small scale project.

Our primary use case for this product is as a transaction database and for the provision of rational data through the application-based server. The main application of my current organization is pointing towards the SQL server database and some servers which are later used for data warehousing. So mainly we use it for transaction data and data warehousing. I'm the assistant manager and data administrator, and we are customers of SQL.

We are currently developing our own business application and we are using SQL Server as the database. We deploy it as a .NET application and the webserver is IIS. The SQL is a three-node clustered system.

We use SQL Server to ingest and to extract reports for multiple customers.

We primarily use the solution for our daily operations.

My primary use case is for data mining and processing data from plants. It's normally just for databases for the systems.

We have a Windows Server environment. This is a production system for secure document issuing in a government department.

Our correlation and relational databases are on Microsoft SQL Server. The company uses two platforms: MySQL and Microsoft SQL Server. Some applications are on MySQL, and some applications are SQL Server. I have pretty much worked all my life in Microsoft SQL Server.

Very pleasing and satisfying experience. * Used to create queries * Implemented store procedures * DBA can also use this effectively.

The customer's MES system use it. The database system desgin as always on architecture. Like Data guard in Oracle , always on contain double data and sync data by using transactions store in transaction log

* Effectiveness in a production environment * New features test

This is a departmental database engine which supports primarily localized solutions, data capture, and retrieval. However, with the exception of our aviation group, it is used for localized data lake or reporting solutions support.

I use SQL Server to optimize SQL queries and find the estimated cost of my queries. I also use it to fine tune my procedures and functions.

The database is primarily used as back-end storage.