SQL Server Reviews

It has all of our data. Our company sells contracts when you buy a car. We sell aftermarket insurance for the tyre, wheel, ding, dent, windshield, etc. When somebody buys a contract, we capture all of that data into a legacy database PostgreSQL, and my task is to incorporate that into our financial platform using T-SQL. So, I write queries, procedures, and views. I use SSIS, and I use SSRS. My job is to get the data into our financial system so that we can process claims, payments, cancellations, and refunds. 

In terms of its version, we're up-to-date. We have version 2019.

This is the heart of the whole company. SQL Server is where all of our financials are. It has all of our data.

I've been using SQL Server for 20 years, and there is nothing that it can't do. It is awesome.

When we are talking about event space architecture, scalability generally comes into play. For example, I might have a hundred thousand transactions a second, and then all of a sudden, I build something that everybody in the world wants. The next thing I know is that I have a million transactions a second. So, to be able to process the throughput, I'd have to scale up, and then when the holidays are over, I'm again down to a hundred thousand transactions, and I want to scale back down. SQL Server is not going to do that. In this way, it is not very scalable. One of the reasons why they want us to use Kafka is so that if we need to, we can do that, but our base program is on SQL Server. So, this is where we would use a Kafka event stack so that if I need more servers, I can just write a command, and I can have more consumers, more brokers, and more producers, and when the holiday season is over, it scales right back down again. SQL Server is not going to do that.

I have been using this solution for 20 years.

We do clustering. If one SQL Server goes down, it automatically goes to another one.

I don't ever need tech support. If it breaks, I can just rebuild it.

They're now using a different database for contracting called Road Runner. I don't know what that is, and how it stores data. I don't know anything about it. 

There is also Postgres. I like SQL Server more than Postgres. That's only because I know SQL Server. I don't know Postgres as well. So, I can't say which one is better because I don't have the same amount of experience in both.

I can bring up a SQL Server in an hour or so and set it up.

In terms of maintenance, the number of people required depends on the need. 
We have a team of DBAs, developers, and UA analysts. We probably have 40 people in our IT area who are maintaining our solution. I'm just the developer. I'm the guy who makes the magic happen, but without other people collecting the information that I need to make the magic happen, I'm stuck. Without the guy who is an expert in permissions, partitioning, and performance tuning, I'm stuck. So, it's definitely a team effort. You can do it all, but you don't want to do it all because then you're running your head off, and you don't really get good at anything. It would be a jack of all trades, master of none type of scenario.

You will seldom find a database that was designed correctly. Just because you got a poor-quality database doesn't mean that you're going to get a better database anywhere else. You rarely get to build a thing on your own. Usually, you inherit somebody else's stuff. So, the challenging thing is working with what you have while trying to implement a better solution. My only advice is to be patient.

I would rate it a nine out of 10. I wouldn't give anything a 10 because I don't have that kind of knowledge, but right now, it does what I need it to do.

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

We've been using this solution for many years.

We're satisfied with the stability.

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

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

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

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

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

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.