Microsoft SQL Server

Microsoft SQL Server is used in our organization to store data, run analyses, and produce reports using data from our web-based application. It is mostly being used in the data analytics department and it allows the team to work on projects together and integrate with other software used in the organization.

SQL Server is used company-wide: All of our business data is stored in SQL databases and all of our applications utilize SQL in some capacity.

We use Microsoft SQL Server to store various databases that are used within both the whole company and also within certain departments. Data from these databases have front-end interfaces for easy editing by certain users and data also feeds into other systems and is merged with other data sources. It allows us to have a common silo for storing our data that helps developers and admin staff easily access the data for further use.

Microsoft SQL Server is being used across the company in mostly all IT and technical / data departments. Microsoft SQL Server allows us to pull data from different tables, manipulate it however we need, and use it elsewhere in the company. For example, I use Microsoft SQL Server to pull data from a different application and use it to make updates in Salesforce.

Our company uses MS SQL Server to run jobs, store data and generates reports. Our team is supporting two separate companies and both use MS SQL Server. One is for storing data and running SSIS jobs for app and reporting purposes. These are company-owned servers and we are hosting other companies to provide service, application and hardware support for them.
Our company maintains these servers and they are being used by different departments, also internal company-wide. Business problems that we commonly encountered are mostly connection issues. These are basically a between network, database and applications connecting to MS SQL Server. The MS SQL Server support is easy to get in touch with when we are having issues with the application itself.

My department uses SQL Server (and Azure Data Studio, increasingly, but still primarily SQL Server) for database management and analysis. Other departments use it as well, including our QA team, to verify the expected output of data manipulation or the functionality of changes to the code base. It's a pretty standard tool at this point.

I consult for system and data integration projects. Many of my customers use SQL as their data management and storage system. During integration projects, I will also use SQL to store information that I need later in the integration process or for reporting purposes or auditing.

SQL Server is our go-to database for both on-prem and cloud database needs. We are running on-prem for 3rd party, custom applications, and the enterprise data warehouse. The Cloud is great for custom applications, as well as beginning to migrate to a data lake structure with Azure SQL DW. Other than embedded databases in a few apps, it is the only RDBMS technology we leverage, although we do run several different versions and editions (Azure SQL DB, Azure SQL DW, SQL Server 2016, 2017).

I use Microsoft SQL Server to write SQL queries for my healthcare organization to do reporting for national quality metrics. It allows me to write efficient, fast queries that export nicely to Excel.

In our database department, we use Microsoft SQL Server for storing data, data aggregation, and manipulation. We use Reporting services tools for creating, managing and deploying reports for our clients. For creating a report definition I personally used Report Builder which makes defining data source connections, queries used to retrieve data, expressions, parameters and others extremely easy to perform. We also try to improve the performance of stored procedures, user-defined functions, and triggers by learning the execution plan in detail. One of our clients has a web app for an insurance company and they have a large amount of data stored in the Microsoft SQL Server database. Our goal is to improve performance from queries that are used in that web app, so we try controlling execution plans with hints or adding indexes. In cases when we meet a new client who already has some database storage then we use replication technology for copying and distributing data and objects from one database to another. Besides that, we also help our clients to build parameterized queries in order to defend from SQL injection which is one of the most common web hacking techniques.

We are using Microsoft SQL Server to store the data of many commercial and internal software applications: SAP Business One, our Point of Sale system installed in more than 60 branches around the country, several web and desktop applications, and our data warehouse used across the company. That represents thousands of transactions per day.

We currently use SQL Server in Azure which makes management easier, though I have used on-premises SQL Server for many years, many versions. I am Microsoft certified in SQL Server 2012 and 2014. As a software developer I like the way SQL Server is easy to program against -- especially when using Entity framework or Entity Framework Core as the middle ware. As a database administrator I like the fact that SQL Server is truly relational, which makes it much easier to model business objects as data tables and to manage Referential integrity, locking and consistency. I like its ability to help with performance scaling via pre-compiled queries, stored procedures and triggers. I like its ability to help with scaling via sharing and replication. But above all I love SSMS (SQL Server Management System) which brings together all the tools in one place with easy access to query plan tools and analysis tools as well as SSIS / SSRS allowing integration of data with other systems and generation of reports.
It has matured over the years into a tool that makes life easy for those architecting or writing systems.

We are a Business Intelligence shop utilizing the entire Microsoft Data Stack. We use SQL Server versions 2012, 2014, 2017. We are also currently evaluating 2019. Our entire organization also uses SQL Server. In our department, it is used to ETL data in (via SSIS), store it into a Kimball Data Warehouse, do reporting off of it via SSRS, and then provide self serve analytics to our business users via SSAS. The best thing is that SSIS, SSRS, and SSAS are all included with SQL Server!

Microsoft SQL Server is the base of all of our in-house servers. We use it to access all of our internal and external data that comes from Verint and other places. It solves our need to store the data that we have in one location and to create a data warehouse on top of it.

IT uses it to design queries within our ERP platform, as requested by various stakeholders throughout operations. There are over 100 separate queries that are used daily. I use it for various accounting reports, as I find it provides more of an exact "what I'm looking for" than the canned reporting available through the ERP.

Microsoft SQL Server primarily serves as the back end of our core business system, which is built on Microsoft Dynamics NAV on the front end. Essentially everything our business does goes through this system, making access to the data crucial. While SQL Server is a required component of NAV, the system still needs to perform and be reliable all of the time. Luckily SQL Server is widely supported and time tested, allowing us to choose it with confidence.

Microsoft SQL Server is being used by the whole organization. Our core OLTP database system is on the MS SQL Server.

Microsoft SQL server is the official database management system for Microsoft, and it is a very reliable tool. Our team has a platform for analyzing city infrastructure which has multiple instances and a DBMS is crucial for managing all of the data. We use Microsoft SQL Server to check queries before publishing them to the live website. The tool is dependable and fairly straightforward to use, even for someone inexperienced with database management.

In my company we use it project/account wise, Our main purpose to use it is because it has a very easy user interface and lots of internet communities for providing the solution.

I use Microsoft SQL Server primarily as the back end database server to ASP.Net C# websites. For authentication and authorization, the database uses tables and stored procedures to implement membership or identity for user login and defining roles. Of course, the database is used to hold data entities for the needs of the website. Use of stored procedures, views, and sequences full-text indexing are just some of the useful features I take advantage of.

Microsoft SQL Server is being used as the default database management solution. It is used across the whole organization and is responsible for managing different types of databases such as ERP, Spatial and regular ones. SQL server caters to regular reports generation, establish relational queries between different datasets, provide backup in case of any issues.

Microsoft SQL Server is our primary data storage for our in house software as well as 3rd party financial software and provides the data for all of our enterprise reporting. We also leverage the additional services that come with Microsoft SQL Server including SQL Server Reporting Services and SQL Server Integration Services.

It is used as a data warehousing and business intelligence platform across the whole organization.

We have used SQL Server for years, and it has been our main database for desktop projects. It also has been the database engine to choose when developing financial applications for its speed and security. We also use it when working with complex data and a variety of fields.

We currently use Microsoft SQL Server, integrated with Automation Anywhere, to develop automation scripts. We opted for SQL Server for its Microsoft support and native Automation Anywhere functions that allow us to work with this Database.