Out of all the tools in the complete SQL Server package, I'm mainly using Toolbox and SQL Profiler because I'm using SSIS packets, so we're using job scheduling a lot. And sometimes we are creating the SSIS packages, so I'm using SQL Server for MSD for maintenance purposes. SQL Server is quite user-friendly. I have experience with Oracle and PostgreSQL, so out of three, I like SQL Server a lot.
Technical Lead at a computer software company with 5,001-10,000 employees
User-friendly with a lot of tools
Pros and Cons
- "SQL Server is quite user-friendly. I have experience with Oracle and PostgreSQL, so out of three, I like SQL Server a lot."
- "It may be a licensing issue, but sometimes its operating speed becomes slow if we have multiple users. It's lacking some performance, but it's acceptable because we have a heavy load."
What is most valuable?
What needs improvement?
They could increase the intelligence of SQL Server. That would be good for us. There are some good intelligent features in SQL Server. However, they need to increase the intelligence because people switching to SQL Server from other solutions are not so familiar with it. I've been working with SQL Server for the last six years, but people are coming from MySQL or Oracle, so it will take one or two months to adjust. Still, they could add some intelligent tools to convert Oracle into SQL Server something like that.
And sometimes when I'm writing a function, there is already a predefined structure available. So if they defined their structure more precisely, that would be good for us. And the last thing I would like to add is that SQL Server should handle queries more like Oracle does. For example, you submit a query in Oracle, and the whole table comes up. In SQL Server, you go to the table, right-click, and it lets you see the first 200 rows. Then on top of that, you can add 200 more rows.
So in place of those 200 rows, if I can update all my table records or search my table record without a new search query, it'll be very beneficial. That functionality exists in Oracle, but this feature is not available everywhere in SQL Server. So if SQL Server had the feature, it'd be great because SQL Server is lacking only on this point. For example, one of my clients is a semi-technical person, so I have to train them to file a query in SQL. And they say that Oracle is much better. Say, for example, that I wanted to query a particular employee from a list of all staff. So the query output comes, and they can directly filter out the data by just applying the filter. They don't have to use the drop-down menu and search for all the employees with a given name.
For how long have I used the solution?
I've been using SQL Server for the last six years. I'm working with SSIS, SSRS, or MDS. These tools are part of SQL Server, and the back-end queries are developed in SQL Server.
What do I think about the stability of the solution?
SQL Server is stable. SQL Server has crashed only two times in six years, but it wasn't a major system error.
Buyer's Guide
SQL Server
August 2025

Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
867,497 professionals have used our research since 2012.
What do I think about the scalability of the solution?
It may be a licensing issue, but sometimes its operating speed becomes slow if we have multiple users. It's lacking some performance, but it's acceptable because we have a heavy load. And I would like to add that we're running SQL Server and SSIS at the same time. So while I've found that SQL Server is quite fast, SSIS is a part of SQL Server. It is just for data testing in India. But if a person knows SSIS, then they usually have very little knowledge about SQL and vice versa.
I know both of them. I found that maybe it's a bad habit, but I'm using SSIS packages. And in the SSIS package, I'm using Toolbox from SQL Server to improve the latency. Implementing both together takes a little time. And one more point is data handling. I am just forwarding the error names, and there are multiple errors in the SQL Server tool, but what if a person comes to work under me and has only one or two years of experience? Sometimes it might be difficult for them to understand what the errors mean. For example, when joining data, it's easy to implement the inner joint. In the inner joint, there are two columns, so when there's an output error, someone who is inexperienced with SQL Server might not understand. Error messages should be a little more precise and defined, so it's easy to understand.
How was the initial setup?
Setting up an individual SQL Server is pretty straightforward, but when you are implementing multiple tools, it's more complicated. In terms of maintenance, for the DBA part, there are two based in my company because I am on a master device, so they don't allow me to maintain the server part. So one person is from South Korea, and the other is from China. They are handling my SQL Server. So maybe there are multiple teams, but I am contacting these two guys, the DBA. And I'm MDS, so I'm a single person. There are two people on my team, and I have one junior staff member. So I have a three-person team, and there are two DBA sites because I'm discussing my master team. I am deployed on the business side, and there are more than 80 people who are end-users of SQL.
Which other solutions did I evaluate?
If you're using SQL Server along with SSIS and SSRS tools, it works pretty smoothly and all. When working with Oracle SQL, PostgreSQL, MySQL, etc, there are a few problems with the connection.
Overall, SQL Server is good, but sometimes, optimization becomes a little bit tricky when you're using SQL Servers in place of Oracle. For example, while I was implementing two queries one time, the SQL Server gave me the wrong results. This wasn't because of their internal modules. So there may have been some missing data, but SQL Server failed to identify those issues. SQL Server needs to improve there.
For example, say there is a line with a value of 136 or 137. The second value is a space, and the third value is null. And the last one is space. So a space means this is also null. So you are comparing these four values, and if you don't have any idea about data, it's a little problematic. So cases like this, we can deal with such queries using syntax, but if a person has no idea how to deal with this, they'll face an issue.
Here's another example. Say there's a team query that means we are erasing data from the teams, and some people are just analyzing the string. So I see data from it, which means the calling system is there. In the calling system, we receive the data to call anyone, and that type of wire call setup is there. So I am receiving a full-text format from the file I have to upload in the SSIS package. And some cells have a null value. It's a text file, so you can understand there are blanks in some places. I don't know the file type, so I am just trying to dump it into our SQL Server. But when I have time to get to that table, I realize that some values are null, space, and blank. So these four values make problems for me.
What other advice do I have?
I rate SQL Server nine out of 10. I would recommend SQL Server to anyone because you can use cloud-based services, so it's very beneficial. If you install SQL Server on-premise and on the Azure cloud, it is much more advantageous for you.
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.

Sr. Supervisor - Enterprises Application DBA at a manufacturing company with 10,001+ employees
A relational database management system that's easy to use
Pros and Cons
- "I like that it's very easy to use, and Veeam is excellent. There are tons of experts and writers in the area now, and we don't find the same for other databases."
- "The price could be better. In the next release, it would be better if the database was more easily extendable."
What is our primary use case?
Despite the core database is not SQL Server in my working company, SQL Server is widely being used as the backend for many in-house applications and customized applications like Solarwinds.
How has it helped my organization?
Helping to effectively and efficiently manage the business-critical data
What is most valuable?
- There are hundreds of "Dynamic Management Views" (DMVs) & Dynamic Management Functions (DMFs) that are system views & system functions that return metadata of the system state and they provide valuable insight into the current SQL instance state.
- Resumable online index rebuild
- Table Partitioning and the Swap out to covert a Table Partition into a separate table.
- Python & R2 Integration, Graph Databases
- Automatic Database Tuning
- Very reliable Backup technology and many more
What needs improvement?
The price could be better:
Compare to Oracle it is cheaper but with the existence of many open source databases currently in the market, consider reducing the Licensing cost. Secondly, with the Core-based Licensing since SQL 2012 Version, the SQL Licensing price has substantially increased.
Postgres Extensions is a concept in Postgres to extend the Postgres features that are very useful for Performance Monitoring & Optimizations. Similarly option to extend the features as necessary.
For how long have I used the solution?
I have been using SQL Server for 12 years.
What do I think about the scalability of the solution?
It's been scalable since 2016. With each version, they are adding more features which are very helpful.
How are customer service and technical support?
On a rare occasion, I had contacted technical support about five or six years ago and only when I had a specific use case.
How was the initial setup?
The GUI-based step-by-step initial setup is easier for the initial setup and even the Jr.DBAs can handle it with minimal training. The automated installation is possible with PowerShell Scripts and the Infrastructure Provisioning and Configurations tools like Ansible. We managed to automate the SQL installation using Ansible Playbooks and Gitlab to deploy Continous Integration and Continous Deployment.
What about the implementation team?
We implemented this solution by ourselves.
What's my experience with pricing, setup cost, and licensing?
CPU Core-based Licensing & Windows Licensing costs are additional overheads compare to open source databases like MySQL and PostgreSQL.
Managed SQL Server Database Service in Azure is lagging with many features like Linked Server, DB Mail.
SQL Server deployment in the Cloud does not seem to be cost-effective with respect to the Licensing cost and average Life cycle of 5 years (I reiterate, this is in my opinion).
If you take Postgre SQL and MySQL, they provide almost all the same features even though they are both open source databases.
What other advice do I have?
I recommend this solution because you can engage in database manipulation, administration and manage almost all your requirements. When compared to Oracle licensing costs, SQL Server is better.
On a scale from one to ten, I would give SQL Server a 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.
Buyer's Guide
SQL Server
August 2025

Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
867,497 professionals have used our research since 2012.
Works at a manufacturing company with 10,001+ employees
A stable, scalable, and easy-to-deploy solution that pretty much covers everything
Pros and Cons
- "It is a pretty good solution. The on-premise version 2019 has many features, and they had introduced a really good and stable environment in version 2019. It has very good integration with big data clusters and other things. It covers pretty much everything that you can do with a SQL server. You can use any language to connect to it, which is not there in other solutions. They have also introduced Python, and it also has ArcScale. PaaS is a modern, scalable database. You can use Power Automate and a lot of features in this. It is very easy, and you don't have to worry about versions and upgrades. Microsoft keeps on adding new features to this solution. Microsoft is improving its connectivity on an ongoing basis. It connects well with Office 365. If you see something not working, in a couple of weeks, it is going to work because there is a team working on it. You can vote for the things that are missing, and Microsoft can work on them depending on the product that they're launching."
- "There are a lot of improvements in the cloud space about which we open a case with Microsoft every now and then. These improvements are not in terms of features or functionality. They are more related to their own compatibility or connectivity on which they keep on working to improve the product."
What is our primary use case?
The .NET applications use SQL Servers on a very large scale. Basically, about 80% or 90% of the database platform is on SQL Server.
We are working on version 2019, but we are also now working on the cloud databases. Our goal is to stay away from versions. We are going to go version-less and move to Azure SQL or managed instance, which is version-less. This way we won't need to worry about any upgrades or any version changes because Microsoft is going to take care of these things. We will always have the latest and greatest version.
What is most valuable?
It is a pretty good solution. The on-premise version 2019 has many features, and they had introduced a really good and stable environment in version 2019. It has very good integration with big data clusters and other things. It covers pretty much everything that you can do with a SQL server. You can use any language to connect to it, which is not there in other solutions. They have also introduced Python, and it also has ArcScale.
PaaS is a modern, scalable database. You can use Power Automate and a lot of features in this. It is very easy, and you don't have to worry about versions and upgrades.
Microsoft keeps on adding new features to this solution. Microsoft is improving its connectivity on an ongoing basis. It connects well with Office 365. If you see something not working, in a couple of weeks, it is going to work because there is a team working on it. You can vote for the things that are missing, and Microsoft can work on them depending on the product that they're launching.
What needs improvement?
There are a lot of improvements in the cloud space about which we open a case with Microsoft every now and then. These improvements are not in terms of features or functionality. They are more related to their own compatibility or connectivity on which they keep on working to improve the product.
For how long have I used the solution?
I have been using this solution for 13 to 14 years.
What do I think about the stability of the solution?
In version 2019, they introduced a really good and stable environment. Bugs are there, but bug fixes are provided by Microsoft. We have premium support with Microsoft. If we find a bug, they work on it and provide a solution.
What do I think about the scalability of the solution?
It is very scalable, but its scalability also depends on what you're using. If it is on-premise, you have to do everything on your own to scale it out. It is easy, but you have to get the infrastructure ready to scale it out. It is a manual process. If you're on a cloud, then it is pretty much easy and straightforward if your cloud has those availabilities. It also has a Hyperscale, where you can put the upper and lower limit, and it can scale up and down as per the use case and the compute that you need.
We have a lot of users. Everyone is connected to this. We have business users, technical users, application users, and integration users. We have 17,000 instances of SQL Server here with a lot of databases.
How are customer service and technical support?
We use Microsoft's Premium Support. They're good. I would rate them an eight out of ten. For on-premise, you design your infrastructure. When you change something or customize a few things, it is hard to get support because the issue can be from either side. When you have a critical issue, which is not straightforward, you have to go between two different vendors, and they start finger-pointing to each other. They say that the issue is not at their end, and there is nothing wrong with their configuration. The issue is because of storage or network. These are the few things for which you have to fight for support. I don't know how they will improve this. It only happens sometimes for an on-premise solution. We don't run into those issues on the cloud because it is their own setup.
A cloud solution is pretty much on their site. They are managing the infrastructure, so they have to provide the solution, and they are good at it, but when you have on-premise, you decide what storage to use. Sometimes, you ignore Microsoft's recommendation, and you don't want to use what they are suggesting. When we run into issues on the DB side or the application side, they can point out to different vendors or causes for issues.
Which solution did I use previously and why did I switch?
We also have Oracle, Db2, and MongoDB databases here. We also have some NoSQL apps, but comparatively, SQL Server has a bigger footprint, and it is better than the others.
Other systems are more complex to configure. When you configure a cluster on the SQL itself, it is easy to configure because you've got more resources, whereas, when you have to configure Oracle or Db2, you have to have a SPEC process because they have to configure that on Red Hat Linux or Unix side. A few companies don't have special admins for Linux because the footprint is not that big. You might have two or three applications running on that system. When you run into a problem, you need to hire someone who can implement it for you, whereas most of the companies, almost 80%, are Microsoft shops. They already have the talent and resources available. You also have offline help and support. You have a lot of blogs or online help available when it comes to Microsoft, but when you go to other solutions like Oracle, sometimes it is a challenge. You really need the right person there, and not everyone will be able to do it.
The capability of a solution also depends on your needs and configuration. If you configure things wrong, any system will fail. When I'm testing something, I always believe in the functionality because Microsoft and Oracle test their products thoroughly. I never question their functionality, but we also check it according to our plan. You have to customize things based on your needs. If you're not getting the results, you have to consult the tech support and bring them in to configure it. These are the things that you run into when you are in your own data center. If you are not getting the throughput from the storage itself, you need to get the storage admin or storage vendor in there. When you move to the cloud, everything is taken care of.
How was the initial setup?
It is straightforward. There is no complexity. It is all automated, and we do un-attended install. We are not sitting and doing it. We just include it with the server build itself. When the server is built, we provide them the un-attended scripts to run, and everything is configured. They can use the media provided by Microsoft. Everything is done in one step. We just need to do auditing. We need to check at the right place, and we just keep checking it.
What's my experience with pricing, setup cost, and licensing?
Cost is a major derivative for any organization. It has a reasonable cost value, and its cloud support is also better than others. Comparatively, Oracle can do the same things or is even better in certain areas, but it is expensive. The cost along with the support are the plus factors for SQL Server.
What other advice do I have?
You need to know the concepts and the business logic before using this solution. It is not straightforward. You need to know what your application needs are and only then you can work on it. You also need to know about the product and how it works.
I would probably advise others to move to the cloud version, which is a modern database. If you want to use SQL Server, Azure is the best because you get the hybrid benefits. You can bring your own license, and you can save costs. You can save 55% of the cost. With AWS, you have to buy your license, which makes it expensive. If you are using SQL Server and your company is more on the Microsoft side, Azure is easier, and there is no change in it. You can also get more out of it. You don't have to put a lot of complexity in supporting or administrating it because Microsoft does that for you behind the scenes. Therefore, it is good to move to Azure SQL or to manage instances where you have more control. Both of these are PaaS solutions. There is no need to go into IES. It is better to stay on-premise than on IES because it creates more complexity. This is because you still have to build the servers, and you have to still manage them. If your application is compatible to be used with PostgreSQL or MySQL, you can also move there.
It also depends on the kind of talent you have in your company. You have to consider the talent that you have. You can choose other technologies, but you need support from your teams. If they're .NET developers and you have to build the knowledge base, it is smoother to stay with SQL Server because you have to change less on the coding side.
I would rate SQL Server a ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Development Associate & Manager at a educational organization with 501-1,000 employees
Offers good performance, but scalability feature needs to improve
Pros and Cons
- "The solution can be deployed in a few minutes."
- "There are certain shortcomings in the scalability of the product, making it an area where improvements are required."
What needs improvement?
There are certain shortcomings in the scalability of the product, making it an area where improvements are required.
From an improvement perspective, the price of the product needs to be reduced.
For how long have I used the solution?
I have been using SQL Server for more than ten years. My company is a gold partner of Microsoft.
What do I think about the stability of the solution?
It is a stable solution. Stability-wise, I rate the solution a seven or eight out of ten.
What do I think about the scalability of the solution?
It is quite a scalable solution. Scalability-wise, I rate the solution a seven out of ten.
My company's clients who use the solution are mostly enterprise businesses.
How are customer service and support?
I rate the technical support a seven out of ten.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I am using Amazon Cognito for the first time in my company.
What was our ROI?
I rate the product's initial setup phase a seven to eight on a scale of one to ten, where one is difficult, and ten is easy.
The solution is deployed on the cloud and on-premises models.
The solution can be deployed in a few minutes.
What's my experience with pricing, setup cost, and licensing?
The product is expensive.
What other advice do I have?
In our company's daily operations, we use SQL Server for our enterprise applications.
Speaking about how SQL Server played a critical role in a recent project, I would say that in my company, we used it for full management since we had a three-tier architecture and an enterprise application.
SQL Server was beneficial for data management needs, considering the fact that it was used as a part of SSIS packages, which was helpful for importing the data from legacy software.
The performance of the solution was good.
Though I can't elaborate on the valuable security features, I can say that I did not face any security concerns when using the product.
In SQL Server, I manage data recovery and backup with the help of database mirroring.
I recommend the product to those who plan to use it since it is easy to use.
I rate the tool 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
IT Cybersecurity and Compliance Coordinator at Plaenge
Exceptional performance and robust stability, ensuring a highly secure environment
Pros and Cons
- "The most valuable feature of SQL Server is that it is easy to set up."
- "There is room for improvement in terms of pricing for SQL Server."
What is our primary use case?
I use SQL Server for my SharePoint environment.
How has it helped my organization?
It offers exceptional performance and robust stability, ensuring a highly secure environment.
What is most valuable?
The most valuable feature of SQL Server is that it is easy to set up.
What needs improvement?
There is room for improvement in terms of pricing for SQL Server.
For how long have I used the solution?
I have been working with SQL Server for ten years.
I am working on the most updated version.
What do I think about the stability of the solution?
I would rate the stability a nine out of ten.
What do I think about the scalability of the solution?
I would rate the scalability a nine out of ten.
I plan to increase my usage in the future.
How are customer service and support?
I would rate the technical support a ten out of ten.
How was the initial setup?
The initial setup is straightforward.
It is easy to install.
What was our ROI?
There is a return on investment. The cost benefits are good.
What's my experience with pricing, setup cost, and licensing?
The cost associated with SQL Servers is on the higher side.
Which other solutions did I evaluate?
While there are other options available such as Oracle Database, Firebird, and MySQL, we specifically chose SQL Server to fulfill our needs for Microsoft services.
We opted for SQL Server as our scalable server solution to meet the requirements of our Microsoft services.
What other advice do I have?
It's a good solution.
I would rate SQL Server a nine out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
A stable tool for any company that has got a Microsoft stack
Pros and Cons
- "I would say that it is a stable product."
- "I would say that people should know how to get a SQL setup in place since it might be an area where they lack when it comes to the solution."
What is our primary use case?
We use the solution to provide the database layer for multiple applications.
For how long have I used the solution?
We have been using this solution for 10+ years.
What do I think about the stability of the solution?
I have had issues with SQL Server but Microsoft support has been able to resolve them quickly and most came down to configuration/design errors and not a stability of the product issue.
How was the initial setup?
SQL Server is quick to install < an hour. Additional features increase the installation time.
What's my experience with pricing, setup cost, and licensing?
The SQL Server pricing model is based on CPU cores that your database server utilises.
What other advice do I have?
To others looking into using a SQL Server, I would say that it goes down to the application that you are developing and what funds you have available to run the total system.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Easy to set up, fairly cost-effective, and scales well
Pros and Cons
- "There is a lot of information about the solution readily available online."
- "Technical support could be better."
What is our primary use case?
We're primarily using the solution for our health record system.
How has it helped my organization?
The use of a solution with SQL Server has helped standardize how we import, store, and report data. It is a standard that many applications use so we are able to buy pre-made solutions instead of having to develop a solution and the data can be moved from application to application easily.
What is most valuable?
The solution comes at a more effective price than Oracle.
It's a little bit more advanced than using MySQL or NoSQL.
It's more prevalent in the industry than SQL Postgre.
The initial setup is mostly straightforward.
The product is scalable.
The stability has been mostly pretty good.
There is a lot of information about the solution readily available online.
What needs improvement?
Every time Microsoft comes out with a new version, they like to move everything around. Updates are a bit intrusive. For example, it used to be in a certain place and then they update it, and now I can't find it.
Technical support could be better.
For how long have I used the solution?
I have been using SQL Server since version 6.4. I have used it with several different companies and help upgrade several versions.
What do I think about the stability of the solution?
With the versions we have, the solution is quite stable. That's one of the reasons we don't immediately download the latest version. We wait a little bit before we go to the newest version. We want to make sure it's very stable beforehand.
What do I think about the scalability of the solution?
The solution is very easy to scale. We have between 300 to 500 people that use it.
How are customer service and support?
Microsoft's tech support is really hard to use. I would rather look outside of Microsoft for solutions. When needed we usually pay the one-time fee but only in rare instances where a deep dive is needed to isolate the issue.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
SQL's been the main solution for this company. I have, however, used Oracle in the past with other companies.
How was the initial setup?
The initial setup is pretty straightforward.
It can be complex depending on what you're trying to do, however, it has a good user base and user support groups, so there's lots of information. If you're trying to do something, likely somebody else has already done it, and you can usually find that information through a user group or a forum, or even on YouTube or Google.
What about the implementation team?
Implementation was a joint effort with our team and the vendor team. Most of the vendor team was India based and was very low-level for best practices and security. We had to clean up a bunch of their generic implementations and correct code.
What was our ROI?
That is a complex question since there are too many variables that are outside the range of IT to answer.
What's my experience with pricing, setup cost, and licensing?
The pricing is pretty decent. It's less expensive than Oracle.
While the solution started out really reasonable, it's gotten a little bit more pricey, as Microsoft keeps changing how they want to license it.
Whether you're using it in the cloud or on-premise changes the costs involved. A lot of times it might be more cost-effective to do it in the cloud. Microsoft includes a lot of the licensing in the cloud.
Which other solutions did I evaluate?
The evaluation was based more on the applications and the solution that the business unit wanted to use which are easier to support if they all use the same database structure. The most common was SQL Server.
What other advice do I have?
We're just a customer and end-user.
We're not using the latest version. We're probably one or two versions behind.
I'd advise new users that you want to know what you're going to use it for. I would say it's more suited to a more midsize or larger company than a mom-and-pop shop - unless they're tying it to some software that uses SQL.
I'd rate the solution at 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.
Sr. Training Manager with 201-500 employees
Stores all of our data, and there is nothing that it can't do
Pros and Cons
- "I've been using SQL Server for 20 years, and there is nothing that it can't do. It is awesome."
- "When we are talking about event space architecture, scalability generally comes into play. For example, I might have a hundred thousand transactions a second, and then all of a sudden, I build something that everybody in the world wants. The next thing I know is that I have a million transactions a second. So, to be able to process the throughput, I'd have to scale up, and then when the holidays are over, I'm again down to a hundred thousand transactions, and I want to scale back down. SQL Server is not going to do that. In this way, it is not very scalable. One of the reasons why they want us to use Kafka is so that if we need to, we can do that, but our base program is on SQL Server. So, this is where we would use a Kafka event stack so that if I need more servers, I can just write a command, and I can have more consumers, more brokers, and more producers, and when the holiday season is over, it scales right back down again. SQL Server is not going to do that."
What is our primary use case?
It has all of our data. Our company sells contracts when you buy a car. We sell aftermarket insurance for the tyre, wheel, ding, dent, windshield, etc. When somebody buys a contract, we capture all of that data into a legacy database PostgreSQL, and my task is to incorporate that into our financial platform using T-SQL. So, I write queries, procedures, and views. I use SSIS, and I use SSRS. My job is to get the data into our financial system so that we can process claims, payments, cancellations, and refunds.
In terms of its version, we're up-to-date. We have version 2019.
How has it helped my organization?
This is the heart of the whole company. SQL Server is where all of our financials are. It has all of our data.
What is most valuable?
I've been using SQL Server for 20 years, and there is nothing that it can't do. It is awesome.
What needs improvement?
When we are talking about event space architecture, scalability generally comes into play. For example, I might have a hundred thousand transactions a second, and then all of a sudden, I build something that everybody in the world wants. The next thing I know is that I have a million transactions a second. So, to be able to process the throughput, I'd have to scale up, and then when the holidays are over, I'm again down to a hundred thousand transactions, and I want to scale back down. SQL Server is not going to do that. In this way, it is not very scalable. One of the reasons why they want us to use Kafka is so that if we need to, we can do that, but our base program is on SQL Server. So, this is where we would use a Kafka event stack so that if I need more servers, I can just write a command, and I can have more consumers, more brokers, and more producers, and when the holiday season is over, it scales right back down again. SQL Server is not going to do that.
For how long have I used the solution?
I have been using this solution for 20 years.
What do I think about the stability of the solution?
We do clustering. If one SQL Server goes down, it automatically goes to another one.
How are customer service and support?
I don't ever need tech support. If it breaks, I can just rebuild it.
Which solution did I use previously and why did I switch?
They're now using a different database for contracting called Road Runner. I don't know what that is, and how it stores data. I don't know anything about it.
There is also Postgres. I like SQL Server more than Postgres. That's only because I know SQL Server. I don't know Postgres as well. So, I can't say which one is better because I don't have the same amount of experience in both.
How was the initial setup?
I can bring up a SQL Server in an hour or so and set it up.
In terms of maintenance, the number of people required depends on the need.
We have a team of DBAs, developers, and UA analysts. We probably have 40 people in our IT area who are maintaining our solution. I'm just the developer. I'm the guy who makes the magic happen, but without other people collecting the information that I need to make the magic happen, I'm stuck. Without the guy who is an expert in permissions, partitioning, and performance tuning, I'm stuck. So, it's definitely a team effort. You can do it all, but you don't want to do it all because then you're running your head off, and you don't really get good at anything. It would be a jack of all trades, master of none type of scenario.
What other advice do I have?
You will seldom find a database that was designed correctly. Just because you got a poor-quality database doesn't mean that you're going to get a better database anywhere else. You rarely get to build a thing on your own. Usually, you inherit somebody else's stuff. So, the challenging thing is working with what you have while trying to implement a better solution. My only advice is to be patient.
I would rate it a nine out of 10. I wouldn't give anything a 10 because I don't have that kind of knowledge, but right now, it does what I need it to do.
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: August 2025
Product Categories
Relational Databases ToolsPopular Comparisons
Teradata
MySQL
Oracle Database
SAP HANA
MariaDB
IBM Db2 Database
CockroachDB
Amazon Aurora
LocalDB
Citus Data
Oracle Database In-Memory
IBM Informix
YugabyteDB
SAP IQ
Tibero
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?