SQL Server is used for storing data.
System Architect, SCRUM Product Owner at a tech company with 10,001+ employees
Easy to use, scalable, and reliable
Pros and Cons
- "I have found SQL Server easy to use."
- "SQL Server could improve by having better usability or user guidance."
What is our primary use case?
What is most valuable?
I have found SQL Server easy to use.
What needs improvement?
SQL Server could improve by having better usability or user guidance.
For how long have I used the solution?
I have been using SQL Server for approximately five years.
Buyer's Guide
SQL Server
October 2024
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
816,562 professionals have used our research since 2012.
What do I think about the stability of the solution?
The solution is stable and the performance is good.
What do I think about the scalability of the solution?
SQL Server is scalable.
How are customer service and support?
I have not needed to contact support.
How was the initial setup?
The implementation was done by our IT department.
What about the implementation team?
We did the implementation in-house.
What's my experience with pricing, setup cost, and licensing?
The price of the solution is fine.
What other advice do I have?
I would recommend this solution to others.
I rate SQL Server an eight 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.
Principal, Sr. IT Consultant at a consultancy with 51-200 employees
It is fairly easy to work with
Pros and Cons
- "It is fairly easy to work with. I like the high-availability options, like mirroring for example, and the high-availability groups."
- "The Management Studio is a pretty heavy piece of software, and it's sometimes slow. I would recommend making an express version of the Management Studio, which is lighter and has fewer features but is a little faster."
What is our primary use case?
We set up SQL Servers for developers who develop applications for data mining. Our clients are generally small or medium-sized businesses. There's also a SQL Server Express that many software vendors use to support their applications. That gets installed often—usually as part of the application installation.
What is most valuable?
It is fairly easy to work with. I like the high-availability options, like mirroring for example, and the high-availability groups. It's quite an interesting feature that enables high availability for the SQL Server. I think it's important. So that's the feature that I'm particularly interested in and it works pretty well.
What needs improvement?
The Management Studio is a pretty heavy piece of software, and it's sometimes slow. I would recommend making an express version of the Management Studio, which is lighter and has fewer features but is a little faster.
For how long have I used the solution?
"Using" is the wrong word. We mostly set it up for others. The last time we set up an SQL Server for a client was about a year ago.
What do I think about the stability of the solution?
We haven't had any experiences. The software hasn't been unstable or glitchy in our environment so far.
What do I think about the scalability of the solution?
In terms of scalability, it would be closed to a high-availability group. So I would say it varies in scale.
What other advice do I have?
I would rate it nine out of 10. Nothing's perfect.
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
Buyer's Guide
SQL Server
October 2024
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
816,562 professionals have used our research since 2012.
Senior BI Consultant at a tech services company with 11-50 employees
Overall high quality features, reliable, and good technical support
Pros and Cons
- "I have found the whole solution with all its features wonderful."
- "If this solution could provide an automatic indexing feature it would be very useful."
What is our primary use case?
Our primary use case is for SQL Server is data warehousing and business intelligence.
How has it helped my organization?
This solution acts as the backbone of most IT services. It is essential for us to use it.
What is most valuable?
I have found the whole solution with all its features wonderful.
What needs improvement?
If this solution could provide an automatic indexing feature it would be very useful.
In the next release, there could be better integration with Power BI or other tools.
For how long have I used the solution?
I have been using this solution for approximately 20 years.
What do I think about the stability of the solution?
The solution is stable. There has been a few bugs but all solutions have them at one time or another.
What do I think about the scalability of the solution?
There are scalability limitations and this is why we are evaluating cloud alternatives.
I rate the scalability of SQL Server a four out of five.
How are customer service and technical support?
We provide support for our clients but if we need support we receive it quickly because we are prime customers.
Which other solutions did I evaluate?
We are currently evaluating cloud options.
What other advice do I have?
I would advise those wanting to implement this solution to thoroughly investigate if this is the right tool for their use case.
I rate SQL Server an eight 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
IT at a financial services firm with 201-500 employees
Enables a person to do whatever is required at the command line level
Pros and Cons
- "Since we can automate most of our tasks, it means that the management is very easy."
- "I would like to see the database become fully automated."
What is our primary use case?
Microsoft SQL Server is a database application, meaning it acts as the backend system for help with the backend data repository system. It concerns itself with every activity that happens at the front end of the database in Microsoft SQL Server. ERP Microsoft solutions is one reason that the SQL server has compatibility. The management of Microsoft SQL Server is actually quite easy. It has a GUI interface and enables a person to do whatever is required at the command line level. It functions as a repository for storing one's data in the relational database.
What needs improvement?
The Standard Edition and Enterprise Edition have certain limitations. While the latter is clearly more expensive than the former, it would be nice to see some of the features in the Enterprise Edition be moved to the Standard Edition. This will encourage many more people to use that solution.
If we were discussing the 2000 edition in respect of the SQL Server, I would probably cite security and performance as issues. However, nowadays, when it comes to an application connected to their databases, there is no real difference between MS SQL Server and Oracle. As a consequence, it would be nice to see the application be made more cost-effective. I am aware of much database self-management in respect of Oracle. I know that the last time a colleague of mine used this solution in California, he informed me that the application itself was managing the database.
At present, the solution uses the older connection and the schema is designed in such a way that it can actually provide a very low level of virtualization. Since the security is also hierarchical within the system, they've really done a very good job.
This said, I would like to see the database become fully automated.
For how long have I used the solution?
I have been using SQL server for a couple of years, since day one.
What do I think about the stability of the solution?
The solution is stable and it has remained so over the years. I've worked in different organizations, such as the banks here in Lagos. Straight off the bat, I've been using Microsoft SQL Server 2000. We currently use Microsoft SQL Server for our ERP needs. How one designs his tables is important. As the team leader, it is my job to ensure that the functioning is as it should be. The application is pretty straightforward.
Since we can automate most of our tasks, it means that the management is very easy. We can have jobs for our backups. The solution grants us the ability to perform database housekeeping tasks.
What do I think about the scalability of the solution?
The solution is very scalable.
How are customer service and technical support?
It's been fun dealing with technical support. Generally speaking, they have shown a willingness to handle issues we may have.
What other advice do I have?
The solution demonstrates performance and this is going well for the moment.
In consideration of its performance, I rate SQL server as a nine 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.
Technical Specialist at a media company with 10,001+ employees
Stable, intuitive, and easy to use for non-technical users
Pros and Cons
- "The solution is very easy to use. It's intuitive and easy to navigate. Overall, it's a straightforward product."
- "The documentation could be much better. It's lacking right now. If there are better help pages, for even complicated queries and stuff like that that would be quite a help for users."
What is our primary use case?
I primarily use it to extract some configuration information for my product - in order to understand how the configuration is done for my base product.
What is most valuable?
The solution is very easy to use. It's intuitive and easy to navigate. Overall, it's a straightforward product.
You don't really need a learning code to study MySQL. If you know the basics, it's quite easy to use the product. There isn't a high learning curve and you don't have to be overly technical.
The initial setup was straightforward.
What needs improvement?
The documentation could be much better. It's lacking right now. If there are better help pages, for even complicated queries and stuff like that that would be quite a help for users.
There were times where it was not working all the time, however, that could be due to some issues on our network side as well. I'm not really sure of that, and therefore can't blame the solution. However, I do remember experiences where, when I tried something, it didn't work.
For how long have I used the solution?
I've been dealing with the solution for seven years now. It's been a while.
What do I think about the stability of the solution?
For my purposes, I haven't had any issues with stability. I find it to be reliable in terms of performance. It doesn't crash or freeze. There are no bugs or glitches. It's good.
What do I think about the scalability of the solution?
I don't really use it heavily, basically, my usage is quite small. It's been okay for me for my purposes. However, it's my understanding that it can scale.
We have more than ten engineers that currently use the product regularly.
How are customer service and technical support?
I've never needed to reach out to technical support from Microsoft, I can't speak to how helpful or responsive they are. I don't have any direct experience I can draw from.
How was the initial setup?
The initial setup was not overly difficult or complex. It was quite straightforward. It's a pretty simple process.
Our team is capable of handling the maintenance internally.
What's my experience with pricing, setup cost, and licensing?
In terms of pricing, I just downloaded it and started using it. I don't have a lot of information on licensing. I can't speak to the costs.
What other advice do I have?
We are just a customer and an end-user. We do not have a business relationship with SQL.
I would recommend the solution to other users. So far, the experience I have had over the years has been a positive one.
I'd rate the solution at a nine 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.
Chief Technology Officer & Vice President, Delivery at a recruiting/HR firm with 1-10 employees
Very stable, easy to use, and easy to move data across versions, but needs better indexing, performance, scalability, and JSON support
Pros and Cons
- "It is easy to use and very stable."
- "Its support for JSON should be improved. It does support JSON, but the support is not good enough currently. They should also improve the way indexes work. Its performance can also be improved because sometimes it becomes very slow for certain table designs. It cannot have more than a certain amount of data. As compared to other databases, its capability to handle large volumes of data is not very good."
What is our primary use case?
We are a product-based company, and we use it as part of our product. It is deployed in a public cloud and on-premises.
How has it helped my organization?
We use it as part of our product, so it is helpful for us. It is easy to move data across versions, and it holds lots of our internal data for operations.
What is most valuable?
It is easy to use and very stable.
What needs improvement?
Its support for JSON should be improved. It does support JSON, but the support is not good enough currently.
They should also improve the way indexes work. Its performance can also be improved because sometimes it becomes very slow for certain table designs.
It cannot have more than a certain amount of data. As compared to other databases, its capability to handle large volumes of data is not very good.
For how long have I used the solution?
I have been using this solution for ten years.
What do I think about the stability of the solution?
It has been very stable. We had a very good experience with it.
What do I think about the scalability of the solution?
Scaling is a challenge because you cannot scale horizontally. We've run into a couple of scenarios where we were not able to scale it easily.
How are customer service and technical support?
Their support is quite satisfactory. They have not been perfect every time, but they have mostly been quite good. They're prompt, but they weren't able to resolve some of the issues.
How was the initial setup?
It is easy to install.
What about the implementation team?
Our IT team handles the installation.
What's my experience with pricing, setup cost, and licensing?
It is expensive.
What other advice do I have?
You should know its limitations. It cannot have more than a certain amount of data.
I would 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.
Database Operation Assistant Manager at a consumer goods company with 10,001+ employees
Plenty of features, flexible, but could be more scalable
Pros and Cons
- "I have found the most valuable features to be the flexibility and the vast amount of features available."
- "The scalability is adequate but could improve."
What is our primary use case?
I use the solution for analytics and reporting.
What is most valuable?
I have found the most valuable features to be the flexibility and the vast amount of features available.
For how long have I used the solution?
I have been using the solution for approximately three years.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The scalability is adequate but could improve. We have approximately 100 people using the solution in our company.
How was the initial setup?
The installation is not difficult, it is quick. It took approximately 15 minutes to complete.
What about the implementation team?
We have four technicians that do the deployment and maintenance of the solution.
What other advice do I have?
I recommend this solution to others.
I rate SQL Server a seven 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.
Consultant at Rpc Data
Easy to set up and configure, integrates well with other components, and the support is good
Pros and Cons
- "The most valuable feature is that it is easy to use and you don't have to do a lot of configuration."
- "More things in SQL Server need to be automated."
What is our primary use case?
We are a solution provider and this is one of the products that we implement for our clients.
It can be used for different things such as data warehousing and online transactional processing (OLTP). This is a product that I have never used in production, however.
What is most valuable?
The most valuable feature is that it is easy to use and you don't have to do a lot of configuration. For example, there is no installation.
When you want to insert data, it is easy to do. For example, if I want to test something then I log into my GitHub account, download what I want, and then upload it to the SQL server.
The integration with other products like SQL Developer is really good. Connecting it to Visual Studio is also quite good.
What needs improvement?
More things in SQL Server need to be automated. We need to do a lot of things, especially on the cloud, and Oracle has better automation for handling these kinds of tasks. Automation is the key, these days.
For how long have I used the solution?
I have been using SQL Server for a couple of months.
What do I think about the scalability of the solution?
With respect to scalability, I can say that the cloud version is scalable. I don't have much to say about how an on-premises deployment scales. However, in general, both Oracle and Microsoft products scale really well.
How are customer service and technical support?
Technical support is responsive and quite good.
Which solution did I use previously and why did I switch?
I also have experience with Oracle Database. When I compared pricing between the two products, I found that Microsoft was more expensive.
How was the initial setup?
There is no installation. Everything is done by Microsoft and all you have to do is deploy it. The process takes less than five minutes.
What about the implementation team?
I have done the installation many times by myself.
As a cloud-based product, there are no special resources required for maintenance. Once you deploy it, you just want to make sure that the data is displayed or presented in the way that you want it. Most of the technical work is handled by Microsoft.
What's my experience with pricing, setup cost, and licensing?
There is a charge for this product if you are using it in production. For development, there is no cost. The pricing from Microsoft is quite expensive compared to Oracle.
What other advice do I have?
In summary, this is a good product, I plan to continue using it, and I definitely recommend it.
I would rate this solution an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free SQL Server Report and get advice and tips from experienced pros
sharing their opinions.
Updated: October 2024
Product Categories
Relational Databases ToolsPopular Comparisons
MySQL
Oracle Database
Teradata
MariaDB
SAP HANA
IBM Db2 Database
Amazon Aurora
CockroachDB
LocalDB
IBM Informix
Oracle Database In-Memory
Citus Data
YugabyteDB
SAP IQ
SAP SQL Anywhere
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?