SQL Server Reviews

We use it for the banking database. It is for banking software, accounting software, and human resource software that we develop to run our bank.

In our production environment, we are using SQL Server 2014 Enterprise, but we also have an installation of SQL Server 2019 for our development environment.

It is secure, and it is fast. For our present database size, we are using the Always-On feature on SQL Server so that our transactions are replicated among three servers. If one server goes down, we can find the data from other servers. We have benefited from this feature.

We use SQL Server Reporting Services, and it is very good. We use scheduled jobs to transfer reports from one server to another server. 

It needs to be improved to handle big data for large volumes of transactions for big industries. As compared to Oracle Database, SQL Server is not suitable for big data or large organizations where the database size could be more than 100 GB or more. In our country, for a large database and a large volume of transactions, we normally use Oracle Database. Most of the large banks are shifting from SQL Server to Oracle Database because of its slowness. 

We have been using this solution since 2008.

For big organizations, like ours, SQL Server is very good in terms of reliability and security. It has the Always-On feature and many more features. I appreciate its reliability.

I don't know whether SQL Server can support large organizations where the database size is more than 100 GB. It might be because of SQL Server, or it might be because of the programming of the software vendor, but a lot of people think that it is a problem with SQL Server. It can't handle a large amount of data or large data size.

In terms of its usage, about 90% of our applications are running on the SQL Server database. We have around 1,600 users for our software, and all the applications are connected to the SQL Server database.

So far, we didn't ask for any technical support.

We used a flat-file database earlier, and since 2008, we have been using SQL Server. We started with SQL Server 2008 edition, and later on moved to 2012, 2014, and 2019.

We switched because there were many problems in the flat-file database. There was so much inconsistency. Some files were updated, and some files were not. There were big network issues. SQL Server has eliminated such issues, so either all transactions happen or nothing happens. This is a Relational Database Management System, and this is at another level compared to the flat-file database.

SQL Server is very user-friendly and very simple. It is very comfortable for us. We have been using it for a long time, so it is not a problem at all.

The deployment of our production server took less than 15 days.

It was done in-house with the help of our vendor. They have Microsoft-certified people. I have also worked on SQL Server for a long time, so we have an idea of how to migrate from one database to another. It was not a big issue for us.

At present, we have five people for its maintenance.

We are using licensed software for our environment. We have the Enterprise license, and we have a standard additional license.

As compared to Oracle Database, SQL Server is less expensive. For mid-sized organizations, SQL Server is completely all right, but people say it can't support large organizations with more than 2,000 users.

Before implementing SQL Server, you need to learn the concept, design, architecture, and data types of a relational database. You can learn it from YouTube. It is step-based, and you can install it. After that, you can migrate your existing SQL Server to the new SQL Server, depending on the size of the data, data architecture, and data type. 

I would rate it an eight out of 10 because I'm satisfied with SQL Server. It is working fine.

We do backups or restore or query tables to create the views, create some triggers to send the attachment report files, and to report on data.

It makes managing the database easy. Backups are very quick.

Sometimes we experience issues with its stability.

I have experience with SQL Server for 3-4 years. 

Sometimes we experience issues with its stability.

Five thousand users are using the solution. 

The initial setup is easy. Fifteen twenty minutes required for deployment. 

Overall, I would rate the solution an eight 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.

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.

Neutral

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.

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.