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.
Chief Technology Officer at KOLOK SA
Many licensing options, quick installation, and scalable
Pros and Cons
- "SQL Server is a very mature solution."
What is our primary use case?
What is most valuable?
SQL Server is a very mature solution.
For how long have I used the solution?
I have been using SQL Server for approximately 20 years.
What do I think about the stability of the solution?
SQL Server is a stable solution.
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.
861,524 professionals have used our research since 2012.
What do I think about the scalability of the solution?
The scalability of SQL Server is good. It can scale up to thousands of times more data than I have.
We have approximately 250 people using this solution in my organization.
How are customer service and support?
I have not used the support from SQL Server.
How was the initial setup?
The initial setup is simple it takes approximately 10 minutes. You only need to run the setup and you have SQL installed.
What about the implementation team?
I have installed SQL databases and SQL Servers regularly. I did the implementation of this solution.
This solution requires one administrator for implementation and maintenance.
What's my experience with pricing, setup cost, and licensing?
Some of the licensing are very expensive, such as the Enterprise license.
The Express version is free. There are a lot of licensing options.
What other advice do I have?
I would recommend this solution to others.
I rate SQL Server a nine out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.

CEO at TMentors
Problem-free, easy to implement, and very reliable
Pros and Cons
- "The scalability is very good."
- "The remote access aspect needs to be improved in terms of security."
What is our primary use case?
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.
What is most valuable?
Overall, we've been satisfied with the capabilities of the product.
The solution is stable. It works without issue - to the point you rarely need any technical support at all.
The scalability is very good.
It's got an easy initial setup.
What needs improvement?
The remote access aspect needs to be improved in terms of security. Right now, it's a little bit hard.
Also, they need to work on the user interface, as it's a little bit old. They need to improve it a little bit.
The pricing could be lowered a bit.
For how long have I used the solution?
We've used the solution for a while.
What do I think about the stability of the solution?
Its stability has been good. The solution performs well and is reliable. There are no bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
We have found the solution to be scalable. If a company needs to expand, it can do so.
How are customer service and support?
Techni al support is good. That said, it's hard to judge as you don't need support on SQL Server. It's working without trouble or issues. Therefore, it's rare to seek support for SQL Server. You rarely have to deal with them.
Which solution did I use previously and why did I switch?
I've also used SQL Azure.
The recommendation is based on the use case. It depends on what use case the customer will need. If they don't have the capacity to manage their own Server, I would recommend Azure, as it's managed. Therefore, you don't have to worry about the management and administration.
The main difference between the two is, in some data types it is not available on SQL Azure while it's available on SQL Server or vice versa. There's a version of SQL Server with a little bit of limited functionality. That said, the difference is not huge. You can go back and forth between them if you want.
How was the initial setup?
The initial setup is very easy. It's even easier than before, in fact. A company shouldn't have any problems with the implementation.
What's my experience with pricing, setup cost, and licensing?
The price could be less.
What other advice do I have?
I'd rate the solution at an eight out of ten. If the price was a bit less or the remote access was better, I would rate it tighter.
In general, I've been happy with the product.
Disclosure: My company has a business relationship with this vendor other than being a customer. partner
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.
861,524 professionals have used our research since 2012.
It's an inexpensive solution that integrates well with cloud-based tools
Pros and Cons
- "SQL Server is an inexpensive solution. I recommend it if the project isn't sensitive. SQL is similar to Oracle and integrates well with tools in the cloud environment. The difference is that Oracle is for data solutions where there is replication and moderation."
- "Our biggest problem with SQL Server is latency. The communication between the cloud and the on-premises environment is slow. The data needs to be encrypted for security, and you have to exchange data certificates between environments. You can adjust the configuration to improve performance, but it would be nice if SQL Server had some templates to resolve problems."
What is our primary use case?
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.
What needs improvement?
Our biggest problem with SQL Server is latency. The communication between the cloud and the on-premises environment is slow. The data needs to be encrypted for security, and you have to exchange data certificates between environments. You can adjust the configuration to improve performance, but it would be nice if SQL Server had some templates to resolve problems.
For how long have I used the solution?
I have been working with SQL Server for 10 years.
Which solution did I use previously and why did I switch?
I worked on Oracle Database for four years. In the last year, I have been working with various cloud databases, including Cosmos DB and DynamoDB in AWS and Azure.
What other advice do I have?
I rate SQL Server nine out of 10. SQL Server is an inexpensive solution. I recommend it if the project isn't sensitive. SQL is similar to Oracle and integrates well with tools in the cloud environment. The difference is that Oracle is for data solutions where there is replication and moderation.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
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
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
Team Lead, Process Improvement at Fidelity Bank Plc
Easy to use, reliable and simple to set up
Pros and Cons
- "Backups hardly get corrupt."
- "The pricing could be more affordable."
What is our primary use case?
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.
What is most valuable?
I like the way it can manage the users from the security section where you can change their roles.
SQL is simple to manage, as long as you know the script, and know the tables that you make reference to. If there are errors, you can easily debug them.
You can easily debug and resolve your issues.
The ease of backup, how you can back up and call up your backups too is great. Backups hardly get corrupt, except if maybe you have some bad hard drive clusters or bad hard drive sectors.
It is stable.
It's an easy-to-use product.
I find the solution to be scalable.
What needs improvement?
The pricing could be more affordable.
It's like to see less frequent updates. They should be once a month.
For how long have I used the solution?
I've been using SQL Server for a very long time.
What do I think about the stability of the solution?
The stability is great. It's very reliable. There are no bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
The product scales well. If you need to expand it, you can.
We have around 50 users on the solution right now.
How are customer service and support?
The solution is pretty problem-free and therefore it would be rare to have to reach out to support.
Which solution did I use previously and why did I switch?
We've always used SQL. I also use SQLite.
How was the initial setup?
The initial setup is very simple, very straightforward. It's not too complex.
The time it takes to set up isn't long. The time of installation is determined by the local system or the server where you are installing it to. That said, it's a light solution. For me, it took maybe ten minutes.
We have eight people who are technical and can handle deployment or maintenance tasks.
What about the implementation team?
I did the installation myself. It's not hard to do. You don't need a consultant or integrator.
What's my experience with pricing, setup cost, and licensing?
We pay a monthly subscription fee.
What other advice do I have?
I'm an end-user.
I would recommend the solution to other users and organizations.
Overall, I would rate it at a nine out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Co-Founder at a logistics company with 1-10 employees
User-friendly and reasonably priced system for storing and managing information
Pros and Cons
- "Easy to implement and user-friendly relational database management system. This product is stable and scalable."
- "The UX design of this system needs improvement."
What is our primary use case?
We're using SQL Server for database work.
What is most valuable?
What I find most valuable in SQL Server is that it's user-friendly.
What needs improvement?
The product needs improvement in its UX design. A newer interface is what I'd like to see in the next release of SQL Server.
For how long have I used the solution?
I've been working with SQL Server for two years.
What do I think about the stability of the solution?
SQL Server is a stable system.
What do I think about the scalability of the solution?
SQL Server is a scalable system.
How are customer service and support?
I'm satisfied with the technical support provided by Microsoft for this product.
How was the initial setup?
SQL Server is easy to implement, especially because it's a very common system that we use in the workplace.
What's my experience with pricing, setup cost, and licensing?
Pricing for this product is very reasonable.
Which other solutions did I evaluate?
I evaluated Oracle Database.
What other advice do I have?
SQL Server is a common product that I use on a daily basis, and I'm using its latest version. Most of my colleagues use it for database work.
200 people use this system in the company.
My advice for people looking into using SQL Server is that it's the best choice, especially for those who are beginners with databases.
My rating for SQL Server is nine out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Senior Database Administrator at a tech services company with 501-1,000 employees
Secure, good GUI, and easy to use
Pros and Cons
- "Its security is good. The GUI of SQL Server is also very good."
- "It is very costly, and that's the reason people are moving away from SQL Server."
What is our primary use case?
We are using it for storing important data.
What is most valuable?
Its security is good. The GUI of SQL Server is also very good.
What needs improvement?
It is very costly, and that's the reason people are moving away from SQL Server.
They have started using Linux, and Linux is the way forward for SQL Server. They have to invest a lot in that.
For how long have I used the solution?
I have been using this solution for almost 10 years.
What do I think about the stability of the solution?
Its stability is good.
What do I think about the scalability of the solution?
Its scalability is good.
How are customer service and support?
I haven't spoken to their support team in the last three years, but prior to that, their support was good.
Which solution did I use previously and why did I switch?
I also have experience with Postgres. The main difference between SQL Server and Postgres is that Postgres is open source. The Community version of Postgre is basically free. Postgres is very easy to set up and very easy to scale. It is quite a good database.
How was the initial setup?
It is very easy.
What's my experience with pricing, setup cost, and licensing?
It is expensive in terms of licensing costs and pricing. If you want to scale SQL Server, it is very expensive.
We probably have to pay extra for technical support. We also have to pay for the license of Windows on which the SQL Server resides, which is an extra cost.
What other advice do I have?
I would recommend SQL Server for its stability, scalability, and ease of use. I would rate it an eight out of 10.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.

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
Teradata
MySQL
Oracle Database
SAP HANA
MariaDB
IBM Db2 Database
Amazon Aurora
CockroachDB
LocalDB
Citus Data
Oracle Database In-Memory
IBM Informix
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?