SQL Server Reviews

We use SQL Server as a database management system for all of our projects.

While this is a reliable product, it has room for improvement.

Although Microsoft SQL was accessible in some projects, we did not use it everywhere. It is determined by the project. It's quite beneficial in some circumstances, but it couldn't support SQL databases in others, consequently, we used other suppliers like Oracle, Informix DB, PostgreSQL, MySQL, and others.

We have been using SQL Server for quite some time now.

We use it both on-premises and in the cloud. It is dependent on the projects.

SQL Server is a stable solution.

SQL Server scales well.

In the future, we may expand our usage.

I don't have any issues with the technical support.

We evaluated each product after using it, starting with Informix DB and ending with Oracle.

Oracle, Informix DB, PostgreSQL, and MySQL are among the products we use.

It's quite easy to install.

Completing the installation is not an issue.

My position is not related to installation, but if it is necessary, I am capable of doing it.

It requires the purchase of a license. Our company's products all have licenses.

It is appropriate for small and medium-sized businesses.

I would recommend this solution to others.

I would rate SQL Server an eight out of ten.

We use a tool called Tosca for automation and all the automation artifacts we are saving are on the SQL Server.

The solution is easy to use and provides similar features to other competitors.

SQL Server could improve by increase the performance, it cannot handle large amounts of data. I did not find any additional features compared to others solutions.

I have been using this solution for a few years.

The solution is stable.

We have not scaled the solution extensively, but I do not foresee any problems.

We have been using Hadoop and Spark.

The installation and configuration are straightforward.

We have a team of three people doing the backend maintenance and application support for this solution.

We did not encounter any issues that we would need support. 

I would recommend this solution to others for small operations. For bigger applications with large amounts of data and a lot of users, I would not recommend it.

I rate SQL Server a six out of ten.

We primarily use the solution for recording transactions and information related to the reservation of a service. 

The product is very stable.

It offers very good documentation. When there are some little issues, it's always very easy to go into the documentation for troubleshooting purposes. There's just so much documentation on hand and a really great community around the product that is very helpful.

It's a very complete product.

We've found it to basically be pretty problem-free.

The integration with other products has always been quite good.

The security of the product has never given us any issues.

We're quite satisfied with the solution. There aren't any outstanding features we would like to add.

The interface could be updated to make it slightly more user-friendly.

We've been using the solution for more than ten years. It's been a while. It's been more than a decade at this point.

The solution is very stable. there are no bugs or glitches. It doesn't crash or freeze. it's excellent.

We haven't really scaled the solution all that much. At the moment, we have measured the scalability in a horizontal way. When we needed to have more installation and more capacity, we split the database into a different SQL Server instance.

In the future, we'll likely need to consider scalability more. We are also moving in the last two years, also to a different architecture from a monolithic to a more microservice architecture. Maybe the scalability can be more easily handled in the applications that are talking to each other and leaving the database out of the equation.

While end-users are hard to quantify, I can say that likely half a million users have come through our system for transactions.

In the near future, we will continue to use the solution. We might use it for the next four or five years, although it is hard to say.

We've always been able to rely on the fantastic documentation and great community around the product in order to troubleshoot problems. It's very easy to fix issues as they arise due to the public knowledge available to everyone.

We've mostly always used this solution. Last quarter, we moved a little bit to a NoSQL database. We have done a little experiment on Cassandra however, previously, it has always been on SQL Server.

We're considering moving away from the solution right now and trying something new. The owner of the company wants to experiment with other technologies and see what is out there, which is why there is talk of change. However, it's not a reflection on this product, which has been largely quite good.

The initial setup is not overly difficult. It's pretty straightforward. A company shouldn't have any issues with the process.

We have 12 technical people on our team that can handle the implementation.

The last version we used is 2015 if I'm not mistaken. We don't jump immediately to the latest version due to the fact that, usually, we look for stability. We make the move to the next version in case of some integration or limitation. We prefer not to move onto something that might have bugs or glitches that need to be patched. It's more secure for us that way. 

I'd recommend the solution to other companies.

I'd rate the solution at a ten out of ten. It's doing exactly what we need it to do. We've very happy with it.

• Effectiveness in a production environment
• New features test

Besides that, SQL Server has become very expensive like Oracle. Its stability delivers performance and usability.

• SSMS
• SSIS
• Reporting services
• FCI clustering
• AlwaysOn
• Basic availability groups.

I would like a mature real-monitoring built in into SSMS, even a trace file analyzer.

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. 

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.

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.

"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.

We haven't had any experiences. The software hasn't been unstable or glitchy in our environment so far.

In terms of scalability, it would be closed to a high-availability group. So I would say it varies in scale. 

I would rate it nine out of 10. Nothing's perfect.

Our primary use case is for SQL Server is data warehousing and business intelligence.

This solution acts as the backbone of most IT services. It is essential for us to use it.

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.

In the next release, there could be better integration with Power BI or other tools.

I have been using this solution for approximately 20 years.

The solution is stable. There has been a few bugs but all solutions have them at one time or another.

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.

We provide support for our clients but if we need support we receive it quickly because we are prime customers.

We are currently evaluating cloud options.

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.

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. 

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.

I have been using SQL server for a couple of years, since day one. 

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.

The solution is very scalable.

It's been fun dealing with technical support. Generally speaking, they have shown a willingness to handle issues we may 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.