SQL Server Reviews

I use SQL Server for .NET. We have ERP software in the background and we use the SQL Server for its creation.

SQL Server and their offers are very good. You can switch over, export, and do other things. I got access from users and it is very flexible to use.

SQL Server is technically good. For questions or other queries, we go through the internet and they explain it there. I think the structure of their product is good.

I have been using SQL Server for one year and a month.

It's stable. It was very easy for me to handle it.

The free version of SQL Server is time-limited before updating to the paid version. So, sort of more access and more work in your database to help process most of the time. It's better to purchase it for more secure functions.

We have a technical support engineer who handles maintenance and security for SQL Server. I think Microsoft's technical support is also very good.

It's a straightforward installation. I installed SQL Server 2012, 2013 and 2016.

The usability of the free version is limited. They also have some guidelines on how to use the paid ones. You still have to check your IT requirements after purchasing it. We are using a licensed one right now, which has more functionality than the free version.

We use SQL Server for tuning data transactional language.

The product helps me tune the transactional language with the databases of our organization.

The product’s most valuable features are flexibility and scalability.

SQL Server could be more robust than Oracle.

I have been using SQL Server for ten years.

The product could be more stable than Oracle.

It is a scalable product.

The technical support services need improvement in terms of communication. It is difficult to understand the accents of the executives from different countries.

The initial setup is easy. The deployment services cost around $2000 to $3000.

SQL Server generates more return on investment than Oracle servers.

The product’s price depends on the specific server requirements.

I rate SQL Server an eight out of ten. It is easy to learn Microsoft products. There is a lot of information available about it on the internet.

We're primarily using the solution for our health record system.

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.

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.

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. 

I have been using SQL Server since version 6.4. I have used it with several different companies and help upgrade several versions.

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.

The solution is very easy to scale. We have between 300 to 500 people that use it. 

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.

Positive

SQL's been the main solution for this company. I have, however, used Oracle in the past with other companies.

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.

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.

That is a complex question since there are too many variables that are outside the range of IT to answer.

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.

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.

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.

Performance-wise, SQL cannot handle large amounts of data. In the next release, I would like them to commission SQL Server on Linux, as has been announced in the past but has not yet happened.

I've been using SQL Server for thirteen to fourteen years.

SQL is a highly unstable server - there are patch updates on the Windows server every week, which is why we only use it for non-critical systems. 

The initial setup was very easy - much, much easier than Oracle - and took about a day to complete. Microsoft is less demanding because everything is GUI, unlike Oracle, where you need to use command lines.

This is a very cheap product.

SQL's performance is good enough if you have a low amount of data. For those looking into implementing SQL Server, I would advise first analyzing your requirements and whether your system is critical or non-critical. If it is non-critical, go for SQL as it will save you in terms of cost, but if it is critical, avoid SQL as it will bring you down in one day. I would rate this solution as eight out of ten.

We use SQL Server as a database solution.

The performance of the SQL Server is very good.

I have been using SQL Server for a few years.

The stability is very good.

The solution is scalable. However, we do not have many large servers using SQL Server anymore, we have moved to SAP HANA.

We have approximately 2,000 users using this solution in my organization.

The support offered by Microsoft is very good. We have not faced any issues with SQL Server to need to contact their support.

We use SAP HANA as a database solution for certain use cases.

We have technical managers and engineers that do the maintenance and support for this solution.

We are on an annual enterprise license for the solution and the cost of the license could be reduced.

I rate SQL Server an eight out of ten.

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.

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. If we can have data available on multiple sites as quickly as possible, that would be a great feature.

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.

It's absolutely scalable. 

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.

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. 

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.

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.

The solution is an RDBMS and can be used to simplify customers' requirements for a back-end database. The main function of the solution is to store information from front-end users.

The most valuable feature of the solution, compared to other RDBMS solutions, such as Oracle MySQL or IBM DB2, it is more user-friendly and has backward compatibility. For example, if you have an application that requires an old version of SQL Server and you have the latest version of the license, you are able to install and use it in backward compatibility mode. They keep supporting the existing legacy application. Additionally, the solution is simple and if it is configured properly it performs very well. 

I have used the solution for approximately six years.

I find the solution to be very stable. 

The solution is scalable. 

The technical support is only provided to the customers having a subscription-based license with a Software Assurance server. For other forms of licensing the solution will not provide support. 

I have previously used other RDBMS solutions, such as Oracle MySQL, Maria DB, PostgreSQL, and IBM DB2.

When comparing PostgreSQL, Oracle MySQL, and Microsoft SQL, Microsoft SQL has an advantage over the other two server databases because it provides a graphical user interface by default.

The initial setup of the solution is very easy and the time it takes depends on the architecture required. If the deployment of a cluster is required then the setup may take up to three hours, whereas standard environment deployment needs half an hour. 

The solution can be installed by our selves but the use of an integrator makes it much easier. 

The solution requires authorization in either the form of perpetual licensing or subscription-based licenses for two years. If a perpetual license version is purchased then customers have it to the end of life, whereas a subscription-based called server with Software Assurance, has to be renewed every two years. 

The areas that need improvement are with regards to the commercial aspect of the solution, the licensing cost could be reduced in order to help customers to adopt it.

I would recommend this solution. However, the customer has to make sure it fits their use case.

I rate SQL Server a nine out of ten. 

We're using it for our on-premise servers, and we have the latest version of SQL Server.  

We use SQL Server for the database for Microsoft Navision. We also use it for the Track-It application that helps users in logging in their IT requests. We also manage all the IT inventory through Track-It. It does automatic auditing and traces online IT equipment.

We have end-computing devices with a server-client type of model. We have a server. All terminals are dumb terminals, but they get connectivity from SQL Server, and it has worked really well. We operate in difficult locations, such as Mombasa in Kenya and Mozambique in Maputo, where power is a big problem. Instead of desktop computers, we went for thin end-computing clients, and it worked really well with SQL Server.

It is a stable product, and it runs seamlessly. It is not complex.

It has been there for a long time, and they are doing whatever bug fixes they have to do. 

They have too many licensing options. They may want to simplify its licensing and bring it down to two, three, or four categories from ten to fifteen categories. Having so many different licensing options makes it difficult to decide which one to choose from. They can club things together. This is an area where they can make things easier for customers.

I have been using SQL Server for ten years.

It is a stable product.

It has pretty good scalability. In terms of usage, we have two different types of usage. For end-computing usage, we have about 600 or 700 students who use the media labs. For Microsoft Navision and Track-It, we have about 100 staff members as users. 

It is being used fairly extensively. Microsoft Navision is one of the core solutions of our business, and it is used on a daily basis. End computing is used by students. Because of the pandemic, for the last 14 months, everything is closed, and everybody is remote, so end computing has not been used, but Navision continued to be used. After the school reopens in each location, we will continue to use it even more. We definitely have plans for expansion.

Their response is fast.

Its initial setup is very straightforward. In case there is an issue, Microsoft's tech support people come online and help you.

For its deployment and maintenance, two people are required at each location. We have one database specialist and one IT service delivery engineer with networking knowledge.

It comes with the bundle package that we have. We have Microsoft Volume Licensing, so we don't have to pay for it separately. It is a part of the package.

I would definitely recommend this solution. I have nothing to complain about.

I would rate SQL Server a nine out of ten.