SQL Server Review

Its use of hyper-threading causes stability issues, but the higher limits for storage and table management are valuable features.


Valuable Features:

  • Reliability
  • Transaction management
  • Its higher limits for storage and table management

Room for Improvement:

Improvement to synchronous replication. Currently Microsoft's Always-On implementation of synchronous replication is not truly synchronous, as it counts the data to be written to the slave node, when it is written to the LDF file, not when it is committed to the actual database. This cause a problem when you are load balancing transactions across synchronous nodes.

Use of Solution:

I have been using it for over seven years, including 2008 (5/10) and 2012 (6/10) versions. We also have an early release of 2016 (8/10) which I have tested, but it's not in our production environment.

Deployment Issues:

We deploy multiples of these servers now and it is all managed via PowerShell scripts and templates. It does not play nicely with hyper-threading, so we disable this now by default.

Stability Issues:

If there is flapping of Always-On database node, SQL Server will break the replication to the child nodes, and it requires manual intervention to restart replication.

Scalability Issues:

Currently no as we use our own load balancer to enable us to scale to any level.

Initial Setup:

A strong knowledge of AD is a must as well as the ability to decipher MSFT blog posts.

Implementation Team:

We did it in-house.

ROI:

Depending on how the product is used, it will take about 12 months.

Cost and Licensing Advice:

Chose your database based on traffic type and desired functionality not on initial cost.

Other Advice:

Take a look at the environment you plan to implement including the application and traffic model. Consider using Azure DB depending on your implementation requirements.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
1 visitor found this review helpful
1 Comment
AlbeezReal UserTOP 5LEADERBOARD

I suggest to engage with an expert in SQL Always ON configuration to address the issues as we have been using it for over 5 years and never faced such issues. Heart-beat Sync between two nodes of remote locations has a dependency on latency which must be less than 15-20 ms. Also review the processor model used for virtualization; sometimes the issue may be at the processor / hyper-visor level.

04 July 17
Guest
Sign Up with Email