SQL Server Reviews

We use it for both development and administration purposes.  

It's serving our data solution needs okay. 

I like that it's the Always On Availability Groups setup. It ensures our servers are always running.

We need it to support Linux for better troubleshooting flexibility.

I have been using this product for five years. We currently use the older versions, SQL Server 2019 and 2017.

We will soon migrate to the 2022 version. 

It works perfectly. No issues there. 

So, it is a stable product. 

There are around 300 to 500 end users using it. 

We use it for our on-premises solutions, virtual servers and SSAS, SSRS packages. Also, our applications are .NET based, so it made sense to use it. 

The initial setup is very easy. It is easy to understand. 

It is an expensive product. 

I would recommend using it , but it's best if you already know how it works.

Overall, I would rate the solution a six out of ten. 

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. 

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 product enables us to grant access to users. The product is easy to use.

The pricing could be better.

I have been using the solution for about four years.

We did not have any issues with stability. The tool is stable.

The tool is scalable. Four other users have access to the server. We are not planning to increase the usage.

The setup is straightforward. The deployment does not take very long.

We did not use an integrator for the deployment. Our in-house team has been able to deploy the tool well.

We pay a yearly licensing fee.

I recommend the solution to others. The solution is straightforward to work with. Overall, I rate the product a nine out of ten.

SQL Server is used to establish secure storage and protect databases from potential vulnerabilities, including those originating from Slack.

The most valuable aspect is the ability to use jobs and various functions to accomplish specific tasks, which cannot be achieved with standard procedures alone. This allows for a combination of features and functionalities to be employed.

I have experience working with SQL Server 2016 and older versions, including handling JSON data. Initially, I found the JSON capabilities to be less helpful, but over time, they have greatly improved. 

SQL Server now offers extensive capabilities for working with various forms of data, particularly when communicating with text, such as in JSON format. 

I particularly prefer working with these features on Azure, as it provides numerous possibilities, especially in the field of business intelligence (BI). Additionally, the serverless platform offered by Azure is highly beneficial and makes tasks easier to manage.

I have not seen significant returns thus far, but I am eager to enhance my experience by transitioning to work in Azure. This shift to Azure is something I am motivated to improve upon.

I have been working with SQL Server since 2018.

We have not had any issues with the stability of SQL Server.

Scalability is dependent on memory.

The matter at hand pertains to whether we are discussing an issue in general or specifically in the context of on-premises environments. However, it is clear that memory and capacity are significant factors in both scenarios. 

Proper management of memory and capacity is essential to ensure smooth system operation and prevent any performance or stability issues. 

As a result, it is essential to handle these issues completely and appropriately in order to meet the system's requirements.

I have not contacted technical support.

The installation process is not complex, but it requires attention to detail in terms of selecting the necessary services and configuring the Cisco server. 

This ensures a proper setup and a tangible model for effective management. While it may not be complicated, it is important to choose the appropriate features during installation. 

Working with ID was not my primary focus; however, I have had the opportunity to work with it for several companies.

It can take an hour to an hour and a half to deploy.

Maintaining it is more challenging than the initial setup. One of the main concerns is ensuring sufficient memory allocation. The default capacity is typically set around sixty, but it can be increased if needed. If there is insufficient memory, it can lead to server downtime and cancellation of transactions, as exceeding the memory limit poses a risk. Therefore, it becomes crucial to address this issue by allocating more memory resources. Additionally, backups and restores play a significant role in ensuring data safety and recovery in case of any issues.

For a brief period, approximately one year before 2018, I had experience working with the open-source version of SQL Server. During that time, I found SQL Server to be the preferred choice, in my opinion.

I developed an application for specific purposes related to McDonough. Using Microsoft SQL Server, I constructed the entire database and implemented supporting stored procedures. This application was commissioned by the European Union to enhance government institutions and similar entities.

Additionally, I worked on financial-related stored procedures specifically related to Serbia Card, as part of a project for the USA.

We acted as a subcontractor for S&P within your company. I have extensive experience in SQL Server, particularly within the Microsoft environment.

They should think twice before they do anything and double-check. Definitely.

I have explored different options such as SonicWall and open-source solutions, but my preference lies with SQL Server. I find SQL Server to be fantastic, as it provides comprehensive functionality and makes tasks incredibly easy. 

Working with Postgres is also simpler compared to other databases like Oracle. Perhaps my familiarity with Excel has made SQL Server more intuitive for me. While I understand that Oracle is known for its complexity, I appreciate that its code and syntax bear similarities. 

Overall, I have a strong affinity for Microsoft products.

I would rate SQL Server a ten 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.

We're primarily using the solution for our health record system.

The use of a solution with SQL Server has helped standardize how we import, store, and report data. It is a standard that many applications use so we are able to buy pre-made solutions instead of having to develop a solution and the data can be moved from application to application easily.

The solution comes at a more effective price than Oracle. 

It's a little bit more advanced than using MySQL or NoSQL.

It's more prevalent in the industry than SQL Postgre.

The initial setup is mostly straightforward.

The product is scalable. 

The stability has been mostly pretty good.

There is a lot of information about the solution readily available online.

Every time Microsoft comes out with a new version, they like to move everything around. Updates are a bit intrusive. For example, it used to be in a certain place and then they update it, and now I can't find it.

Technical support could be better. 

I have been using SQL Server since version 6.4. I have used it with several different companies and help upgrade several versions.

With the versions we have, the solution is quite stable. That's one of the reasons we don't immediately download the latest version. We wait a little bit before we go to the newest version. We want to make sure it's very stable beforehand.

The solution is very easy to scale. We have between 300 to 500 people that use it. 

Microsoft's tech support is really hard to use. I would rather look outside of Microsoft for solutions. When needed we usually pay the one-time fee but only in rare instances where a deep dive is needed to isolate the issue.

Positive

SQL's been the main solution for this company. I have, however, used Oracle in the past with other companies.

The initial setup is pretty straightforward.

It can be complex depending on what you're trying to do, however, it has a good user base and user support groups, so there's lots of information. If you're trying to do something, likely somebody else has already done it, and you can usually find that information through a user group or a forum, or even on YouTube or Google.

Implementation was a joint effort with our team and the vendor team. Most of the vendor team was India based and was very low-level for best practices and security. We had to clean up a bunch of their generic implementations and correct code.

That is a complex question since there are too many variables that are outside the range of IT to answer.

The pricing is pretty decent. It's less expensive than Oracle. 

While the solution started out really reasonable, it's gotten a little bit more pricey, as Microsoft keeps changing how they want to license it.

Whether you're using it in the cloud or on-premise changes the costs involved. A lot of times it might be more cost-effective to do it in the cloud. Microsoft includes a lot of the licensing in the cloud.

The evaluation was based more on the applications and the solution that the business unit wanted to use which are easier to support if they all use the same database structure. The most common was SQL Server.

We're just a customer and end-user.

We're not using the latest version. We're probably one or two versions behind.

I'd advise new users that you want to know what you're going to use it for. I would say it's more suited to a more midsize or larger company than a mom-and-pop shop - unless they're tying it to some software that uses SQL.

I'd rate the solution at an eight out of ten.

Performance-wise, SQL cannot handle large amounts of data. In the next release, I would like them to commission SQL Server on Linux, as has been announced in the past but has not yet happened.

I've been using SQL Server for thirteen to fourteen years.

SQL is a highly unstable server - there are patch updates on the Windows server every week, which is why we only use it for non-critical systems. 

The initial setup was very easy - much, much easier than Oracle - and took about a day to complete. Microsoft is less demanding because everything is GUI, unlike Oracle, where you need to use command lines.

This is a very cheap product.

SQL's performance is good enough if you have a low amount of data. For those looking into implementing SQL Server, I would advise first analyzing your requirements and whether your system is critical or non-critical. If it is non-critical, go for SQL as it will save you in terms of cost, but if it is critical, avoid SQL as it will bring you down in one day. I would rate this solution as eight out of ten.

It has all of our data. Our company sells contracts when you buy a car. We sell aftermarket insurance for the tyre, wheel, ding, dent, windshield, etc. When somebody buys a contract, we capture all of that data into a legacy database PostgreSQL, and my task is to incorporate that into our financial platform using T-SQL. So, I write queries, procedures, and views. I use SSIS, and I use SSRS. My job is to get the data into our financial system so that we can process claims, payments, cancellations, and refunds. 

In terms of its version, we're up-to-date. We have version 2019.

This is the heart of the whole company. SQL Server is where all of our financials are. It has all of our data.

I've been using SQL Server for 20 years, and there is nothing that it can't do. It is awesome.

When we are talking about event space architecture, scalability generally comes into play. For example, I might have a hundred thousand transactions a second, and then all of a sudden, I build something that everybody in the world wants. The next thing I know is that I have a million transactions a second. So, to be able to process the throughput, I'd have to scale up, and then when the holidays are over, I'm again down to a hundred thousand transactions, and I want to scale back down. SQL Server is not going to do that. In this way, it is not very scalable. One of the reasons why they want us to use Kafka is so that if we need to, we can do that, but our base program is on SQL Server. So, this is where we would use a Kafka event stack so that if I need more servers, I can just write a command, and I can have more consumers, more brokers, and more producers, and when the holiday season is over, it scales right back down again. SQL Server is not going to do that.

I have been using this solution for 20 years.

We do clustering. If one SQL Server goes down, it automatically goes to another one.

I don't ever need tech support. If it breaks, I can just rebuild it.

They're now using a different database for contracting called Road Runner. I don't know what that is, and how it stores data. I don't know anything about it. 

There is also Postgres. I like SQL Server more than Postgres. That's only because I know SQL Server. I don't know Postgres as well. So, I can't say which one is better because I don't have the same amount of experience in both.

I can bring up a SQL Server in an hour or so and set it up.

In terms of maintenance, the number of people required depends on the need. 
We have a team of DBAs, developers, and UA analysts. We probably have 40 people in our IT area who are maintaining our solution. I'm just the developer. I'm the guy who makes the magic happen, but without other people collecting the information that I need to make the magic happen, I'm stuck. Without the guy who is an expert in permissions, partitioning, and performance tuning, I'm stuck. So, it's definitely a team effort. You can do it all, but you don't want to do it all because then you're running your head off, and you don't really get good at anything. It would be a jack of all trades, master of none type of scenario.

You will seldom find a database that was designed correctly. Just because you got a poor-quality database doesn't mean that you're going to get a better database anywhere else. You rarely get to build a thing on your own. Usually, you inherit somebody else's stuff. So, the challenging thing is working with what you have while trying to implement a better solution. My only advice is to be patient.

I would rate it a nine out of 10. I wouldn't give anything a 10 because I don't have that kind of knowledge, but right now, it does what I need it to do.

This is the main database for our financial system. I'm the IT manager and we are customers of SQL server. 

We've been using this solution for many years.

We're satisfied with the stability.

We have around 100 users. The database isn't used directly, so users are not even aware that there is a SQL Server underneath. 

There are some local companies that have direct relations with Microsoft. We use them regularly when we need some support.

I don't recall, it's been many years since we implemented this product. 

We pay a license fee, it could always be cheaper.

I recommend this solution and rate it 10 out of 10.