Principal Database And Cloud Architect at a financial services firm with 10,001+ employees
Real User
A relational database management system with a valuable developer edition, but the price could be better
Pros and Cons
  • "I love the developer version. Microsoft tells you about all the cool things they provided for everybody. You can develop and do anything with it. It's really good to learn. Oracle will not give you that much freedom, and Microsoft really kills it. You don't do anything with it but develop, learn, break, and push it to its limits. If there are problems, you show Microsoft or ask them, "what's going on here?" There is good community support for the developer edition, and that's what I really appreciate. You can teach people about it without limitations. You can have small databases created. You can keep it for a year and then work on it. It's a good thing for learners and developers."
  • "The price could be better. It costs a lot, and competing databases like Postgres are free."

What is most valuable?

I love the developer version. Microsoft tells you about all the cool things they provided for everybody. You can develop and do anything with it. It's really good to learn. Oracle will not give you that much freedom, and Microsoft really kills it. 

You don't do anything with it but develop, learn, break, and push it to its limits. If there are problems, you show Microsoft or ask them, "what's going on here?" There is good community support for the developer edition, and that's what I really appreciate. You can teach people about it without limitations. You can have small databases created. You can keep it for a year and then work on it. It's a good thing for learners and developers.

What needs improvement?

The price could be better. It costs a lot, and competing databases like Postgres are free.

For how long have I used the solution?

I have been using SQL Server for about ten years.

What do I think about the stability of the solution?

There are problems in all systems, and I don't see any difference between open source and proprietary solutions. SQL Server, Postgres, and Oracle are all vulnerable. There are no known issues per se, but any system can be broken. There is nothing special about this database.

Buyer's Guide
SQL Server
March 2024
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.

What do I think about the scalability of the solution?

SQL Servers and other databases are all scalable. I just don't see any problem with scalability.

How are customer service and support?

Whenever we have issues, we talk directly with Microsoft. They are responsive, and they help.

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

I'm more into open source solutions, and I love Postgres. I've worked as a database administrator as well. But I really hate all the tools used to manage performance or backup or just any of those disaster, recovery, and availability solutions. I hate them. They really impose a lot of overhead in a demonstration and aren't really flexible. When you're in the cloud, you don't have to worry about most of those things. 

Some of them still exist, but the cloud providers do provide them and you stick to that. You enhance them or add some more features, but really the most hated feature is, making sure that your database really can recover from many kinds of disasters. Resiliency, the most important part and when that is really managed by the cloud online, the overhead costs  are removed. The rest is really easy. Performance is okay, and there are indicated spots for data because I work with financial data and a lot of it is our important critical data. So, the cloud is really the best thing that happened to us.

How was the initial setup?

When it comes to the initial setup, most of them can be automated. For example, most setup settings for progressions, management, disaster and recovery, failover, and failback. Most of those things can be automated and provisioned into one kind of pipeline. Connecting that data to an application and even provisioning from the code repository through Jenkins. Those things are really easy to automate.

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

It costs a lot.

What other advice do I have?

I would advise potential users to use SQL Server with Microsoft Azure. I don't recommend managing it locally.

On a scale from one to ten, I would give SQL Server a seven.

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.
PeerSpot user
Information Systems Manager at a aerospace/defense firm with 51-200 employees
Real User
A scalable and easy-to-deploy solution that secures our data, saves time, and just runs
Pros and Cons
  • "The management studio is probably the thing we use the most for running quick queries and creating quick reports. Quite often, somebody comes and says, "Hey, can you find XYZ?" It is so much easier just to jump in there and run a quick query."
  • "They can build more performance-tuning tools in it. They can also make the stuff a little more user-friendly and provide the ability to schedule jobs. They can perhaps also streamline it a little bit so that it is not so resource-intensive, which would be helpful. SQL Server has a tendency to consume all the memory you allow it to. If you are not careful, you can basically break your server. I would like to see it having a smaller footprint in terms of system resource consumption. They might want to consider re-evaluating their pricing. It is expensive."

What is our primary use case?

It is used for the backend database for our ERP system and the document management system. We are using its latest version.

How has it helped my organization?

It saves time. Our data is also a lot more secure. Prior to SQL Server, things were run in a flat-file database that required a ton more maintenance to keep it running. SQL Server is pretty much bulletproof. It just runs.

What is most valuable?

The management studio is probably the thing we use the most for running quick queries and creating quick reports. Quite often, somebody comes and says, "Hey, can you find XYZ?" It is so much easier just to jump in there and run a quick query.

What needs improvement?

They can build more performance-tuning tools in it. They can also make the stuff a little more user-friendly and provide the ability to schedule jobs.

They can perhaps also streamline it a little bit so that it is not so resource-intensive, which would be helpful. SQL Server has a tendency to consume all the memory you allow it to. If you are not careful, you can basically break your server. I would like to see it having a smaller footprint in terms of system resource consumption. 

They might want to consider re-evaluating their pricing. It is expensive.

For how long have I used the solution?

I have been using this solution for 12 years.

What do I think about the stability of the solution?

It is pretty much bulletproof. We never had data corruption and database failure. We've had hardware failures, but that's not the fault of the software.

What do I think about the scalability of the solution?

It is very scalable, and you don't run into indexing issues like you would with a flat file. I don't think we've even scratched the surface in terms of its capabilities. Our databases are fairly small in comparison to others in our industry who are using the same software. 

We've got about 40 users using it, and primarily, they don't touch the database directly. They're just using it through ERP and our document management system. They are just non-IT employees. They are office users.

We're using it fairly extensively for the core of our business software, and we will likely increase the usage of it. We've got some projects in the hopper that will take advantage of SQL Server. So, we plan on increasing our usage of it.

How are customer service and technical support?

I didn't have the need to contact Microsoft support.

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

We haven't used any other solution prior to SQL Server. It was just a flat-file.

How was the initial setup?

It was pretty straightforward. It basically walks you through the process. It took a couple of hours.

What about the implementation team?

Initially, we used a consultant to set up our ERP system, but that was 12 years ago. Since then, we've upgraded it several times, and that was done in-house. Our experience with the consultant was overall positive.

For its maintenance, we are a department of two.

What was our ROI?

We have definitely seen a return on investment when it comes to SQL Server.

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

It is expensive, especially when you have open-source products that are just about as functional and they're free. They might want to consider re-evaluating their pricing.

We purchased it in retail. It was somewhere in the neighborhood of 9,000. There is just the standard licensing fee. If they migrate this product the way they're trying to do everything else, eventually, it is going to be subscription-based, which is going to suck, but that's the way the industry is going, so it is what it is.

What other advice do I have?

If you've never done it before, Microsoft has plenty of documentation and online guides to walk you through it. Just take your time, and follow the steps. If you can do it in a virtual environment, it is better because it is easier to start over if you mess it up, but it is fairly user-friendly. If you have questions during the setup, stop and Google it. The information is out there.

I would rate SQL Server an eight out of ten because there is always room for improvement.

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.
PeerSpot user
Buyer's Guide
SQL Server
March 2024
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.
Mohamed Abozied - PeerSpot reviewer
Network Administrator at Alsafy
Real User
Great for creating backups and databases but needs more security updates
Pros and Cons
  • "It's a very stable solution."
  • "There should be more security updates for the product."

What is our primary use case?

I use the SQL Server for backups and for creating databases and a lot of other stuff. I also use it to shrink data and some stuff like this. 

What is most valuable?

The solution is great for creating backups.

You can create databases using this product.

I like the way you can shrink the volume using SQL.

It's a very stable solution.

I've found the product to be able to scale well. 

What needs improvement?

There should be more security updates for the product. That would be ideal. 

For how long have I used the solution?

I've used the solution for about five or six years. I've used it for quite a while at this point. 

What do I think about the stability of the solution?

The stability of the product is great. There are no bugs or glitches. It doesn't crash or freeze. it's reliable. 

What do I think about the scalability of the solution?

So far, I have found the solution to be quite scalable. If a company needs to expand it out, it can do so. 

We have about 4,000 users on the solution currently. About five to seven different departments use it. 

How are customer service and support?

I don't directly deal with technical support. That would be handled by a different department and a person who is responsible for dealing with issues. Therefore, I can't speak to how helpful or responsive they would be. 

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

I did not use a different solution before using SQL. 

How was the initial setup?

It's easy for anyone to install. For me, it was good and easy to install. A company shouldn't have any issues tacking the process. 

The deployment is quick. It takes about 15 to 20 minutes. That's it. 

What about the implementation team?

I didn't need the assistance of consultants or integrators. It was something I could handle on my own. 

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

You can pay an annual or monthly licensing fee in order to use the solution. 

What other advice do I have?

I'd recommend the solution to others. It's very useful.

I'd rate the solution at 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.
PeerSpot user
Ariful Ambia - PeerSpot reviewer
Executive Director at a manufacturing company with 5,001-10,000 employees
Real User
Intuitive features, low maintenance, and reliable
Pros and Cons
  • "SQL Server is similar to other Microsoft products, such as BI, they are easy to use. You do not need to have an expensive BD to maintain them. All the useful intuitive features you find in Microsoft solutions you will find in SQL Server."
  • "Since this is a relational order system, scalability has a limit. If your system is very big, you need bigger servers and you have to spend more money. We scale a system up to a certain level, and then we move or shift data to the warehouse, which is NoSQL. We then do not have any bottleneck in scaling. For using this technique we are happy with it."

What is our primary use case?

We have a few transitional systems in our large company that we maintain with Microsoft SQL Server.

What is most valuable?

SQL Server is similar to other Microsoft products, such as BI, they are easy to use. You do not need to have an expensive BD to maintain them. All the useful intuitive features you find in Microsoft solutions you will find in SQL Server.

For how long have I used the solution?

I have used SQL Server within the past 12 months.

What do I think about the stability of the solution?

SQL Server is stable. However, every product has limitations. It is stable for a certain amount of workload. Beyond the capabilities of this solution, you will need other data solutions, such as Oracle. A solution that is more secure.

What do I think about the scalability of the solution?

Since this is a relational order system, scalability has a limit. If your system is very big, you need bigger servers and you have to spend more money. We scale a system up to a certain level, and then we move or shift data to the warehouse, which is NoSQL. We then do not have any bottleneck in scaling. For using this technique we are happy with it.

It is hard to tell or count how much data we are using because being one of the leading companies in Bangladesh, we have many teams who work on it. Different teams work on many different technologies.

We have not had an issue with the scalability SQL Server.

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

For databases, we have used a lot of data tests with other solutions, such as Oracle. We have used all Oracle data, Postgres, and a few others.

How was the initial setup?

The initial setup is very straightforward. You do not have to worry about the management of the SQL Server instance.

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

To scale the solution there are additional costs.

What other advice do I have?

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.
PeerSpot user
Karol Bura - PeerSpot reviewer
IT Manager at Drukarnia Interak sp. z o.o.
Real User
Top 20
Has good stability
Pros and Cons
  • "We're satisfied with the stability."
  • "We pay a license fee, it could always be cheaper."

What is our primary use case?

This is the main database for our financial system. I'm the IT manager and we are customers of SQL server. 

For how long have I used the solution?

We've been using this solution for many years.

What do I think about the stability of the solution?

We're satisfied with the stability.

What do I think about the scalability of the solution?

We have around 100 users. The database isn't used directly, so users are not even aware that there is a SQL Server underneath. 

How are customer service and support?

There are some local companies that have direct relations with Microsoft. We use them regularly when we need some support.

How was the initial setup?

I don't recall, it's been many years since we implemented this product. 

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

We pay a license fee, it could always be cheaper.

What other advice do I have?

I recommend this solution and rate it 10 out of 10. 

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.
PeerSpot user
Team Lead, Process Improvement at Fidelity Bank Plc
Real User
Easy to use, reliable and simple to set up
Pros and Cons
  • "Backups hardly get corrupt."
  • "The pricing could be more affordable."

What is our primary use case?

I use the client, however, I can also use the server, the Microsoft SQL Server Studio. I can use both, both the client and the studio.

We connected Automation Anywhere to the DB. Our reporting tool is also connected to that DB. Our financial application is also connected to the DB and some other databases too as well as some of our APIs.

What is most valuable?

I like the way it can manage the users from the security section where you can change their roles. 

SQL is simple to manage, as long as you know the script, and know the tables that you make reference to. If there are errors, you can easily debug them. 

You can easily debug and resolve your issues. 

The ease of backup, how you can back up and call up your backups too is great. Backups hardly get corrupt, except if maybe you have some bad hard drive clusters or bad hard drive sectors.

It is stable.

It's an easy-to-use product.

I find the solution to be scalable.

What needs improvement?

The pricing could be more affordable.

It's like to see less frequent updates. They should be once a month.

For how long have I used the solution?

I've been using SQL Server for a very long time.

What do I think about the stability of the solution?

The stability is great. It's very reliable. There are no bugs or glitches. It doesn't crash or freeze.

What do I think about the scalability of the solution?

The product scales well. If you need to expand it, you can.

We have around 50 users on the solution right now. 

How are customer service and support?

The solution is pretty problem-free and therefore it would be rare to have to reach out to support.

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

We've always used SQL. I also use SQLite.

How was the initial setup?

The initial setup is very simple, very straightforward. It's not too complex. 

The time it takes to set up isn't long. The time of installation is determined by the local system or the server where you are installing it to. That said, it's a light solution. For me, it took maybe ten minutes. 

We have eight people who are technical and can handle deployment or maintenance tasks. 

What about the implementation team?

I did the installation myself. It's not hard to do. You don't need a consultant or integrator.

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

We pay a monthly subscription fee. 

What other advice do I have?

I'm an end-user.

I would recommend the solution to other users and organizations.

Overall, I would rate it at a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Database Administration Team Leader at a transportation company with 10,001+ employees
Real User
A stable relational database management system with a valuable Always On feature
Pros and Cons
  • "I believe Always On is the most valuable feature. It's also easy to use and not very tricky."
  • "Analysis services have a lot of room for improvement. Basically, manageability on the available tools. They should have improved them already. They are not very efficient. My main headache is with the analysis service, and it would be really good if Microsoft developed some additional tools that are more user-friendly to manage the analysis. This is both from the perspective of management, users' roles, and performance analysis. My main wish for SQL Server would be that management tools for analysis services grow and mature a bit."

What is our primary use case?

We use it for both database services and analysis services.

What is most valuable?

I believe Always On is the most valuable feature. It's also easy to use and not very tricky.

What needs improvement?

Analysis services have a lot of room for improvement. Basically, manageability on the available tools. They should have improved them already. They are not very efficient. My main headache is with the analysis service, and it would be really good if Microsoft developed some additional tools that are more user-friendly to manage the analysis. This is both from the perspective of management, users' roles, and performance analysis. My main wish for SQL Server would be that management tools for analysis services grow and mature a bit.

For how long have I used the solution?

I have been using SQL Server for about 15 years.

What do I think about the stability of the solution?

It's stable. The database service is better than the analysis service, but it's quite stable. It's as stable as the support it has. If it has a good infrastructure and good machines with disks, it's quite stable.

What do I think about the scalability of the solution?

SQL Server is vertically scalable. We have about 3,000 people using this solution.

How are customer service and technical support?

We haven't used their technical support a lot. I would say it depends on the scope of the help you need. On a scale from one to ten, I would give technical support a seven.

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

I don't know the exact prices because my focus is essentially technical and not on the bills. A few years ago, they changed the billing policy for the Enterprise Edition, and it became less attractive. But I believe they are still cheaper than Oracle. SQL Server isn't cheap, but it's not expensive either. 

What other advice do I have?

I would tell potential users that it's important to have a good infrastructure, but my advice is for any database, not only SQL Server. It's important to have a good infrastructure and a good network if you're planning to use Always On and clusters. I believe the most important thing is the infrastructure where the SQL Server will be based.

On a scale from one to ten, I would give SQL Server an eight.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Enterprise Architect at a educational organization with 10,001+ employees
Real User
Easy to set up and use, and the technical support is good
Pros and Cons
  • "It is the latest technology and pretty powerful in terms of the high availability of the virtual server."
  • "We have had problems implementing a data warehouse using SQL Server."

What is our primary use case?

We use SQL Server for our application data.

As a government agency, all of our data is stored in our environment on-premises.

What is most valuable?

SQL Server is easier to use than Oracle, programming-wise.

It is the latest technology and pretty powerful in terms of the high availability of the virtual server.

What needs improvement?

We have had problems implementing a data warehouse using SQL Server. It may be because the data is too big, although it claims to be able to handle the amount of data that we have. Perhaps there are some technical issues because there is something weird going on. It cannot find the correct IP address.

For how long have I used the solution?

I have been using SQL Server for ten years.

What do I think about the stability of the solution?

This product is not quite as stable as Oracle. I would rate the stability as moderate and would not rate it ten out of ten.

What do I think about the scalability of the solution?

SQL Server claims to be good, scalability-wise, but we have had issues with it.

On the other hand, we have been using it for a lot of large applications and it has worked well in those cases. For the most part, it is good, and we have a lot of users.

How are customer service and technical support?

Microsoft technical support is good.

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

I also have experience with Oracle and I find that SQL Server is easier to work with, but it is not as powerful.

How was the initial setup?

Initially, it is easy to set up.

What other advice do I have?

My advice for anybody who is considering this product is that it is relatively easy to set up.

I would rate this solution 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.
PeerSpot user
Buyer's Guide
Download our free SQL Server Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2024
Product Categories
Relational Databases Tools
Buyer's Guide
Download our free SQL Server Report and get advice and tips from experienced pros sharing their opinions.