SQL Server Reviews

We use this solution to store our data and for running queries, simple select queries that enable me to create the views I need and report from those views. I'm an ESM specialist and we are customers of SQL Server. 

I like the stability of the solution, the fact that you have two, three, four nodes replicating at any given time at different locations, and they're all synchronized; if one is lost it automatically moves to another. The other advantage here is that when it comes to application maintenance, you switch onto another node while you maintain another server and there's no downtime. 

The solution could have additional security. 

The solution is easily scalable because of its flexibility.

I don't do the installation, but it appears straightforward according to those who carried out the implementation. These days deployment takes about an hour. We have 1,200 or so users. With the onboarding of more customers, we'll be increasing our use of SQL Server. For now, we have one person dealing with maintenance. 

I rate this solution nine out of 10. 

It is for supporting our custom applications. We have a number of custom applications that we use that have SQL embedded.

I am using the version before the latest one.

Its usability is very good. Its performance is satisfactory.

Their support could be better. There should be more visibility on the progress of the ticket, and their last line of support should be more knowledgeable. Other than that, we have nothing to complain about.

I have been using this solution for seven to eight years.

Their support could be better. Sometimes, you don't have much visibility of how your service request is progressing. There should be more visibility, and the last line of support should be more knowledgeable.

It was straightforward. It took two to three hours.

We have internal staff for its implementation. We have a team of about three or four people who are well-versed with SQL Server, and we have 30 to 40 users who use this solution.

You need to pay for the license. It most probably has per-core licensing.

I would recommend this solution to others. We are satisfied with the product in general. Overall, I'd rate it an eight out of ten.

All our databases are using Microsoft SQL. It supports our application, such as HR and finance.

SQL Server could improve by being more user-friendly, it is still geared towards specialists. Additionally, the monitoring system is difficult to use, not everyone can use it well. The configuration should be able to be done through the GUI.

I have been using SQL Server for approximately 10 years.

SQL Server is highly stable.

SQL Server is very scalable because we use it across a couple of different types of applications, such as micro-infrastructure setup and server farm.

The solution is suitable for any environment, such as small, medium, and large enterprises. 

SQL Server support system is well-established. It's a Microsoft solution therefore you receive support very easily. It is the number one selling point of SQL Server. I have been highly satisfied with the support.

SQL Server's initial setup is simple. However, you must be a specialist to do it. That's the unfriendliness that I see about the solution. It has to be done by an engineer and not any engineer can do it, you have to be a specific Microsoft engineer.

My advice to others would be to create a standard for SQL Server to allow a high level of security. What we did is, we adopted CIS, which is the Center for Information Security, hardening standards and benchmarks to keep it secure. SQL Server out of the box comes with a lot of unnecessary services that can make you very vulnerable to any site attack.

I rate SQL Server an eight out of ten.

SQL Server is only running in China, it is not connected to our site.

We have some PCs running on Windows 7, but it is not supported.

We have no vision. We don't know when or how we have been hacked.

We require expert support with it. That is why I am looking for CRMs.

We have been using SQL Server for one year.

We use several versions such as 2008, 2012, and 2015.

SQL Server is stable.

We are not running more than 1%. Scalability needs improvement.

We have 415 users in our organization.

We have plans to increase our usage.

We have an Active Directory system, so we can install antivirus on the endpoints.

Normally, we can check with the deployment person, and our IT team will respond to the message once my team has deployed it.

I have some experience with McAfee MVISION Endpoint. We are focused on the MV1 edition. We have to blend into the EDR.

McAfee has three editions, MVISION 1, 2, and 6. We are still working with version 1.

We are also working with Endpoint Plan 1.

We have 15 servers, both Windows OS and Linux OS.

The initial setup is not complex.

We have an in-house IT team that can deploy this solution.

We have some people who have worked in IT and with endpoint software. I believe my team is capable of handling the new software, and solutions.

The licenses are purchased annually.

The license fee is very low.

I was looking into some solutions to meet our company's needs. Endpoint Protection for Business, McAfee, and Microsoft Defender for Endpoint was among the solutions I researched. For endpoint security, I prefer Microsoft Defender or McAfee Endpoint Security.

Now we're comparing the cost-effectiveness, and especially the features, and giving ourselves the ability to choose the solution, truly enabling a solution.

I would recommend this solution to others who are interested in using it.

I would rate SQL Server a nine out of ten.

We developed a product for banks and we store the data in SQL Server.

SQL Server has good performance, but it could be better.

I have been using SQL Server for a couple of years.

The stability of SQL Server is very important for us because we provide services for banks. The banks need a secure and stable solution from us and we have requested from the cloud provider to give us this level of service.

We have approximately 10 developers and architects using SQL Server. Additionally, we have approximately four end-users using the solution.

The support from Microsoft has been good.

I have previously used Oracle.

The initial setup of SQL Server is not complicated. 

We have four technicians that do the implementation and maintenance of the solution.

There is a license required to use the solution and I am satisfied.

I would recommend this solution to others.

I rate SQL Server a seven out of ten.

We use SQL Server for storing all our company information, such as ERP, customer applications, and our wealth management systems. All of our data is stored in SQL Servers.

SQL Server is a very mature solution.

I have been using SQL Server for approximately 20 years.

SQL Server is a stable solution.

The scalability of SQL Server is good. It can scale up to thousands of times more data than I have. 

We have approximately 250 people using this solution in my organization.

I have not used the support from SQL Server.

The initial setup is simple it takes approximately 10 minutes. You only need to run the setup and you have SQL installed.

I have installed SQL databases and SQL Servers regularly. I did the implementation of this solution.

This solution requires one administrator for implementation and maintenance.

Some of the licensing are very expensive, such as the Enterprise license. 

The Express version is free. There are a lot of licensing options.

I would recommend this solution to others.

I rate SQL Server a nine out of ten.

We do data warehousing on it. We have databases on it. A lot of our applications use it for transactions and data.

We're using version 2019. We're trying to migrate to 2021 because 2023 is not yet that stable.

It works fine in terms of performance and stability.

I would like Microsoft to evolve SQL Server because stateful databases dying are in a way. We would like to find out if it can absorb Hadoop and other similar things. They should make it useful for data mining. Data is evolving forever, and how we store it is also changing constantly. So, SQL Server also needs to change.

I have been using this solution for two decades.

It works fine. There are no issues.

It is scalable. There are a lot of users. There are over 300 applications using this solution. Each application has its own users. In the technical team, there are about 13 people working with it.

I logged a ticket recently when I had an issue with the data manager. Their support wasn't that bad. I would rate them an eight out of 10.

I've used different solutions. There are times when I use Db2, and there are times when I use Oracle Database. Oracle beats SQL Server when it comes to procedures and process optimization.

The initial setup is easy. It takes 30 minutes at the most. What limits you is just your infrastructure in terms of:

• Do you have enough room on those servers to process that stuff?
• Do you have enough RAM resources?
• Do you have enough storage?
  

I can do it by myself.

It is annual.

I would recommend it to other users. I would rate it a nine out of 10.

We use the solution on FastAutomate, our core product, to store the aggregated data from different nodes. It resides on the server that's handling the agents. We also use it for different organizations for development. Therefore, we use it for development mainly.

Overall, we've been satisfied with the capabilities of the product.

The solution is stable. It works without issue - to the point you rarely need any technical support at all.

The scalability is very good.

It's got an easy initial setup.

The remote access aspect needs to be improved in terms of security. Right now, it's a little bit hard. 

Also, they need to work on the user interface, as it's a little bit old. They need to improve it a little bit. 

The pricing could be lowered a bit.

We've used the solution for a while. 

Its stability has been good. The solution performs well and is reliable. There are no bugs or glitches. It doesn't crash or freeze. 

We have found the solution to be scalable. If a company needs to expand, it can do so. 

Techni al support is good. That said, it's hard to judge as you don't need support on SQL Server. It's working without trouble or issues. Therefore, it's rare to seek support for SQL Server. You rarely have to deal with them.

I've also used SQL Azure.

The recommendation is based on the use case. It depends on what use case the customer will need. If they don't have the capacity to manage their own Server, I would recommend Azure, as it's managed. Therefore, you don't have to worry about the management and administration.

The main difference between the two is, in some data types it is not available on SQL Azure while it's available on SQL Server or vice versa. There's a version of SQL Server with a little bit of limited functionality. That said, the difference is not huge. You can go back and forth between them if you want.

The initial setup is very easy. It's even easier than before, in fact. A company shouldn't have any problems with the implementation. 

The price could be less.

I'd rate the solution at an eight out of ten. If the price was a bit less or the remote access was better, I would rate it tighter.

In general, I've been happy with the product.

SQL Server is our primary database for identity access management.

What I find most useful in SQL Server is that it's easier to manage and to query. Its databases are well-designed. It's easy to do any changes, and it's easy to query the database through reports and whatever information you need.

There is always room for improvements. In SQL Server, the databases should be able to deal with more data in a faster way. Sometimes, when you have a lot of information running on the SQL databases, the system hangs. Though there are always improvements being done to SQL Server, there's still a lack of speed in being able to process so much information, so the performance of this solution still needs to be improved.

Another area for improvement in SQL Server is its front end, in terms of running the queries, e.g. it would be better if it could give suggestions. For example: When you write something, this solution could have a feature similar to a dictionary's intelligence that will tell you what to write such as the one you have in Word, or in PowerPoint, for example, you'll have the design suggestions for it. An improvement I'd like to see in SQL Server is for it to suggest what you put next when you are writing SQL codes or queries.

We've been dealing with SQL Server for four years now.

SQL Server is a very stable product.

SQL Server is a product you can scale. You can add and remove modules as needed.

SQL Server is expensive if you use the advanced SQL version. If you use the standard version, it's not expensive, because it's included in Windows, in Microsoft. It's very expensive if you use the advanced version. We're using both. For IBM, we're using the advanced version, but then we use the basic SQL Server for the other platforms.

You just pay for the SQL Server license. There's no additional cost as everything's already included.

We currently don't have any issues with SQL Server. There's nothing that we couldn't solve internally, so I haven't had the chance to contact their technical support team.

I'm giving SQL Server an eight out of ten rating.

I can recommend this solution for medium and large enterprises. For small enterprises, it depends: if they use the standard, free one on Windows, yes. If they don't, I wouldn't recommend the investment.

I have SQL Server running in an on-premise environment, but we are testing it out on the cloud. We are trying out using APIs to access a database. SQL Server creates a lot of opportunities for us. While some of the larger companies have Oracle, SQL Server is more common in Peru. I'm responsible for administration and implementation, including configuration and data replication.

Our biggest problem with SQL Server is latency. The communication between the cloud and the on-premises environment is slow. The data needs to be encrypted for security, and you have to exchange data certificates between environments. You can adjust the configuration to improve performance, but it would be nice if SQL Server had some templates to resolve problems.

I have been working with SQL Server for 10 years. 

I worked on Oracle Database for four years. In the last year, I have been working with various cloud databases, including Cosmos DB and DynamoDB in AWS and Azure.

I rate SQL Server nine out of 10. SQL Server is an inexpensive solution. I recommend it if the project isn't sensitive. SQL is similar to Oracle and integrates well with tools in the cloud environment. The difference is that Oracle is for data solutions where there is replication and moderation.