Microsoft SQL Server Reviews and Ratings

Use Cases and Deployment Scope

We use it to hold the databases that with use for our Apps. It gives us a efficient way to store all the data we have in order to make our apps works. Any business needs a database to store it's data and with Microsoft SQL things are easier to manage.

Likelihood to Recommend

With Microsoft SQL you will have a easier and faster deployment and work. It's true that you have other open sources options , like mysql for example but the learning curve and support it's harder. It's pricey but it's worth it. If you are a small organization you could try to use SQL Express but the database size is limited , in that scenario you might want to go with a open source option.

Use Cases and Deployment Scope

Microsoft SQL Server is being used for the various applications in our organization, which are OLTP, Data warehouse, and Java-based applications. The various tools that come up with Microsoft SQL Server like SQL Server Management Studio, SQL Server Profiler etc make the maintenance and performance analysis very easy. We also have integrated it with Power BI for the analysis purposes.

Likelihood to Recommend

In our organisation, scalability is of frequent use. With Microsoft SQL Server, we are able to scale up and down the servers based on the demand. We are also using it in our Data warehouse applications and the performance has been far better as compared to other databases. Since we are using other Microsoft products as well, Microsoft SQL Server provides a good ecosystem with those products.

Use Cases and Deployment Scope

Microsoft SQL Server is used in our organization by IT personnel to Store data, fetch data specific to requirements. For instance, in Sales Module SQL server is used to fetch data specific to a sales transaction and it helps to troubleshoot the errors reported by users. Similarly, it is used by IT technical team and other IT functional team to query the data stored in data server.

Likelihood to Recommend

1) We had a set-up where the ERP application and the servers were in-house and Microsoft SQL Server is perfect to query the data and troubleshoot the error reported by user. 2) The Microsoft SQL Server is taught to students from high school and this is like a baseline for students from IT. So it makes it easy to use at organization level since individual had already gained lot of experience in querying in previous projects at college level or otherwise. 3) In case of Cloud architecture, there is stiff competition and every software enterprise need to re-version itself for betterment. Otherwise, its- no less than any product out there.

Use Cases and Deployment Scope

Microsoft SQL Server supports the databases for our primary accounting system (MS Dynamics GP). This avoids us using much less efficient flat files or less compliant software from, for example, open source solutions.

Likelihood to Recommend

Support for any data set that has relational or repetitive data is a good place for Microsoft SQL Server. It scales well and has the instructions to do almost anything you need it to do. It is also extremely scriptable.

Use Cases and Deployment Scope

I work for a company that creates a software suite that allows our customers to manage and track their work, their companies and contacts, user logins, etc. We use an extensive database built over the years and several stored procedures that can be called from our software to perform calculations and format data in needed layouts.

Likelihood to Recommend

Microsoft SQL is ubiquitous, while MySQL runs under the hood all over the place. Microsoft SQL is the platform taught in colleges and certification courses and is the one most likely to be used by businesses because it is backed by Microsoft. Its interface is friendly (well, as pleasant as SQL can be) and has been used by so many for so long that resources are freely available if you encounter any issues.

Use Cases and Deployment Scope

I primarily use Microsoft SQL Server 2019 and 2022 data engine to run commercial workloads of various customers. A frequent configuration use case is the usage of Microsoft SQL Server Always On failover cluster instances to provide high availability and redundancy at the Microsoft SQL Server instance level. In some cases, I also make use of Microsoft SQL Server replication to ensure that a primary (publisher) database is replicated, by using transaction of snapshot replication, to a subscriber SQL instance from which the customer can run various SQL queries for analytical reporting purposes without affecting the SQL production workloads. Another common case where I make use of Microsoft SQL Server is when running hybrid cloud SQL workloads, in which case I combine on-premise SQL Server deployments, Azure VM-based SQL Server deployments and Azure SQL or Azure SQL Managed Instance resources.

Likelihood to Recommend

Microsoft SQL Server is ideal for highly available SQL workloads by using SQL Server Always On availability groups. Microsoft SQL Server might not be appropriate for solutions which require a very low resource footprint, since it requires significant CPU cores and RAM memory as well as high IOPS, always depending on the usage scenario.

Use Cases and Deployment Scope

We use MSSQL Server along with SSIS and SSRS as it's a very competent software suite and very stable. It integrates well with other software that we use, namely JAMS Scheduler.

Likelihood to Recommend

MSSQL Server is excellent for most organizations that have database needs. Typically businesses will be either a "Microsoft" or "Oracle" shop and it tends to boil down to the software used, as many require SQL Server to begin with. In my experience mostly small to medium sized business use MSSQL Server. For ETL, I find SQL Server the way to go as SSIS is better than Informatica, but that's my opinion.

Use Cases and Deployment Scope

I am a computer engineer. I have been working as a software developer for about 7 years. I've been using Microsoft SQL Server since I was a student. The interface is very simple and useful, even beginners can use it comfortably. The dark theme has no shortcomings except that it is added under options. Table, schema, and index adding operations can be handled with a single line.

Likelihood to Recommend

I'm making bank software and I can use Microsoft SQL Server for all scenarios. Customer

data, account data, card data, credit data all information is kept

in the Microsoft SQL Server database. It provides convenience while keeping related data.

While reporting, slowness may occur because there is too much data. We

use Oracle as an equivalent.

Use Cases and Deployment Scope

We use SQL server as a back-end for the vast majority of our software applications. This includes backends for web apps, data staging and SSIS/SSRS. As far as DB's go, SQL server is our first choice because it integrates easily with our Microsoft .net and .net core applications. Our SQL DB's are used across the entire organization.

Likelihood to Recommend

If your organization builds a lot of Microsoft based applications using .net or .net core, then the use of SQL is a no-brainer. The integration with .net is second to none as a backend for web apps and APIs.

In general, SQL performs well for a multitude of tasks beyond web app backends. We use SQL for high volume transactions for our core ESB which has very high data volume and data churn.

Use Cases and Deployment Scope

We currently use Microsoft SQL Server as our database application for our applications. We are using the Microsoft SQL Server jobs, Analysis services, cubes, and many other features to help provide front end data solutions to our customers. Our instance of Microsoft SQL Server also allows for multi-database implementation with full backup capabilities. We also pair with the latest management studio to get the best UI experience.

Likelihood to Recommend

Microsoft SQL Server is best for enterprise-level databases for data management. If you need to scale easily there are other options like Azure SQL, etc, but this also works best on bare metals servers. The licensing can get a bit complicated so it is not good for small companies/applications. I also don't think it is the best for mobile applications, etc.