The columnstore index feature is useful for us, and we also use the integration services. It is also very stable.
Data Architect/Engineering manager at Intellias
Stable, scalable, and good integration services
Pros and Cons
- "The columnstore index feature is useful for us, and we also use the integration services. It is also very stable."
- "We would like to have a common storage option in the SQL Server. This option is available in Oracle Database. It would be great if Microsoft could create something like a columnstore that has not only indexing but also tables for common storage."
What is most valuable?
What needs improvement?
We would like to have a common storage option in the SQL Server. This option is available in Oracle Database. It would be great if Microsoft could create something like a columnstore that has not only indexing but also tables for common storage.
For how long have I used the solution?
I have been using SQL Server for four years.
What do I think about the stability of the solution?
It is pretty stable.
Buyer's Guide
SQL Server
October 2026
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
922,921 professionals have used our research since 2012.
What do I think about the scalability of the solution?
If we talk about just standard RDBMS, it is very scalable because we don't have to scale platforms.
How are customer service and support?
All communication with Microsoft technical support is done by our internal support group. I'm not communicating with them directly. I guess their technical support is okay and fast.
What other advice do I have?
I would recommend SQL Server as a solution for a medium enterprise or a small business.
I would rate SQL Server an eight 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.
IT manager at IRPC PCL
An easy initial setup with good pricing and good stability
Pros and Cons
- "The pricing of the product is very good."
- "We've mostly been pretty happy with its performance."
- "The solution could offer better integration with other solutions - specifically Microsoft."
What is our primary use case?
We primarily use the solution as a WAP server and we have it on-premises.
How has it helped my organization?
It's helped us connect to our company's machines.
What is most valuable?
The pricing of the product is very good.
We've found the stability to be very reliable.
The initial setup isn't too complicated. It's pretty straightforward.
What needs improvement?
Overall, the solution could be improved in future releases. We hope to improve the way we use it ourselves in our next project.
The solution could offer better integration with other solutions - specifically Microsoft.
For how long have I used the solution?
I've been using the solution for about five years at this point. It'd been a while.
What do I think about the stability of the solution?
Thus far, the solution has been quite stable. It doesn't crash or freeze. there aren't bugs or glitches. It works well for us overall and we find it to be reliable.
What do I think about the scalability of the solution?
I'm not sure about the capability of the solution's scalability. We've never really tested its capabilities, and it's therefore hard to gauge.
How are customer service and technical support?
We have a department that handles support. I find them knowledgeable. They respond in a reasonable amount of time.
How was the initial setup?
The initial setup wasn't complex. It was pretty straightforward. We didn't have any issues with the implementation process at all.
What's my experience with pricing, setup cost, and licensing?
The licensing is reasonable. It's not too expensive. We are charged on a yearly basis, however, I don't know the exact amount we are charged. I'm not a part of the billing and payments department.
What other advice do I have?
I believe we are using the 2019 version of the solution.
In general, I would recommend the solution to other organizations. We've mostly been pretty happy with its performance.
We're not Microsoft partners. We are just customers.
Overall, I would rate the solution eight out of ten. If it had better integration capabilities with Microsoft, I might rate it higher.
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.
Buyer's Guide
SQL Server
October 2026
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
922,921 professionals have used our research since 2012.
Owner at BNS
Reliable, with good programmability, and helpful web support
Pros and Cons
- "The most valuable features are programmability and reliability."
- "My experience is limited, but compared with Oracle, Microsoft SQL Server is many times better and easier to program with."
- "Price could be cheaper, and access to reporting tools should be better."
What is our primary use case?
We are using this solution for business websites.
What is most valuable?
The most valuable features are programmability and reliability.
What needs improvement?
Price could be cheaper, and access to reporting tools should be better.
For how long have I used the solution?
I have been working with SQL Server for more than 20 years.
What do I think about the stability of the solution?
It's a stable product.
What do I think about the scalability of the solution?
It has limited scalability, but it's perfectly adequate for our needs. We apply vertical scalability to it and not horizontal.
We are a very small software development company, scaling is not an issue for us.
How are customer service and technical support?
Technical support is good.
In general, we use what is available on the web, rather than talking to people. The articles on the web are more useful.
We have no particular issue with Microsoft.
How was the initial setup?
The initial setup was straightforward. It was very easy to do.
What's my experience with pricing, setup cost, and licensing?
The price could be cheaper.
What other advice do I have?
The marketing for dealer support and that type of environment is very contorted. It's very difficult to access, but, with the technical side of things, they are fine.
My experience is limited, but compared with Oracle, Microsoft SQL Server is many times better and easier to program with. So, I love Microsoft. I don't like Oracle.
I would rate SQL Server a ten 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
Technical Department Manager at Direcbusiness Technologies, Inc.
Straightforward setup and good stability
Pros and Cons
- "We have many users, between 50 and 100 using the SQL Server product."
- "We have been using SQL Server from the start, so it's a stable product."
- "Right now we don't get much technical support from Microsoft"
What is our primary use case?
We use it mostly for integration into an ERP system. We also use it for our internal development of products.
How has it helped my organization?
We have many users, between 50 and 100 using the SQL Server product.
What is most valuable?
We have been using SQL Server from the start, so it's a stable product.
What needs improvement?
I think a web console for the management studio, I think that would be a good thing. I think also on load balancing. I think that's something that we can use.
For how long have I used the solution?
We've been using SQL Server for 12 years. We are currently using the latest version. It is deployed on-premise and cloud.
What do I think about the stability of the solution?
The product is stable.
What do I think about the scalability of the solution?
The product is scalable.
How are customer service and technical support?
Right now we don't get much technical support from Microsoft. I think for all issues we encounter, we do the solutions by ourselves. I think if there should be some avenue for us to raise some issues that we are encountering, so maybe that would be something that's good for us as well. It is not easy to contact Microsoft support for this product.
How was the initial setup?
Setup required two engineers to deploy it. It was pretty straightforward and took one to two days.
What's my experience with pricing, setup cost, and licensing?
We didn't have any licensing costs for SQL Server.
What other advice do I have?
I would recommend this product to others and give it an 8 out of 10.
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. Implementer
Enterprise Solutions Department Manager at Smart Vision
A stable solution for storing and retrieving data
Pros and Cons
- "The technical support is good."
- "SQL Server is both scalable and stable."
- "The user interface and the reporting could also be improved."
- "The time series database could be improved."
What is our primary use case?
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.
What needs improvement?
The time series database could be improved. There needs to be more storage space for large documents.
The user interface and the reporting could also be improved. It's not bad, but it could be improved upon.
For how long have I used the solution?
I have been using this solution for 20 years.
What do I think about the scalability of the solution?
SQL Server is both scalable and stable.
How are customer service and technical support?
The technical support is good.
How was the initial setup?
Installation was very easy. We had it installed within one hour.
What about the implementation team?
One of our team members deployed it.
What other advice do I have?
I would definitely recommend this solution to others.
On a scale from one to ten, I would give SQL Server a rating of eight.
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: My company does not have a business relationship with this vendor other than being a customer.
System Engineer at a financial services firm with 1,001-5,000 employees
Good system architecture but they need to implement load-balancing capabilities
Pros and Cons
- "SQL Server is a stable product."
- "The most valuable feature is the system architecture."
- "The number of concurrent users is too limited and other databases are better than SQL in this regard."
- "We are the largest micro-credit finance company with more than thirty companies internally. We have 25,000 employees using the business application and SQL does not scale to our requirements."
What is our primary use case?
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.
What is most valuable?
The most valuable feature is the system architecture.
What needs improvement?
The number of concurrent users is too limited and other databases are better than SQL in this regard.
There are limitations with load balancing.
We would like to see support for in-memory processing.
For how long have I used the solution?
We have been using SQL Server for more than seven years.
What do I think about the stability of the solution?
SQL Server is a stable product.
What do I think about the scalability of the solution?
We are the largest micro-credit finance company with more than thirty companies internally. We have 25,000 employees using the business application and SQL does not scale to our requirements.
I think that Oracle is better suited to smaller applications.
How are customer service and technical support?
The supporting sites are good.
Which solution did I use previously and why did I switch?
I have also worked with SAP HANA.
How was the initial setup?
Setting up the database clustering is too complex.
Our current deployment has been ongoing for three years and it is not yet complete because our application is still being developed.
What about the implementation team?
Our in-house team is handling the deployment.
Which other solutions did I evaluate?
We are currently searching for other products to replace this one with.
What other advice do I have?
My advice for anybody who is considering SQL Server is that it works well for small applications. However, large business applications that use a content delivery network or geographical location, it is not suitable for.
I would rate this solution a seven out of ten.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Deputy Manager IT at Carl Bechem Lubricants India Pvt. Ltd.
Users can quickly and efficiently retrieve a large amount of records from a database
Pros and Cons
- "The latest version supports for big data analytics. SQL Server's vector processing-based batch execution mode is now available to the entire execution of R or Python code. Since much of the work that tends to be done in R and Python involves aggregation, batch mode - which processes rows of data several at a time, can be very helpful."
- "It is an overall very good product."
- "CAL licenses should cost less. Microsoft usually prices high for client access licenses. Server plus user client access license (CAL) licensing requires a separate Server license for each server on which the software is installed, plus a user CAL for each user accessing the server."
What is our primary use case?
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.
How has it helped my organization?
Microsoft database is very user friendly. This new version of SQL Server continues to meet these twin demands. It adds new features from the worlds of data science and NoSQL. It offers cross-platform capabilities and Docker container compatibility. But it also reinforces its investment in core database engine performance, ease of index maintenance, high availability, and data warehouse performance. That's a difficult balance and one that other database vendors don't have to meet. While this may be Microsoft's cross to bear, the company does pretty well with it, turning a formidable challenge into a positive market differentiator.
What is most valuable?
The latest version supports for big data analytics. SQL Server's vector processing-based batch execution mode is now available to the entire execution of R or Python code. Since much of the work that tends to be done in R and Python involves aggregation, batch mode - which processes rows of data several at a time, can be very helpful. Two other new batch mode features, memory grant feedback, and adaptive joins will enhance SQL Server's performance and efficiency as well. It is good to move from Microsoft to deal with big data analytics
What needs improvement?
CAL licenses should cost less. Microsoft usually prices high for client access licenses. Server plus user client access license (CAL) licensing requires a separate Server license for each server on which the software is installed, plus a user CAL for each user accessing the server. A SQL Server CAL is required for a user to access or use the services or functionality of either edition of SQL Server and frequent updates to the latest versions will lead to obsolete and discontinuing the security patches has to be improved.
For how long have I used the solution?
Since two years
What do I think about the stability of the solution?
Very good stability with 250-300 users.
What do I think about the scalability of the solution?
This product can withstand with 250-300 users.
How are customer service and technical support?
Very good.
Which solution did I use previously and why did I switch?
SQL standard 2008.
How was the initial setup?
Straightforward - no complexity.
What about the implementation team?
Vendor team with an in-house team.
What was our ROI?
2 years.
What other advice do I have?
It is an overall very good product.
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.
General Manager/MVP at Yotta Infrastructure Solutions LLP
Reliable, Stable, And Cost-effective Solution For A Small Database
Pros and Cons
- "The features that we have found the most valuable are reliability, availability perspective, and current scalability."
- "SQL Server suffices our main requirement of a small database, and it is also very cost-effective."
- "The scalability and the high availability feature can be expanded or improved. Currently, there is a limitation on scalability. A feature similar to the Oracle Diagnostic feature can be included to provide a better user experience."
What is our primary use case?
We use on-premises, standalone deployment of SQL Server for our own CRM database. There are around seven to eight users in our company.
How has it helped my organization?
SQL Server suffices our main requirement of a small database, and it is also very cost-effective.
What is most valuable?
The features that we have found the most valuable are reliability, availability perspective, and current scalability.
What needs improvement?
The scalability and the high availability feature can be expanded or improved. Currently, there is a limitation on scalability.
A feature similar to the Oracle Diagnostic feature can be included to provide a better user experience.
For how long have I used the solution?
We have been using SQL Server for around 10 years.
What do I think about the scalability of the solution?
Stability and scalability are both good. It suffices for our current requirements, but if we want to scale up in the future, it has limitations.
How are customer service and technical support?
We sometimes contacted Microsoft technical support, and we also have in-house Microsoft support. We are happy with the support.
How was the initial setup?
The initial setup was straightforward.
What about the implementation team?
Our in-house team handled the deployment.
What's my experience with pricing, setup cost, and licensing?
SQL Server is a cost-effective solution for a small database.
What other advice do I have?
I would definitely recommend SQL Server.
I would rate SQL Server an eight out of ten.
Not a ten because it has some limitations. When considering overall scalability, reliability, features, if you look at Oracle, it's still ahead of SQL Server.
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
Assistant Manager at ECU
Great security features; query store was particularly helpful with data analysis
Pros and Cons
- "Very good security features."
- "Security is obviously the most valuable feature because I can provide certain logins for a particular level of security and I can provide specific permissions for certain logins."
- "Query optimitzer could be simplified."
- "I'd like to see a simplification of the query optimizer and feel that SQL needs to look into the internal processing of the query because the query optimizer sometimes uses a different query plan, which we don't expect."
What is our primary use case?
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.
What is most valuable?
Security is obviously the most valuable feature because I can provide certain logins for a particular level of security and I can provide specific permissions for certain logins. That's a very good feature. I like the user interface as well, it's easy to use. The SSMS Management Studio, which we use to do some work in database file query is a recent feature from 2018 and the SSMS is quite good. It has many features and it also shows the query statistics which I was not getting previously. The other feature I like is the query store which helped me a lot to analyze the data getting hit on the database.
What needs improvement?
I'd like to see a simplification of the query optimizer and feel that SQL needs to look into the internal processing of the query because the query optimizer sometimes uses a different query plan, which we don't expect. It is similar to the triggers they have which are used after execution and not before. For example, if I'm running a query, my trigger will be run after the query has executed although I sometimes need the trigger before execution. That's a feature not supported by the product.
For how long have I used the solution?
I've been using this solution for four years.
What do I think about the scalability of the solution?
It is quite scalable compared to other data engines and the latest version has increased support for new technologies, like Python and other languages. It's a big improvement on the previous version. We have 30 to 40 SQL servers installed and they're used for different different applications; internal applications, client applications as well as for ETA tools and reporting purpose. We probably have up to 200 users querying the SQL server of the product on a daily basis.
How are customer service and technical support?
I'm satisfied with the technical support. Whenever a call is raised to Microsoft they see to it that all our questions are answered properly and in a timely manner. It doesn't take long for things to be resolved.
How was the initial setup?
The initial setup is very straightforward, just like any typical software where you just click next, next, next, next. You just need to know your environment properly and which exact features you need to install. Deployment takes max one to two hours to install on-premises. Depending on the environment and whether or not you're installing any cluster environment, it will take a couple of hours. To deploy a stand-alone SQL server doesn't take much time.
What other advice do I have?
I would recommend this solution, particularly for OLTP purposes, the transactional data purpose rather than for warehousing. For data warehousing I think there are better solutions but for the transaction data, for application purposes, SQL Server great.
I would rate this solution a nine out of 10.
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.
Buyer's Guide
Download our free SQL Server Report and get advice and tips from experienced pros
sharing their opinions.
Updated: October 2026
Popular Comparisons
Teradata
Snowflake
Oracle Database
MySQL
MongoDB Atlas
SAP HANA
IBM Db2 Database
MariaDB
Amazon Redshift
CockroachDB
SAP IQ
Google Cloud SQL
Oracle Database In-Memory
Amazon Aurora
Actian Ingres
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?















