We just raised a $30M Series A: Read our story
NS
Network Engineer at a pharma/biotech company with 1,001-5,000 employees
Real User
Top 5Leaderboard
An easy initial setup with good pricing and good stability

Pros and Cons

  • "The pricing of the product is very good."
  • "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: I am a real user, and this review is based on my own experience and opinions.
RN
Manager at a pharma/biotech company with 10,001+ employees
Real User
Top 10
Feature-rich, stable, scalable, and easy to install

Pros and Cons

  • "There is no lack of features."
  • "The agility of the non-SQL-based features is relevant on the market."

What is our primary use case?

We have hundreds of databases that are using SEL Server and there may be other capabilities.

What is most valuable?

It's a standard product that is used with standard applications, which is why we use it.

There is no lack of features.

What needs improvement?

There are newer models that are available on the market. The agility of the non-SQL-based features is relevant on the market.

Integration is one thing but it's making use of all the iterations or the new cloud data result.

Today's architectures are in many different directions. Not always via SQL relational databases, but also NoSQL databases, and they have a pretty good Java database as well.

For how long have I used the solution?

We have been using SQL Server in our organization for 10 years, but I am not a day-to-day user.

We use a couple of the versions. We have used the 2016 version and most likely have used some newer versions as well.

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 don't have any issues with the scalability of SQL Server.

We have hundreds of thousands of applications using this solution.

How are customer service and technical support?

We have a dedicated Microsoft account team and we have also dedicated support conditions.

Which solution did I use previously and why did I switch?

Areas in our organization use AWS Lambda.

We use other relational databases. The most important product besides SQL Server is Oracle. We use SQL Server and Oracle equally.

How was the initial setup?

I am not a patient person with installations, but there are no issues with the installation of this solution.

We have a database team to maintain this solution along with an engineering team, an operational team and we have eternal resources.

What's my experience with pricing, setup cost, and licensing?

The enterprise-level license agreement is very complicated. It's complex, not only with SQL server but with a number of products.

What other advice do I have?

I would recommend this solution to others.

I would rate SQL Server an eight out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: November 2021.
555,139 professionals have used our research since 2012.
ITCS user
CTO at a tech services company with 11-50 employees
Real User
Top 5Leaderboard
Reliable and easy to use with good technical support

Pros and Cons

  • "The solution is very common. It's easy to use."
  • "The solution is expensive. The licensing costs are high."

What is our primary use case?

The solution is primarily used as a relational database. It's a great option for anyone who needs to still use a database.

What is most valuable?

The solution is very common. It's easy to use.

The product offers a lot of support. Technical support has been great.

It's a reliable solution currently in this space.

The solution doesn't take a long time to set up. It's pretty straightforward. 

What needs improvement?

The solution is expensive. The licensing costs are high. 

For how long have I used the solution?

I've been dealing with the solution for 20 years or so. It's been two decades. I've used it for a while. 

What do I think about the stability of the solution?

The stability is pretty good. I find it to be reliable. There are no bugs or glitches. It doesn't crash or freeze. The performance is good.

What do I think about the scalability of the solution?

We have 150 users on the solution currently.

How are customer service and technical support?

I've contacted Microsoft technical support in the past and have been satisfied with the level of service I get. They're good.

How was the initial setup?

We have a special database team that is running. Except for the initial installation of the hardware, they are doing everything as it's an in-house solution.

It took a day or two to implement. It might have even taken less time. 

What about the implementation team?

We have a team that can manage the implementation process. 

What's my experience with pricing, setup cost, and licensing?

The licensing is a bit expensive. We'd like them to be more flexible in terms of costs.

We pay a yearly licensing fee.

Which other solutions did I evaluate?

We did not evaluate other solutions before implementing this solution. 

What other advice do I have?

I'm using either the 2018 or 2019 version of the solution. I don' know the exact number off-hand.

I'd rate the solution at an eight out of ten. It's a very good solution and I've been pretty happy with its capabilities. 

I would recommend the solution to other users.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
VP
Chief Information Officer at a financial services firm with 501-1,000 employees
Real User
Good SSMS and profiling tools that work well for internal applications

Pros and Cons

  • "I like that the new version has a memory-optimized table to improve the performance."
  • "I would like to see the performance improved. Migrating should be easier and the scalability needs improvement."

What is our primary use case?

We use SQL Server for our internal applications.

What is most valuable?

Working with SQL Server, it is quite convenient to use the SSMS tools to write a profile. I also like the profiling tools.

I like that the new version has a memory-optimized table to improve the performance.

What needs improvement?

We had some difficulty doing the performance tuning when we migrated from the 2008 version to the 2016 version. We experienced a drop in the performance. We could not understand or figure out what caused the drop in performance. We did not change any settings to cause this effect. We tried to keep the same settings.

We feel that when running the 2008 version, it was much quicker in terms of performance. 

That is an area of SQL Server that can be improved. Moving to a new version, you shouldn't have to change the configuration.

We have not been able to utilize it fully because it is not straightforward.

I would like to see the performance improved. Migrating should be easier and the scalability needs improvement.

For how long have I used the solution?

I have been using this solution for many years. 

We are using version 2016.

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?

In terms of scalability, it has some room for improvement.

We have 20 people in our organization who are using this solution.

How are customer service and technical support?

We don't usually get support from Microsoft. We get it from our software vendors or we try to do it ourselves.

We are somewhat satisfied with the support that we have received from the vendor, but not fully because of the issue we faced when we moved to a newer version. But in other areas, it's okay.

Which solution did I use previously and why did I switch?

We have used SQL Server from the beginning.

How was the initial setup?

The initial setup was moderate. It was not easy but it was not difficult.

What other advice do I have?

I would rate SQL Server 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.
OmidKoushki
Solution Architect at KIAN company
Real User
Top 5Leaderboard
Highly scalable, easy to use, but better performance and monitoring needed

Pros and Cons

  • "The solution is very easy to use."
  • "SQL Server needs to improve in performance and monitoring because there are no specific monitoring solutions to detect and analyze events for issues in the database. You have to use another monitoring solution. If Microsoft could provide an update to this solution or provide a monitoring solution specifically for SQL Server, it would be very valuable."

What is our primary use case?

I have been working on SQL Server for installations, configuring for developers, and for creating backup jobs from the MBF files.

What is most valuable?

The solution is very easy to use.

What needs improvement?

SQL Server needs to improve in performance and monitoring because there are no specific monitoring solutions to detect and analyze events for issues in the database. You have to use another monitoring solution. If Microsoft could provide an update to this solution or provide a monitoring solution specifically for SQL Server, it would be very valuable.

For how long have I used the solution?

I have been using this solution for approximately three years.

What do I think about the stability of the solution?

I have found the SQL Server stable.

What do I think about the scalability of the solution?

The solution is highly scalable. You are able to implement a SQL cluster mechanism for replicating the data between two nodes of the SQL Server. If one of the nodes is down the second node becomes active.

We have approximately 20 developers working directly with SQL Server and approximately 1,000 end-users that are working on the application that is behind the SQL Server.

How are customer service and technical support?

The technical support is good. We had a big problem and after an investigation, we could not find the solution. We needed to make use of Microsoft support team and open a specific case on the Microsoft panel. They were able to provide solutions for solving this issue.

Which solution did I use previously and why did I switch?

I have used MySQL.

How was the initial setup?

The installation is not very complex. However, the process could take a long time because you have to follow the step-by-step instructions for the installation. The time it takes to do the installation is approximately two days.

What's my experience with pricing, setup cost, and licensing?

There is a license required for this solution. One of the problems is for smaller businesses to purchases a license because it is expensive for a lot of them to afford.

What other advice do I have?

I would recommend this solution to others.

I 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.
Flag as inappropriate
RP
Project manager at a tech services company with 11-50 employees
Real User
A good choice in terms of price and quality, good speed, and good user interface

Pros and Cons

  • "Its speed and the ease of server management are valuable. If I compare Microsoft SQL Server to MySQL, what I like in Microsoft SQL Server is the speed. We are using Microsoft Management Studio for managing our Microsoft SQL Server, and the user interface that I get to work with is also better."
  • "There should be more tools and documentation for tuning the performance of Microsoft SQL Server. It would be nice to have more tools for tuning because currently, all the tuning that we have to do with our databases is almost manual. We have to read a bunch of knowledge base articles, and this information should be better documented. Its free text search should also be improved. It is quite important for us. Currently, we're developing our own free text search because of the lacking flexibility in Microsoft SQL Server. Therefore, we're kind of using elastic search and making different implementations in order to reach our targets. Using just the native free text search of Microsoft SQL Server is not enough for us. It should have more flexible features as compared to the current version."

What is most valuable?

Its speed and the ease of server management are valuable. If I compare Microsoft SQL Server to MySQL, what I like in Microsoft SQL Server is the speed. We are using Microsoft Management Studio for managing our Microsoft SQL Server, and the user interface that I get to work with is also better.

What needs improvement?

There should be more tools and documentation for tuning the performance of Microsoft SQL Server. It would be nice to have more tools for tuning because currently, all the tuning that we have to do with our databases is almost manual. We have to read a bunch of knowledge base articles, and this information should be better documented.

Its free text search should also be improved. It is quite important for us. Currently, we're developing our own free text search because of the lacking flexibility in Microsoft SQL Server. Therefore, we're kind of using elastic search and making different implementations in order to reach our targets. Using just the native free text search of Microsoft SQL Server is not enough for us. It should have more flexible features as compared to the current version.

For how long have I used the solution?

I have been using this solution for more than 15 years. Our clients are using its multiple versions, starting from SQL Server 2012.

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

In general, it is scalable, but we are only using the single-server mode. We are not using any kind of clustering. Therefore, I cannot say anything from my personal experience about the scalability of Microsoft SQL Server.

How are customer service and technical support?

I do not have any experience with Microsoft support. We either use in-house knowledge professionals or third-parties for consulting services.

How was the initial setup?

Its initial setup is quite straightforward. A major upgrade is a bit more complicated. We had some issues with the upgrade.

What other advice do I have?

I would recommend this solution. It is a good choice in terms of price and quality.

I would rate Microsoft SQL Server an eight out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
SS
Founder and Managing Director at a tech services company with 11-50 employees
Real User
Top 10
Feature-rich databases and user-friendly interface

Pros and Cons

  • "SQL Server's Management Studio is very user friendly. I like their database and the additional features it offers. It's also easy to integrate SQL Server with things like CLR, PowerShell, and command shell"
  • "I would like to see SQL Server add the ability to write to multiple sites or support replication between multiple sites at the transaction level."

What is our primary use case?

SQL Server can be useful for a lot of businesses and enterprise solutions. SQL Server is very powerful and useful when you need to store, retrieve, process, and analyze a large amount of data. In my organization, almost everyone uses SQL Server. That's about 10 people using it.

What is most valuable?

SQL Server's Management Studio is very user-friendly. I like their database and the additional features it offers. It's also easy to integrate SQL Server with things like CLR, PowerShell, and command shell

What needs improvement?

I would like to see SQL Server add the ability to write to multiple sites or support replication between multiple sites at the transaction level. If we can have data available on multiple sites as quickly as possible, that would be a great feature.

For how long have I used the solution?

I've been using SQL Server for around 10 years. I have 30 years of experience in the IT industry. In that time, I have worked on different kinds of databases, such as Oracle. Before that, I worked on FoxPro. I have also worked with PostgreSQL.

What do I think about the scalability of the solution?

It's absolutely scalable. 

How are customer service and technical support?

Our clients are the end-users of the SQL Server applications, and we do all the development and maintenance for them. So anything related to support, our clients take care of it.

How was the initial setup?

I work on the development and performance-tuning side, so I don't do the installation but my guess would be that it is pretty straightforward by now. 

What's my experience with pricing, setup cost, and licensing?

I am not aware of the cost because our clients take care of them, but I think there are enterprise licenses. If you go for Azure Cloud databases, then you just can pay as you go.

What other advice do I have?

SQL Server is my favorite database. Because I've been working on it for so many years, I like it. I have only good things to say about it. I would rate SQL Server nine 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: Partner
Flag as inappropriate
KH
Data Solution Architect at a comms service provider with 1,001-5,000 employees
Real User
Top 5Leaderboard
Easy to manage, stable and scalable, and has backup and recovery tools

Pros and Cons

  • "It is easy to manage for the administrator. It is also easy to use for applications that are Windows-based. It is a very stable product, and it has got backup and recovery tools."
  • "Its security can be improved. When you look at the Windows environment, it isn't the most secure environment. It is exposed to so many attacks. They continuously need to improve the security of the platform on which it sits."

What is our primary use case?

SQL Server is used as database software. People who are using .NET and Windows-oriented tools prefer SQL Server.

What is most valuable?

It is easy to manage for the administrator. It is also easy to use for applications that are Windows-based.

It is a very stable product, and it has got backup and recovery tools.

What needs improvement?

Its security can be improved. When you look at the Windows environment, it isn't the most secure environment. It is exposed to so many attacks. They continuously need to improve the security of the platform on which it sits.

For how long have I used the solution?

I have been using this solution for more than ten years.

What do I think about the stability of the solution?

It is very stable.

What do I think about the scalability of the solution?

It is pretty scalable. You can scale your machine and nodes. Instead of using just one node or one server, you can use multiple servers and then cluster them together for failover and performance. You can also do replication across sites. Currently, we have around 50 users.

How are customer service and technical support?

We have got support from Microsoft. They are very quick at resolving issues. They are quite good.

Which solution did I use previously and why did I switch?

We were using different products. 

How was the initial setup?

It is easy to install. It might take 20 or 30 minutes to install.

What about the implementation team?

I installed it myself.

What's my experience with pricing, setup cost, and licensing?

Its price is fine. You have to buy the license and support.

Which other solutions did I evaluate?

We compared it with Oracle and MySQL. We got a lot of dev inputs, and we also looked at the vendors supplying the solutions. We found SQL Server to be the best and chose it because of the vendor.

What other advice do I have?

I would recommend this solution to others. We would definitely keep on using this solution.

I would 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.
Flag as inappropriate