SQL Server Reviews

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.

We are an independent software vendor and users of this product. I'm a company founder. 

The most valuable feature for me is that the database engine is always on.

The solution is lacking a compound index for comparing values as you find in PostgreSQL. SQL Server doesn't support that feature so we need to build binary indexes to be able to compare those compound values. I'd also like to see AI capabilities. Oracle has a cloud solution which maintains its own indexes. If you buy a service from Oracle's cloud system, it keeps track of the queries that you have made to the database and it automatically implements its own indexes. It's such a good optimized database and I'd like to see an SQL Server that maintains its own indexes with AI capability. 

I have an issue with memory support: If you create a table and a third procedure followed by an additional procedure using that third procedure, and then wish to alter the original table with the two dependent objects, you have to drop those third procedures and alter the table and recreate dependencies. Those dependencies make it impossible to work in an online environment. If there's a problem, for example, in your implementation and you have to modify a production system, for example, it can't be done. SQL Server generates DLL files in this instance and you can't change DLLs of a running program. It should be easy for them to solve. 

I've been using this solution for 20 years. 

I have the issue of memory support but the solution is stable. 

For Turkey, the licensing costs are too high. Previously, independent software vendors like us would buy the license from Microsoft and resell to our customers.
For vendors it was half the retail price, but that's no longer possible. Sometimes enterprise companies buying in bulk can get licenses at a better price, but we don't have that and it's impractical for us to sell this solution. 

The solution doesn't have too many surprises and is easy to understand. It's all dependent on the architecture and implementation. Newer products use code-first solutions and I'm not sure people will continue to go down the SQL path. If I were starting my project now, I would have chosen another database. 

I rate the solution eight out of 10. 

SQL Server has helped us make better decisions through the queries that we have built.

SQL Server's most valuable features are that it is a large number of community resources to help you out. that's one, and then it is quite powerful.

SQL Server backups could be better.

I have been using SQL Server for approximately three years.

SQL Server is a stable solution.

I have found SQL Server to be scalable.

The solution is suitable for all-sized businesses.

The technical support from SQL Server is quite good.

I was satisfied with the implementation of the solution.

The price of SQL Server is great. In my company, SQL Server is part of the Microsoft Suite, we don't have to pay for any additional license costs, it's quite cost-effective for us.

My advice to others is SQL Server is a good tool to work with and there are a lot of community resources available to help you out in case you are stuck anywhere.

I rate SQL Server a ten out of ten.

We're using SQL Server for database work.

What I find most valuable in SQL Server is that it's user-friendly.

The product needs improvement in its UX design. A newer interface is what I'd like to see in the next release of SQL Server.

I've been working with SQL Server for two years.

SQL Server is a stable system.

SQL Server is a scalable system.

I'm satisfied with the technical support provided by Microsoft for this product.

SQL Server is easy to implement, especially because it's a very common system that we use in the workplace.

Pricing for this product is very reasonable.

I evaluated Oracle Database.

SQL Server is a common product that I use on a daily basis, and I'm using its latest version. Most of my colleagues use it for database work.

200 people use this system in the company.

My advice for people looking into using SQL Server is that it's the best choice, especially for those who are beginners with databases.

My rating for SQL Server is nine out of ten.

SQL is our main data store for enterprise applications, all applications that we have in the organization.

SQL could be improved by making all features available on the on-premise version of the product as well as the cloud version. When you buy the on-premise version, it's sort of an inferior product compared to the cloud version, which seems to get most of the latest and greatest features.

I've been using this solution for a few years.

SQL is stable.

This solution is scalable.

I am satisfied with Microsoft's technical support.

The initial setup was ok, it met our requirements.

We implemented SQL ourselves, and it took around a week to install.

Subscriptions are available on a yearly basis.

I would give SQL a score of nine out of ten. 

We are using it for various applications.

It is easy to deploy and easy to maintain.

They need to improve their support. It should be faster.

I have been using it for a couple of years.

It is stable.

It is scalable. We have more than a thousand users who use this solution. It is being used heavily, and we don't have any plans to increase its usage.

Their support needs improvement. It should be faster.

We didn't use any other solution previously. We have been using it for a long time.

It was easy.

I can install it myself. We also have a technical team of three admins.

Its licensing is yearly. There are no additional costs. There is only the subscription license.

I would recommend this solution to others. I would rate it a seven out of 10.

We primarily use the solution as a backend server.

There are a few applications of the Oracle product for our data sitting on the SQL Server as well. 

It's useful as a backend server.

We have found the solution to be scalable. 

The stability of the product needs to be improved. It's really not stable enough.

In Microsoft, the Active-Active options are not available. There are a lot of requirements that are coming right from the customer, which may not be provided by Microsoft. There are a few use cases where we do need the Active-Active options instead of Active-Passive, yet those kinds of options are not available for Microsoft.

We've been working with the solution for going on five years.

We've struggled with the stability of the product. We'd like for it to be more stable and reliable. 

The scalability is very good. If a company needs to expand, it can do so.

We are a customer and an end-user.

I would rate the solution at a seven out of ten. While the scalability is there, the solution is lacking a few aspects that customers really need.

We primarily use the solution to store databases. 

Since MongoDB, we have come up and there are lots of tools that do enhance the database management system or keep an eye on our data. People can easily access it. 

The solution is stable. It's reliable. 

The initial setup is simple. 

MongoDB is a bit better. A traditional database system, like the SQL Server, is failing to catch up.

You need an experienced person to use that piece of technology so that you can store everything in a logical manner. We'd like it to be easier to store in a logical manner.

The scalability could be better. 

We've been using this solution since 2012. It's been a while at this point. 

It's not scalable. It hinders your performance as it's slow in nature and you need experienced people to work on it. That is why it's not very scalable.

We currently have ten to 15 users on the solution. 

At this time, we have no plans to increase usage. We are focusing more on MongoDB.

We don't have any experience with Microsoft technical support. Therefore, I wouldn't be able to rate how responsive or helpful they are.

We did not previously use a different solution. We are currently moving towards MongoDB, however.

The installation is easy, especially since the new version has come up. Now, with the latest versions, installation is easy.

I cannot remember the time it took to complete the installation.

Earlier, we had to bring in a technical team, however, our own technical team is quite experienced now. They can now do it themselves.

We pay a yearly subscription fee. 

We use both cloud and on-premises deployment models. We're using the latest version of the solution. 

I'd recommend the solution to other users and organizations. If there are people who can't afford MongoDB or if an organization doesn't want to migrate to MongoDB, it's important to keep in mind the users would have to learn the fundamentals of the SQL server first. Knowledge of it is a necessity.

I'd rate the solution at a six out of ten.

While we were still using the solution, we employed version 2008, which is a bit on the old side. 

We basically used the solution for hosting the database for Sage ERP.

Stability and usability, which is quite simple, are two of the solution's most valuable features. 

The solution could be better when it comes to security. 

The solution is part of Windows services, which means that if these should stop running, the database system, too, would be affected. This makes it very crucial to constantly monitor the SQL Server, something which reflects on cheap personnel time. 

Scalability could be better.

Although it comes with a cost, using the most recent version is highly advisable, since it would ensure a certain measure of bug fixes and stability. The sole issue would involve the cost, as this is expensive. 

When it comes to integratable features, the monitoring should be addressed. 

We used SQL Server for nearly six years, although we have since moved to another platform. We have used the solution at some point within the last 12 months. 

The solution has good stability, although my advice is to use the most recent version towards this end, to provide for bug fixes. This will ensure some stability. 

The scalability could be improved. 

As support would have involved a licensing fee, we opted not to make use of this. 

We find there is ample documentation online to allow us to resolve issues through independent research.

The initial setup was straightforward.

Although it comes with a cost, using the most recent version is highly advisable, since it would guarantee a measure of bug fixes and provide some stability. The pricing is expensive, though, this being the sole issue. 

We chose not to make use of support, as this would have incurred a licensing fee. 

I rate SQL Server as an eight out of ten. 

We primarily use SQL Server for reporting.

I love SQL Server's Common Table Expression. In addition to that, I like its lead and lag functions. That helped us reduce a lot of code when comparing rows in SQL Server.

The way SQL Server pivots data could be improved. For example, I would like built-in comma-separated pivot and unpivot functions. 

I've been working with SQL Server for the past seven years. 

SQL Server is stable.

SQL Server is scalable. I can't say if we'll increase usage in the future because I'm only working here as an analyst. It's a company decision. If necessary, then I can make a recommendation. I can go for that if the client wants, so it depends entirely on our client. If the client wants Oracle instead of Microsoft, I don't have an option.

I never contacted Microsoft support about SQL Server, but I have called about Power BI one or two times. It was great support.

I rate SQL Server eight out of 10.