SQL Server Reviews

We use the product as a database for the applications. 

The tool helps us by being available always. 

We don't encounter any issues with the solution. 

The tool is expensive.

I have been using the product for the last ten years. 

The solution is stable. 

The tool is scalable. 

The tool is easy to install. 

We have seen ROI with the tool's use. 

I would rate the tool's pricing a six out of ten. It is not extremely cheap but also it's not the most expensive product. 

I would rate the product an eight out of ten. 

We use this solution to extract data. We have a partnership with Microsoft and I'm a solutions architect. 

This is a user-friendly solution. It's great that I can extract the data from the SQL server and store it in my local data source for BI purposes.

I think that performance could be improved and SQL presents some challenges for us.

The stability is good. 

We haven't faced any scalability issues. We have over 200 users. 

I interact with multiple data sources, multiple customers and their ERPs. It can be Oracle, SAP or MongoDB among other solutions. MongoDB, for example, is a little more complex than the SQL Server and we often have more of a challenge establishing a connection with MongoDB.

The initial setup is not a problem. 

This solution is moderately expensive. 

I can definitely recommend this solution to smaller and midsize organizations. I rate this solution eight 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. 

We use SQL Server for developing systems.

The most valuable feature of SQL Server is the performance.

I have been using SQL Server for years.

We have approximately three people who are using this solution.

The technical support from Microsoft has been good.

The initial setup of SQL Server is straightforward.

We have two administrators that did the implementation of the solution.

The price of SQL Server could be reduced, the license is expensive. We have an annual subscription.

I would recommend SQL Server to others.

I rate SQL Server a seven out of ten.

I'm a web developer, and I use SQL for the backend.

The most valuable aspect of the solution is its ease of use.

It's a pretty stable solution.

We found it to be quite scalable. 

While using it, we really didn't experience any pain points. It doesn't need any additional features. 

I have a couple of years of experience with the solution so far. 

The stability and performance are good. It doesn't crash or freeze. it's not buggy. there are no glitches. It's pretty reliable. 

The scalability has been good. If a company needs to expand it, it can do so.

I've never used technical support. I can't speak to how helpful or responsive they would be. 

I'm not sure which version of the solution I'm using. 

I'd rate the solution at a nine out of ten. We've been satisfied with its overall capabilities in general.

We are using SQL Server for data processing.

The most valuable features of SQL Server are the speed, great support, and it is from a known vendor.

The security features of the solution could be better.

I have used SQL Server within the past 12 months.

SQL Server is a scalable solution.

We have approximately 200 users using this solution. We increase the number of users every year.

I have not contacted their technical support.

The process for the deployment is straightforward. It takes approximately four hours to complete.

We did the implementation of SQL Server in-house. We have eight people managing the solution. The team includes managers, technicians, and administrators.

There is a subscription that needs to be purchased to use the solution.

I would advise others this is a good Microsoft solution.

I rate SQL Server a nine out of ten.

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.

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.

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.