SQL Server Review

We've measured notable performance improvements with this solution


How has it helped my organization?

There was an online system in which we had about 2500 requests to the DB per second. Every request had a completion window of one second to process and retrieve data. Before my arrival, the numbers were 1000 requests per second and two, and sometimes, three to five seconds spent per request.

After switching to SQL Server, and AlwaysOn, and Snapshot, and tinkering, and configuring and tinkering, the handling capacity we measured increased to about 5000 requests per second, while the time decreased to 0.5 seconds per request.

What is most valuable?

The AlwaysOn high-availability feature is the most valuable feature of SQL Server to us. This is because of the relative ease of the configuration, rather than configuring for OLTP-OLAP distinction.

What needs improvement?

As a software developer, it can be hard to do something in Oracle that is SQL Server specific, and vice-versa, sometimes.

Improvements must not be stopped and must not end. When business needs arrive, then the improvements follow. For example, 15-20 years ago, MySQL did not have built-in Stored Procedure support; there was no business need for MySQL to have stored procedures built-in.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

One stability issue I encountered was the deadlocking between calls to the same resources (tables, etc.). That was solved by row versioning. (We were shooting ourselves in the feet).

What do I think about the scalability of the solution?

No scalability issues.

How is customer service and technical support?

I have never had the need to reach out to the vendor.

Which solutions did we use previously?

Yes I did use another solution previously. The switch was mainly for the performance. Secondly, it was for the technology compatibility.

How was the initial setup?

It was very straightforward. There was no complexity which I couldn’t handle.

Which other solutions did I evaluate?

I’m not a "product" fan. I try to use "the" product which will comply smoothly with the software I’m working on.

What other advice do I have?

I’ve been working on Microsoft SQL Server since 2005, and currently I’m using SQL Server 2014 in my development environment and SQL Server 2012 in the production environment.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email