The solution is used primarily for medium companies in vertical accounting applications. We use the solution as a good general-purpose database.
Consultant at a tech company with self employed
Works well as a general-purpose database, but it needs to improve documentation for specialist applications
Pros and Cons
- "I value the ability it gives me to test on small machines and easily scale up to larger devices for live applications."
- "When we run into problems, it's usually during installation, and finding answers to the problem has been a nightmare because the documentation is terrible."
What is our primary use case?
What is most valuable?
I value the ability it gives me to test on small machines and easily scale up to larger devices for live applications.
What needs improvement?
When we run into problems, it's usually during installation, and finding answers to the problem has been a nightmare because the documentation is terrible.
Likewise, I find the business reporting rather poor, and the solution doesn't work well as a data warehouse product. When I tried to use it as one, I did not find it very satisfactory.
For how long have I used the solution?
I've used SQL Server for about 20 years, probably. I've used a number of different versions, including 2010 and 2007.
Buyer's Guide
SQL Server
March 2025

Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
845,040 professionals have used our research since 2012.
What do I think about the stability of the solution?
We have never had a stability problem.
What do I think about the scalability of the solution?
We rarely have more than a few hundred users. It's more about the person using it since we don't have heavy, continuous use.
How are customer service and support?
We've never had a sensible answer from technical support.
How was the initial setup?
I have generally found implementing the solution easy. But when it comes to the time we took to implement the solution, the problem's always been the application and not the database. The solution is usually easy to implement because we use standard facilities. If you need something special, you run into all sorts of trouble because SQL Server gives you an awful lot of ability to change the settings.
What's my experience with pricing, setup cost, and licensing?
We've used it as a development tool, and it's very cheap as a development tool. Besides, someone else has paid for it for my use, so it's a question of whether the cost suits the end user. The solution has a good midrange price for the applications in which we've used it. Oracle's pricing would raise more eyebrows, but SQL Server's pricing has proven satisfactory for our market range.
Which other solutions did I evaluate?
We mainly use SQL Server because it's cost-effective for our applications. We've occasionally tried other databases for various reasons. We've used the Sybase database, but the Sybase database is very close to SQL Server. We've also tried MySQL, but that was more of an exercise in porting than anything else. However, it's not a fair comparison because we had done the development on SQL Server and then used that as a porting exercise.
What other advice do I have?
The solution's generally been easy to use for the general cases we've used. The solution has been satisfactory for the sort of applications we've used.
We've been very much middle of the road in using SQL Server. We don't use specialist, and we've tried to keep to standard SQL as far as possible. We don't use the clustering facilities or try to use any of the specialist facilities. We could drop it and switch to MySQL or another database if we had to. We are using SQL Server, not for the particular services it's got, but using it as a middle-range product. We're taking advantage of the fact that it runs on all sorts of platforms, and it's a good value development product that works very easily for us. We're not using it for some of the things Microsoft clients find particularly useful for. We're not high-intensity users. For people like us, it fits in very easily.
For our purposes, SQL Server is just about ideal. It's easy to use and fit. Some of the later versions, in particular, have been easy to use. We have had installation problems on some of the later versions, and the documentation is poor. I'll rate SQL Server a seven out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.

General Manager IT at a manufacturing company with 10,001+ employees
User-friendly database with excellent backup features
Pros and Cons
- "The backup capabilities are extremely good."
- "I would like to have the ability to restore backups in the next release."
What is our primary use case?
This application is used as a contact center and would be great for banks.
What is most valuable?
The backup capabilities are extremely good.
What needs improvement?
I would like to have the ability to restore backups in the next release.
For how long have I used the solution?
I have been working with SQL server for the past ten years.
What do I think about the stability of the solution?
This solution is very stable from what we have seen.
What do I think about the scalability of the solution?
This is a scalable solution.
How are customer service and support?
Technical support is very good. I am able to easily contact them and they are very informative.
How was the initial setup?
The initial setup was straightforward.
What other advice do I have?
This is a great solution for anyone with basic knowledge of DNS who wants to build up a database. There are many videos to help you navigate the platform.
I would rate this solution a nine out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Implementer
Buyer's Guide
SQL Server
March 2025

Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
845,040 professionals have used our research since 2012.
Sr. Network Administrator at ACMC
Stable and easy to use
Pros and Cons
- "One of the most valuable features of SQL Server is that it's easy to use."
- "SQL Server could be improved with cheaper licensing because it's very expensive."
What is our primary use case?
We primarily use SQL Server as a database management system.
This solution is deployed on-prem.
What is most valuable?
One of the most valuable features of SQL Server is that it's easy to use.
What needs improvement?
SQL Server could be improved with cheaper licensing because it's very expensive.
For how long have I used the solution?
We have been using SQL Server since 2016, so more than five years.
What do I think about the stability of the solution?
This solution is stable.
Which solution did I use previously and why did I switch?
Before implementing SQL Server, we used Oracle. We switched to SQL Server because it had good integration.
How was the initial setup?
The installation is straightforward. I was able to handle deployment and maintenance by myself.
What about the implementation team?
We implemented this solution through an in-house team.
What's my experience with pricing, setup cost, and licensing?
For licensing, we pay yearly. The licensing is very expensive, and it should be cheaper.
What other advice do I have?
I rate SQL Server an eight out of ten. I would recommend it to others, as long is it meets their requirements.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
BI Developer at a manufacturing company with 1,001-5,000 employees
A stable and scalable relational database management system
Pros and Cons
- "The performance is great."
- "It's difficult to make changes. It's a very complicated product in general — that's the issue."
What is our primary use case?
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.
What is most valuable?
The performance can be great. Tuning and understanding SSAS is not straightforward.
What needs improvement?
The issue is that Microsoft is not really supporting the Multi Dimensional Analysis Services feature any longer and it's looking very obsolete. We're looking at replacing it.
SSAS-MD is difficult to make changes. It's a very complicated product in general — that's the issue. It is too complicated for most. It's too difficult to change. It's too difficult!
For how long have I used the solution?
I have been using this product for more than 10 years.
What do I think about the stability of the solution?
This particular product is quite stable. We've not had any particular problems. We've had problems with Microsoft Excel recently, but Analysis Services has been quite stable.
What do I think about the scalability of the solution?
Scalability-wise, it's quite good. It's not scalable up to the big data type of thing that people are doing now. It's scalable up to a point, but it has been overtaken by newer products.
How are customer service and technical support?
We try and avoid calling Microsoft support, generally. That's the truth. We've tried getting support for other products like Power BI — support is an issue.
They're changing their products and they're not stable enough. Analysis Services has been okay, but some of their other products, like Excel and Power BI, are not stable.
What's my experience with pricing, setup cost, and licensing?
We're looking at alternative solutions because we think Microsoft's licensing costs have been expensive and multidimensional cubes have been overtaken by other technologies such as in-memory databases and products like Snowflake.
We're looking for a solution that allows us to pay by usage rather than pay by the number of users. We don't want to pay for hardware capacity that we rarely use. I'm looking at several products, including Snowflake, that bill by how much we use the product. I'm not sure if Microsoft is on board with that yet. I was also looking at Qlik — they do a commercial model that is paid by the amount of time. I think paying per usage is a rising trend at the moment.
What other advice do I have?
Overall, on a scale from one to ten, I would give SQL Server a rating of nine. It's generally a good product.
If you're interested in using this solution, my advice is to do your research. It's a good product, but there are other products available.
One of the biggest issues that I have with Microsoft is that they change their products and don't continue to support the old product. We've got some things in Microsoft Excel that are no longer supported. They bring out a new model and they drop support for some of the older features.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Head of IT, CTO at a insurance company with 51-200 employees
Reliable, scalable, and user-friendly but the pricing could always be better
Pros and Cons
- "It's much more friendly in comparison with Oracle."
- "I am fine with the pricing, but pricing is an area that can always be improved."
What is our primary use case?
We are using this solution as a database. The main purpose is as an SQL Server.
How has it helped my organization?
Our backend and core systems are using Microsoft SQL Server. We have no complaints from anyone who is using it.
We have nothing that we can compare it with.
What is most valuable?
It's much more friendly in comparison with Oracle.
We are using the standard features. I don't see any areas that can be simplified with the standard functionalities. We don't use any special extended features.
From my point of view, using SQL Server 2017 and 2019 is very good. I haven't experienced any issues or been in a situation where I was struggling with problems for which I didn't have access to proper documentation or proper functions.
For how long have I used the solution?
I have been using SQL Server for eight years.
What do I think about the stability of the solution?
After eight years in our company, we have not had any issues with SQL Server from a stability point of view.
What do I think about the scalability of the solution?
We are a small company. We don't have any issues with this and we are fully virtualized. If we need to, we can extend the amount of CPUs as we want.
Our core system is being used by 50 users, but they are not accessing the SQL Server. We have approximately 10 users in our company who are using the SQL Server.
How are customer service and technical support?
I have never used technical support.
Which solution did I use previously and why did I switch?
I am using Avamar and Data Domain. I have been using Data Domain for four or five years. It was used as the data storage for the backup solution in our sister company.
I worked with Oracle in the previous company. Microsoft SQL Server is better.
We have also used Software Center, Active Directory, Microsoft Exchange, and almost everything that is Microsoft-based.
How was the initial setup?
It was installed by an outsourcing company. It is another sister company.
What's my experience with pricing, setup cost, and licensing?
It's cheaper than Oracle.
I am fine with the pricing, but pricing is an area that can always be improved.
We are Microsoft D-level partners. Pricing is not an issue for us, because of the outreach of our mother company.
What other advice do I have?
We are a Microsoft-based company.
I would rate SQL Server a seven out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Lead Data Architect at a financial services firm with 1,001-5,000 employees
Easy to use and integrates well with other Microsoft products, but the performance needs improvement, and there are many hidden costs at the enterprise level
Pros and Cons
- "The most valuable features are ease of use and the integration with Single Sign On (SSO), as well as with other Microsoft products."
- "The performance needs some improvement and it needs more features integrated into it."
What is our primary use case?
We are using SQL server for both transactional and analytical purposes, and for storing the data.
How has it helped my organization?
We are familiar with Microsoft products and bringing another Microsoft product was a very easy transition.
What is most valuable?
The most valuable features are ease of use and the integration with Single Sign On (SSO), as well as with other Microsoft products.
What needs improvement?
The performance needs some improvement and it needs more features integrated into it.
Technical support could be better.
Scalability could be less costly.
One of the conflicts with Microsoft is if you have an enterprise relationship, you have to deal with a third-party offering Microsoft solutions.
In the 2016 version, they don't have support for Python. It may be included with the 2019 version but if they don't, I would like to see support for Python implemented.
For how long have I used the solution?
The company has been using this solution for approximately 20 years. I was in contracting and now have been using it for approximately five years.
What do I think about the stability of the solution?
SQL Server is pretty stable.
What do I think about the scalability of the solution?
There is a concern with the scalability because it's an on-premise technology.
Scaling always comes with more costs and also the licensing cost increase, which makes it complex, and more difficult.
We have backend developers, data engineers, data scientists, and analysts using this solution.
How are customer service and technical support?
Most of the time, technical support is not straightforward and it goes to a third party.
I wouldn't say that it is great, but okay.
Which solution did I use previously and why did I switch?
Previously, we had not used any other solutions. We have been a Microsoft shop from the beginning.
How was the initial setup?
The initial setup was not easy but not complex. Rather, it was somewhere in between.
What about the implementation team?
We did not use an integrator or reseller to deploy this solution.
What's my experience with pricing, setup cost, and licensing?
Pricing is reasonable for small organizations, but the scaling increases the price.
For larger organizations that would be using enterprise solutions, it contains some hidden costs.
What other advice do I have?
It's suited for small organizations, but if someone from a larger organization is looking for this, they might have some problems implementing enterprise-wide solutions. This is because of the integrations, as there would be hidden costs to it.
The best parts of this solution are the costs and that it is easy to use, but the cons would be with implementing an enterprise-wide solution. There are many hidden factors, such as costs. Also, you have to put more effort into integrating with other solutions across the enterprise.
I would rate this solution a six out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Information Technology Security Officer at South African National Accreditation System (sanas)
Beneficial support system, highly scalable and reliable
Pros and Cons
- "SQL Server is very scalable because we use it across a couple of different types of applications, such as micro-infrastructure setup and server farm."
- "SQL Server could improve by being more user-friendly, it is still geared towards specialists. Additionally, the monitoring system is difficult to use, not everyone can use it well. The configuration should be able to be done through the GUI."
What is our primary use case?
All our databases are using Microsoft SQL. It supports our application, such as HR and finance.
What needs improvement?
SQL Server could improve by being more user-friendly, it is still geared towards specialists. Additionally, the monitoring system is difficult to use, not everyone can use it well. The configuration should be able to be done through the GUI.
For how long have I used the solution?
I have been using SQL Server for approximately 10 years.
What do I think about the stability of the solution?
SQL Server is highly stable.
What do I think about the scalability of the solution?
SQL Server is very scalable because we use it across a couple of different types of applications, such as micro-infrastructure setup and server farm.
The solution is suitable for any environment, such as small, medium, and large enterprises.
How are customer service and support?
SQL Server support system is well-established. It's a Microsoft solution therefore you receive support very easily. It is the number one selling point of SQL Server. I have been highly satisfied with the support.
How was the initial setup?
SQL Server's initial setup is simple. However, you must be a specialist to do it. That's the unfriendliness that I see about the solution. It has to be done by an engineer and not any engineer can do it, you have to be a specific Microsoft engineer.
What other advice do I have?
My advice to others would be to create a standard for SQL Server to allow a high level of security. What we did is, we adopted CIS, which is the Center for Information Security, hardening standards and benchmarks to keep it secure. SQL Server out of the box comes with a lot of unnecessary services that can make you very vulnerable to any site attack.
I rate SQL Server an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Technical Director/ Project Manager / Consultant at SC Iceberg Data Intelligence SR
User-friendly and cost effective Server for ETL and reporting
Pros and Cons
- "This solution is user-friendly and easy to understand."
- "The stability of the solution should be improved in the next release. Sometimes it is great, sometimes it is troublesome. I would also like data conversion and the code pages to be a bit more straightforward."
What is our primary use case?
I am an integrator of this solution and my customers use this for ETL and reporting.
What is most valuable?
This solution is user-friendly and easy to understand.
What needs improvement?
The stability of the solution should be improved in the next release. Sometimes it is great, sometimes it is troublesome. I would also like data conversion and the code pages to be a bit more straightforward.
For how long have I used the solution?
I have been working with SQL Server for the past fifteen years.
What do I think about the stability of the solution?
Stability can be shaky.
What do I think about the scalability of the solution?
This is a scalable solution.
Which solution did I use previously and why did I switch?
I use to work with Informatica via the Oracle package and switched to SQL because it is cheaper and a bit better than the others.
How was the initial setup?
This solution is pretty easy to deploy.
What's my experience with pricing, setup cost, and licensing?
SQL Server has the best licensing price.
What other advice do I have?
There is a lot to learn about this solution when first using it, as with any other tool.
I would rate this solution an eight out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator

Buyer's Guide
Download our free SQL Server Report and get advice and tips from experienced pros
sharing their opinions.
Updated: March 2025
Product Categories
Relational Databases ToolsPopular Comparisons
MySQL
Teradata
Oracle Database
MariaDB
SAP HANA
IBM Db2 Database
Amazon Aurora
CockroachDB
LocalDB
IBM Informix
Citus Data
Oracle Database In-Memory
YugabyteDB
SAP IQ
SAP Adaptive Server Enterprise
Buyer's Guide
Download our free SQL Server Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Microsoft sql2017 VS SAP Hana
- SQL Server 2005 vs. InfoBright - what are the pros and cons of these solutions?
- SQL Server 2012 - can I make OLTP transactions from my ERP run in memory?
- How does NuoDB compare to MySQL and SQL Server?
- What are the main architectural differences between Microsoft SQL Server and Oracle Multitenant?
- Would you say the price of SQL Server is high compared to that of similar products?
- Has using SQL Server helped your organization in any way?
- Which authentication mode is best for SQL Server?
- Which solution do you prefer: Microsoft SQL Server's enterprise edition or Oracle Database's enterprise edition?
- Which is better: SQL Server or SAP HANA?