SQL Server Reviews

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.

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 use the SQL Server for backups and for creating databases and a lot of other stuff. I also use it to shrink data and some stuff like this. 

The solution is great for creating backups.

You can create databases using this product.

I like the way you can shrink the volume using SQL.

It's a very stable solution.

I've found the product to be able to scale well. 

There should be more security updates for the product. That would be ideal. 

I've used the solution for about five or six years. I've used it for quite a while at this point. 

The stability of the product is great. There are no bugs or glitches. It doesn't crash or freeze. it's reliable. 

So far, I have found the solution to be quite scalable. If a company needs to expand it out, it can do so. 

We have about 4,000 users on the solution currently. About five to seven different departments use it. 

I don't directly deal with technical support. That would be handled by a different department and a person who is responsible for dealing with issues. Therefore, I can't speak to how helpful or responsive they would be. 

I did not use a different solution before using SQL. 

It's easy for anyone to install. For me, it was good and easy to install. A company shouldn't have any issues tacking the process. 

The deployment is quick. It takes about 15 to 20 minutes. That's it. 

I didn't need the assistance of consultants or integrators. It was something I could handle on my own. 

You can pay an annual or monthly licensing fee in order to use the solution. 

I'd recommend the solution to others. It's very useful.

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

We have a few transitional systems in our large company that we maintain with Microsoft SQL Server.

SQL Server is similar to other Microsoft products, such as BI, they are easy to use. You do not need to have an expensive BD to maintain them. All the useful intuitive features you find in Microsoft solutions you will find in SQL Server.

I have used SQL Server within the past 12 months.

SQL Server is stable. However, every product has limitations. It is stable for a certain amount of workload. Beyond the capabilities of this solution, you will need other data solutions, such as Oracle. A solution that is more secure.

Since this is a relational order system, scalability has a limit. If your system is very big, you need bigger servers and you have to spend more money. We scale a system up to a certain level, and then we move or shift data to the warehouse, which is NoSQL. We then do not have any bottleneck in scaling. For using this technique we are happy with it.

It is hard to tell or count how much data we are using because being one of the leading companies in Bangladesh, we have many teams who work on it. Different teams work on many different technologies.

We have not had an issue with the scalability SQL Server.

For databases, we have used a lot of data tests with other solutions, such as Oracle. We have used all Oracle data, Postgres, and a few others.

The initial setup is very straightforward. You do not have to worry about the management of the SQL Server instance.

To scale the solution there are additional costs.

I rate SQL Server an eight out of ten.

We are consultants and users of this solution and we deploy both on cloud and on-prem. The primary use case of this solution is for its Health Check feature. I'm the company owner and CIO.

We assist companies to improve the performance of their servers. We're generally able to improve performance by 40%. 

I like the Always On tool which improves the SQL server availability. We cross-link servers with Oracle, MySQL and other platforms using PolyBase as a service to join with big data systems like Spark.

I think the treatment of database storage could be improved. There is also an intermediate locked file that prevents users from inserting or writing something in the database that slows things down. I'd like to see the Perform Volume Maintenance Task made available for locked files. It would mean that the SQL server can directly grow files. Without it, you have to go to the local system account, which can disrupt users. It's connected to the local security policy. 

I've been using this solution for 20 years. 

This solution has fantastic stability. 

The scalability is great, and you can use several servers concurrently without using duplication services. Our company is small but we manage around 30,000 users. We have 10 people involved in maintenance and deployment. 

We are part of the Microsoft team in Spain and sometimes we have to call support with a specific question but not very often. In the past 12 months I've only made contact a couple of times. 

I previously used Informix DB because Linux was not the best tool for enterprise when I began working in the industry. Microsoft was working on new technologies and when they came out with SQL I switched to it. I've had the certification on SQL for several years already. 

The initial setup is relatively easy but it depends on the situation, and sometimes requires some planning. You can configure SQL after you've deployed on cloud. Implementation can take some time because it's not just the installation of the SQL server which can be done in less than an hour. The implementation of the database systems can take several days or weeks depending on the organization. Our consultants have more than 12 years of experience working as DBAs, so we carry out the installation. 

In a standard package, you need to buy two core packs. If you need four core packs the price is around € 8,000. There are more options in the cloud where fees are around € 60 a month. The cost is scaled and if you're deploying in the cloud you need to buy a machine infrastructure as a service. We only sell the license across the cross solution provider (CSP) program. If you have less than 25 users, you can buy an SQL standard per server license where the cost is around €1,200 approximately.

I rate this solution 10 out of 10. 

We provide support services to clients. We find that some of our clients are running the latest system while others are still on Windows 2016, others are moving to 2019. Some other clients take time to upgrade. If I interact with five clients, I'll basically be in five different environments.

Our use case for the SQL Server is for transaction processing. We store all the transactions that occur. For example, if you now purchase something from the point of sale, all the information about the good you are purchasing gets stored on the SQL Server. 

When you perform a transaction that information is stored at the bank that owns the point of sale and perhaps even your bank, where your money is will be stored in a SQL Server.

All the people in all of the organizations, which are involved in the process use SQL Server.

If your transaction goes through my server, I store part of the transaction there, and if I have to route that transaction to Visa or Mastercard, they have their own SQL Server, and they also store the transaction up until you get receive your goods at the particular merchant. Almost everyone in that transaction stores the information on their respective Microsoft SQL server.

The most valuable feature would most likely be querying. We query a lot, we use a lot of stored procedures. As for other features, such as replication and all other more fancy features we don't use them the most. I do not know, but perhaps the DBAs would be the best people who know of the features that they use, but as far as how I use it, it's just for querying and running stored procedures. We use the bare minimum features.

We do not know all the features of SQL Server.

If SQL Server could perhaps run on Linux, that would be good. Most of us prefer Linux and I've used a lot of Linux. I understand that SQL Server is quite powerful, but I'm not sure if the functionality is there, but if it could be used in an open-source type of environment, it would be very good.

I have been using SQL Server for approximately 10 years.

SQL Server is stable and is a high-performance database. We do hundreds of transactions per second, it's fairly robust, it does not struggle. Mostly, if your hardware is strong enough and you've set it up properly, then you can actually perform a lot of transactions per second on a SQL Serving installation.

The scalability of SQL Server is relatively easy. if you are in a Microsoft environment, then I think that it relatively it should not be that difficult. However, I haven't been on a project whereby we have had to scale.

SQL Server is suitable for all companies in my experience, ranging from small to large enterprises businesses.

I have not dealt much with technical support, because most of the time when we have issues, we go online. If it's a Microsoft issue, then we go and read up what that issue is. If there's an error, then there are places on the Microsoft support system where we are able to enter in the error code and it is able to tell you why you have that problem. As far as dealing or interacting with people or technical support from Microsoft, I have not done that.

I use MySQL and when comparing the solutions I have found the SQL Server is much more professional, and it's quite big and robust. MySQL is a community of people who are contributing to a project and you have to hack them in order for it to work. But it is quite good as well.

The installation is straightforward and not complex. However, it depends on some of the features that you may want to use. I think it is simply because you only need to tick whatever functionalities you want to use and the ones that you don't need to use, you don't select them.

Most of the time we are doing the implementation from scratch. If it's a big bank, then they would normally have dedicated people who deal with SQL. However, it depends on the customer.

There is some maintenance that is required, such as updates and tuning. We need to find ways of filling up the data so that it doesn't get stale but normally with regular updates, you should be fine.

I cannot comment on the price because I find that the organization already has a license when I arrived. I have not had a sneak peek at the price. When you join an organization, they tell you we are using the 2018 version and that someone purchased it. I don't know who purchased it, I'm not privy to that kind of information.

My advice to companies that are wanting to implement the solution is they have to make sure that they've have a proper skillset. When you have the proper skillset or people who are certified it would make for a better investment into the product. When you are certified, then you know the system in and out and you should be able to have the best implementation for the type of business you have.

I rate SQL Server an eight out of ten.

We use SQL Server as a database solution.

The performance of the SQL Server is very good.

I have been using SQL Server for a few years.

The stability is very good.

The solution is scalable. However, we do not have many large servers using SQL Server anymore, we have moved to SAP HANA.

We have approximately 2,000 users using this solution in my organization.

The support offered by Microsoft is very good. We have not faced any issues with SQL Server to need to contact their support.

We use SAP HANA as a database solution for certain use cases.

We have technical managers and engineers that do the maintenance and support for this solution.

We are on an annual enterprise license for the solution and the cost of the license could be reduced.

I rate SQL Server an eight out of ten.

We use the latest version.

Most SQL Server applications come with package applications from the shelf. This means that when one buys an application, most of these applications work with SQL Server as a basis. They add SQL Server as a database to applications which come with it that one buys. As such, I don't see many people developing new applications with SQL server.

A valuable feature of the solution is that it is comparatively simpler to manage than Oracle. Now that the Linux version is an option, this can be taken into consideration, since Windows limited one's use to things which could only be done in Windows. 

Database support could be improved. Oracle provides better support. 

While the price of the solution is comparatively cheaper, people are paying to Microsoft, in any event, for other things that they're using. 

Thoughs the licensing cost could be cheaper, this depends, as there is nobody who only uses the database with Microsoft. Every company has Windows, Office, Active Directory and all the security features of Microsoft. This means that, overall, when one buys these licenses together, he also gets the database. The focus is not on the price of the database, but what is actually being paid to Microsoft. 

The licensing price could be better, more user-friendly. Things should be be moved from the enterprise to the standard edition. 

As with Oracle, we have been using SQL Server for a long time. They actually have the same shelf life. We have been using the solution for around 30 years. 

The support does not reflect how Microsoft used to be. It can depend. Oracle has a much more sophisticated database, so it comes with expanded support. There are many solutions which come out of the box, as all the problems which could arise have already been encountered by the customers. This is why they are building a big data, to have a ready answer for any issue which may arise, the answer being very quick and straightforward. 

When it comes to Microsoft, noone delves deep, so such problems as those arising with Oracle are not encountered. Oracle is much more sophisticated and comes with many problems. This is why the solution comes with better support, as they have already provided a foundation for many of the solutions.

We did not use a solution prior to SQL Server, with the exception of, maybe, Access. 

The installation is good. 

It took very little time, a couple hours. 

Installation can be done on one's own. Everything can be done sequentially, from one thing to the next. 

While the price of the solution is comparatively cheaper, people are paying to Microsoft in any event for other things that they're using.

Although the licensing cost could be cheaper, this depends, as there is nobody who only uses the database with Microsoft. Every company has Windows, Office, Active Directory and all the security features of Microsoft. This means that, overall, when one buys these licenses together, he also gets the database. The focus is not on the price of the database, but what is actually being paid to Microsoft.

The licensing price could be better, more user-friendly. Things should be moved from the enterprise to the standard edition.

Microsoft is fine. They have done a good job.

As everyone has a station with Microsoft installed, everybody is making use of it. When it comes to the database, this depends on the application. As I said, we are talking about a package solution, so use of the same application could consist of several hundred people or thousands. 

I rate SQL Server as a nine out of ten.