For the database server configuration storage and memory
With the server hardware become more powerful, while prices had dropped sharply, many companies (especially small companies) found that the database server is now faced with many choices to buy. This means that the relative lack of experience, database administrators have also been asked to design more powerful system. Your system design for large-scale database systems, can buy a lot of large hard drives and ample memory, the database server. The following is to design a system you should observe some basic principles.
Keywords:
With the server hardware become more powerful, while prices had dropped sharply, many companies (especially smaller companies) to buy now found in the database server faces many choices. This means that the relative lack of experience, database administrators have also been asked to design more powerful system. Your system design for large-scale database systems, can buy many hard drives and ample memory, a large database server. The following is to design a system you should follow some basic principles.
storage system that people in the design of disk arrays is the most common mistakes, only the calculation of the required spare capacity. Idle capacity storage subsystem is designed to consider when part of it; the other part is the storage system needs to support the input / output number of operations.
a basic principle to be observed is that the database write the best use of frequent RAID 10 arrays, while read operation is usually best to use the database frequently RAID 5 array. The reason is that, if the data is written to RAID 5 array, the performance will be affected. Because the data written to RAID 5 array, the storage system must be in writing before the data to calculate parity bits, while the calculated parity bit will take a long time, which means that write performance of RAID 5 array will be reduced.
Because of this performance impact, we always recommend that you should put the transaction log into RAID 10 arrays. Transaction log is always very frequently write documents, regardless of the database is read-oriented database, or to write the main database. tempdb database should also be placed on RAID 10 array, specifically with the transaction log files are located on a different array to another RAID 10 array.
partition on each disk array, it shall ensure that the partition is aligned correctly. By default, Windows 2003 and the following version of the partition is not aligned properly, which causes the disk subsystem not reach the ideal level of performance. Utility by using diskpart.exe (Windows 2000 in diskpar.exe) create a partition to resolve this issue. This creates the alignment offset for each partition should be 64kb; in default, created its alignment offset for each partition is 32kb. By default, Windows 2008 partition that created their alignment offsets to 128kb.
physical database construction
Microsoft recently recommended a relatively new technology is, for two to four CPU core which each of the core, the database should be a physical database file. Should be set for each file inside the database to do this.
If your server has two quad-core CPU, then a total of eight core. We assume a database with two file groups, one called Data, another called Indexes. Then each file group should have two to four physical files. This technology allows SQL Server to disk input / output optimization. If possible, you should try to spread files for each storage array in the paper as little as possible.
tempdb database configuration to be a bit different. Configure tempdb database, it is recommended for each CPU core, the database should be a physical file. This system can be thought tempdb database to speed up input / output operations. Like the user database, put the files on each disk array should be as little as possible.
you in the database should always be at least two file groups. The first file group including the table, the second group, including the index. You need to file them in different groups, so check the index, the load to the operating table will not be affected, and vice versa.
system memory in the past, buying only a few GB of memory installed on the database server is quite common. This is because the price of memory is still very expensive.
Today, memory prices are very cheap; as long as you can accept the deregulation, should buy as much memory. The more memory, speed of the database is almost always faster. Exception is, if you install the database memory more than Colonel, for example, if you have 3 GB of database size, but the installed 8GB of memory, then add more memory for the server to enhancing the performance of the database does not help, because the SQL Server may have been able to load the entire database into memory.
in the decision to allocate how much memory SQL Server is definitely not to allow SQL Server to have all the memory allocated to it. Because the Windows operating system requires memory to run, installed on the database server needs of any other memory to run the same software, such as backup software and antivirus software. Recommend leaving one or two GB of memory for the operating system and other software used. The amount of memory depends on what software is installed.
because no two database servers are the same, so there is no clear principles and rules of your hardware solution should look like. You have many options; wants to design a future use and reliable solution for many years, the key is to understand your database needs, understand their own hardware, to understand what links these needs have been met in order to buy right now and neither made the hardware configuration is too low, and no purchase is too high for the next year in terms of hardware configuration. Editor: Yang Kun Contact Email: yang_kun@cnw.com.cn more for businesses, data security is extremely important, these three data storage means, and how the real situation of the enterprises themselves according to select the appropriate data storage model .