SQL Server Reviews

There are certain shortcomings in the scalability of the product, making it an area where improvements are required.

From an improvement perspective, the price of the product needs to be reduced.

I have been using SQL Server for more than ten years. My company is a gold partner of Microsoft.

It is a stable solution. Stability-wise, I rate the solution a seven or eight out of ten.

It is quite a scalable solution. Scalability-wise, I rate the solution a seven out of ten.

My company's clients who use the solution are mostly enterprise businesses.

I rate the technical support a seven out of ten.

I am using Amazon Cognito for the first time in my company.

I rate the product's initial setup phase a seven to eight on a scale of one to ten, where one is difficult, and ten is easy.

The solution is deployed on the cloud and on-premises models.

The solution can be deployed in a few minutes.

The product is expensive.

In our company's daily operations, we use SQL Server for our enterprise applications.

Speaking about how SQL Server played a critical role in a recent project, I would say that in my company, we used it for full management since we had a three-tier architecture and an enterprise application.

SQL Server was beneficial for data management needs, considering the fact that it was used as a part of SSIS packages, which was helpful for importing the data from legacy software.

The performance of the solution was good.

Though I can't elaborate on the valuable security features, I can say that I did not face any security concerns when using the product.

In SQL Server, I manage data recovery and backup with the help of database mirroring.

I recommend the product to those who plan to use it since it is easy to use.

I rate the tool a seven out of ten.

SQL Server is easy to manage. 

The tool needs to improve its pricing and technical support. 

I have been working with the product for ten years. 

I rate the product’s stability a seven out of ten.

I rate the tool's scalability a seven out of ten. 

I rate the tool's deployment a seven out of ten. Deployment time depends on the customer's environment. 

I rate the product’s pricing a six out of ten.

Our clients are from small, medium, and enterprise businesses. It helps users to manage their data. 

I rate the overall product an eight out of ten.

The solution is used as our backend database for our in-house applications. 

It's consolidated all of our Microsoft Access databases.

Having everything in one centralized set of databases is the most valuable feature.

Over the years additional features, data warehousing, cubing, just better performance and better manageability in terms of the actual Microsoft SQL Server AppLINK console.

I have experience with SQL Server. 

It is a highly stable solution. It was our database of choice because of its reliability. It just does what it says on the tin. We've never experienced any issues with it. I've never experienced any issues with it crashing or anything like that. 

The solution is very scalability. I rate the scalability a ten out of ten. 

Their technical team is very efficient. 

Positive

We switched to SQL for the reliability and scalability.

The initial setup is cumbersome as it's very menu-driven. The deployment takes half a day's time. We run it on a virtual machine or virtual service. We build a virtual server. We downloaded the ISO from Microsoft's licensing website.

I rate the setup an eight out of ten. 

The deployment was done by a single person, in-house. 

The SQL server is affordable. I rate the pricing a five out of ten. 

I rate the overall solution a ten out of ten. 

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.

I use SQL Server for my SharePoint environment.

It offers exceptional performance and robust stability, ensuring a highly secure environment.

The most valuable feature of SQL Server is that it is easy to set up.

There is room for improvement in terms of pricing for SQL Server.

I have been working with SQL Server for ten years.

I am working on the most updated version.

I would rate the stability a nine out of ten.

I would rate the scalability a nine out of ten.

I plan to increase my usage in the future.

I would rate the technical support a ten out of ten.

The initial setup is straightforward.

It is easy to install.

There is a return on investment. The cost benefits are good.

The cost associated with SQL Servers is on the higher side.

While there are other options available such as Oracle Database, Firebird, and MySQL, we specifically chose SQL Server to fulfill our needs for Microsoft services.

We opted for SQL Server as our scalable server solution to meet the requirements of our Microsoft services.

It's a good solution.

I would rate SQL Server a nine out of ten.

We use the solution to provide the database layer for multiple applications.

We have been using this solution for 10+ years.

I have had issues with SQL Server but Microsoft support has been able to resolve them quickly and most came down to configuration/design errors and not a stability of the product issue.

SQL Server is quick to install < an hour.  Additional features increase the installation time.

The SQL Server pricing model is based on CPU cores that your database server utilises.

To others looking into using a SQL Server, I would say that it goes down to the application that you are developing and what funds you have available to run the total system.

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.

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.