In this article we discuss several options for scaling up a SQL Server implementation
The most common problem that arises while working on SQL Server is the storage problem. Often due to lack of space, the operations become slow leading to reduced efficiency. But scaling up your SQL Server is not a very difficult task, and it can be done in more ways than just enhancing your existing hardware. Scaling options available for SQL Server include ‘Scaling up’ and / or ‘Scaling out’ (using multiple SQL servers). The emphasis of this article will be on scaling up, which means using a faster CPU, clearing the existing Storage and adding on to the Memory.
If your system is running on low memory, then scaling your SQL Server is easy, you will have to lighten your pocket a little and add on to the memory. Buying new memory for an old system is often expensive, but when the options are limited, you will have to go for it, no one can afford the productivity to suffer due to slower systems. If you have already added memory to the maximum capability of your server, and there are no more memory slots left, then you have no option but to use an upgraded server, with more memory slots.
If you have used only one of your CPU socket then scaling up a server is no problem, you can go on scaling up to a four-socket tier. If all the four sockets have been used and you are looking for more sockets, then you will have to shed a lot of money. A server with eight CPU sockets is double the amount of server with four CPU sockets. To scale up your CPU always use servers with modern processors, opt for four socket server instead of a two socket server and an eight socket server over a four socket server. If you fall short even with an eight socket server, opt for a monster. Do note that SQL Server editions of 2008 and later, require a DataCentre edition of SQL Server for each socket, if you need a server with more than eight sockets.
It is often believed that whenever you are short on storage, you should use devices with greater storage capacity. This does not work for all systems, you might use enhanced storage device and still be working at snail’s pace. The easiest solution for low storage is to work on code improvements by involving more man power instead of spending on acquiring new storage devices. Performance tuning instead of purchasing more hardware is always more beneficial and cost effective. But that is usually kept as a secondary solution instead of a primary resort.
A highly optimized, top of the line SQL Server implementation too can fall prey to a SQL crash
SQL crashes can happen in nearly every SQL Server implementation and even a top of the line hardware stack cannot always prevent their occurrence. The best defense against a SQL crash involves investing in a sql recovery tool like DataNumen SQL Recovery to prevent data loss. This remarkable tool can ensure that you do not lose any records due to the crash and all data including those entered after the last backup is retrieved in perfect shape.
Alan Chen is President & Chairman of DataNumen, Inc., which is the world leader in data recovery technologies, including access recovery and sql recovery software products. For more information visit https://www.datanumen.com/