For Day 11 of this series, I am going to talk about some of the basic things that you should consider from a hardware perspective when you are trying to increase the basic resiliency and availability of an individual database server. These are some of the first steps<\/span> you would take as part of designing a high availability solution for your data tier.<\/p>\n The basic principal here is to try to eliminate as many single points of failure as possible at the hardware and configuration level. I believe you should do these things regardless of what other high availability techniques you decide to use. When you are choosing components for a database server (as opposed to a web server, for example), here are some basic things to include:<\/p>\n Despite this fact, you will undoubtedly be pressured multiple times in your career, by different people, into not running SQL Server database backups for one reason or another. You really need to stand your ground and not give in to this pressure. There is an old saying: \u201cIf you don\u2019t have backups, you don\u2019t have a database\u201d.<\/p>\n I also want to note one configuration setting I like to use for database servers, to reduce their boot and SQL Server startup time. For a standalone database server, reducing your total reboot time has a direct effect on your high availability numbers. I always go into the BIOS setup for the server, and disable the memory testing that normally occurs during the POST sequence.<\/p>\n This will shave a significant amount of time off of the POST sequence (often many minutes), so the server will boot faster. I think this is pretty low risk, since this testing only occurs during the POST sequence. It has nothing to do with detecting a memory problem while the server is running later (which is the job of your hardware monitoring software). I am sure some people may disagree with this setting, so I would love to hear your opinions.<\/p>\n","protected":false},"excerpt":{"rendered":" For Day 11 of this series, I am going to talk about some of the basic things that you should consider from a hardware perspective when you are trying to increase the basic resiliency and availability of an individual database server. These are some of the first steps you would take as part of designing […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,19,35],"tags":[122,138],"class_list":["post-711","post","type-post","status-publish","format-standard","hentry","category-sql-server-hardware","category-sql-server-high-availability","category-sql-server-storage","tag-hardware-redundancy","tag-reliability"],"yoast_head":"\n\n