SQL Server Reviews

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.

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.

SQL Server is our primary database for identity access management.

What I find most useful in SQL Server is that it's easier to manage and to query. Its databases are well-designed. It's easy to do any changes, and it's easy to query the database through reports and whatever information you need.

There is always room for improvements. In SQL Server, the databases should be able to deal with more data in a faster way. Sometimes, when you have a lot of information running on the SQL databases, the system hangs. Though there are always improvements being done to SQL Server, there's still a lack of speed in being able to process so much information, so the performance of this solution still needs to be improved.

Another area for improvement in SQL Server is its front end, in terms of running the queries, e.g. it would be better if it could give suggestions. For example: When you write something, this solution could have a feature similar to a dictionary's intelligence that will tell you what to write such as the one you have in Word, or in PowerPoint, for example, you'll have the design suggestions for it. An improvement I'd like to see in SQL Server is for it to suggest what you put next when you are writing SQL codes or queries.

We've been dealing with SQL Server for four years now.

SQL Server is a very stable product.

SQL Server is a product you can scale. You can add and remove modules as needed.

SQL Server is expensive if you use the advanced SQL version. If you use the standard version, it's not expensive, because it's included in Windows, in Microsoft. It's very expensive if you use the advanced version. We're using both. For IBM, we're using the advanced version, but then we use the basic SQL Server for the other platforms.

You just pay for the SQL Server license. There's no additional cost as everything's already included.

We currently don't have any issues with SQL Server. There's nothing that we couldn't solve internally, so I haven't had the chance to contact their technical support team.

I'm giving SQL Server an eight out of ten rating.

I can recommend this solution for medium and large enterprises. For small enterprises, it depends: if they use the standard, free one on Windows, yes. If they don't, I wouldn't recommend the investment.

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.

For my business requirements, the performance is good. If we use it on a larger scale, it will not fit our business needs.

It is easy to use.

It has simple syntax, but you must check your packet on a daily basis.

We occasionally face or encounter a problem with the database table itself. Some tables and their flyers, as well as the content's data, must be truncated. It was a major issue with my ERP system because it is a backbone database application. It hasn't happened often, but it was a bad experience. Regarding some table issues, I believe we will encounter them in many applications, but I believe the other vendor, such as Oracle, has more than tools to protect my data.

In the next release, I would like to see a better user interface and a familiar syntax.

I have been working with SQL Server since 2003. It's been more than 10 years.

We use a version component for each application. One is for 2014, and the other is for 2017.

SQL Server is a stable solution.

We have two users in my company. The ERP system has nearly two users. We have about five users for subsidies and the sister company.

I'm not going to increase our usage because I'm going to the cloud. We're going to the cloud, according to my plan. Oracle NetSuite, Microsoft cloud, or NetSuite. Because they are both cloud-based, I don't need to increase the number of SQL server users, either for administration or for users.

I'm not opening a ticket with SQL about the issues we experienced, because it was opened by my partner, but it didn't solve the problem. For my table, it almost uses truncate comma syntax, and it flushes my table contact.

Approximately 10 years ago, I used Oracle Database.

The initial setup is straightforward. I did not encounter any issues.

We have 12 technical teams with four admins to maintain the solutions in our companies.

I don't need a license for it as I will be migrating to Office 365.

I would recommend this solution for small and medium-sized companies, but for enterprise businesses.

I know it's not the best, but this application meets our requirements.

I would rate SQL Server an eight out of ten.

I am an integrator of this solution and my customers use this for ETL and reporting.

This solution is user-friendly and easy to understand.

The stability of the solution should be improved in the next release. Sometimes it is great, sometimes it is troublesome. I would also like data conversion and the code pages to be a bit more straightforward.

I have been working with SQL Server for the past fifteen years.

Stability can be shaky.

This is a scalable solution.

I use to work with Informatica via the Oracle package and switched to SQL because it is cheaper and a bit better than the others.

This solution is pretty easy to deploy.

SQL Server has the best licensing price.

There is a lot to learn about this solution when first using it, as with any other tool.

I would rate this solution an eight out of ten.

This application is used as a contact center and would be great for banks.

The backup capabilities are extremely good.

I would like to have the ability to restore backups in the next release.

I have been working with SQL server for the past ten years.

This solution is very stable from what we have seen.

This is a scalable solution.

Technical support is very good. I am able to easily contact them and they are very informative.

The initial setup was straightforward.

This is a great solution for anyone with basic knowledge of DNS who wants to build up a database. There are many videos to help you navigate the platform.

I would rate this solution a nine out of ten.

I use the client, however, I can also use the server, the Microsoft SQL Server Studio. I can use both, both the client and the studio.

We connected Automation Anywhere to the DB. Our reporting tool is also connected to that DB. Our financial application is also connected to the DB and some other databases too as well as some of our APIs.

I like the way it can manage the users from the security section where you can change their roles. 

SQL is simple to manage, as long as you know the script, and know the tables that you make reference to. If there are errors, you can easily debug them. 

You can easily debug and resolve your issues. 

The ease of backup, how you can back up and call up your backups too is great. Backups hardly get corrupt, except if maybe you have some bad hard drive clusters or bad hard drive sectors.

It is stable.

It's an easy-to-use product.

I find the solution to be scalable.

The pricing could be more affordable.

It's like to see less frequent updates. They should be once a month.

I've been using SQL Server for a very long time.

The stability is great. It's very reliable. There are no bugs or glitches. It doesn't crash or freeze.

The product scales well. If you need to expand it, you can.

We have around 50 users on the solution right now. 

The solution is pretty problem-free and therefore it would be rare to have to reach out to support.

We've always used SQL. I also use SQLite.

The initial setup is very simple, very straightforward. It's not too complex. 

The time it takes to set up isn't long. The time of installation is determined by the local system or the server where you are installing it to. That said, it's a light solution. For me, it took maybe ten minutes. 

We have eight people who are technical and can handle deployment or maintenance tasks. 

I did the installation myself. It's not hard to do. You don't need a consultant or integrator.

We pay a monthly subscription fee. 

I'm an end-user.

I would recommend the solution to other users and organizations.

Overall, I would rate it at a nine out of ten.