Select the best SQL Server version that meets Database Requirements

BKJIA quick translation] when I see this question, I don't think there is a definite answer!

The reason is that SQL Server has jumped from a simple desktop-based application to an important enterprise-level database management system product, but it still maintains the advantages of ease of installation and use. This is what I heard from users and professionals when I attended a discussion on SQL Server, but I didn't talk about how to best configure and maintain the best performance of database applications.

As a database administrator/developer/DESIGNER/System Architect, what is the optimal SQL Server version you have selected? I have mentioned similar issues at this Technical Education Conference. For example, "Can someone help me list the differences between Sever2008 Standard Edition and Enterprise Edition ?" The user only cares about the differences in installation. When asked why the operating system group does not select/supports the Enterprise Edition, the answer is: "The only difference is that the Enterprise Edition allows clustering", so the user will ask me, is clustering the only difference between Enterprise Edition and Standard Edition? This is a very serious problem and problem.

BKJIA editing recommendations: Special Topics: SQL Server 2008 deep application

Every time I suggest you refer to SQL Server 2008: Compare the Enterprise Edition and Standard Edition, you may agree with the list of differences I listed. SQL Server can maintain the scalability, availability, and performance of applications! In order to continue to answer questions about the differences between the Enterprise Edition and Standard Edition, I asked you about the most important features required by the application. The following lists the functions provided based on your feedback:

◆ The application code is optimized enough, and the database has been standardized according to the optimal method, but although a little resource memory and disk are added for the hardware), the previous version of SQL 2005 Enterprise Edition) the server still has performance defects. Therefore, my solution is to learn from the experience of Parallel Index operations in the Enterprise Edition, because it does not affect CPU performance: SQL Server uses the same algorithm to perform index operations, just like query operations) determine the number of independent threads to run in the degree of parallelism ). The maximum degree of parallelism of the index operation depends on the maximum degree of parallelism server configuration option. By setting the maxdop index option in the create index, alter index, drop index, and alter table statements, You can reset the maximum degree of parallelism for individual INDEX operations. The reason for selecting this option is that you only need to create an index query plan, create or recreate an index, or delete a clustering index, parallel and multi-threaded operations are allowed on computers with multiple processors. For more details, I suggest you refer to this article to estimate the Parallel Index configuration)

◆ Data growth in the next three years will be huge at least 80%), which may reach 2.5 TB, making it quite difficult to archive data, therefore, I chose to consider table and index partition storage. In previous versions, the index view was adopted to create a partition view or encapsulate a stored procedure, and the storage location of the data was pointed out. Another stored procedure was executed to read the specified partition, return the required dataset. Only the Enterprise Edition and the development edition of SQL Server start from 2005), allows the partition of a large amount of data, the data of a table is divided into multiple smaller, can be more effective management and maintenance. The application is used for production purposes, and the Development version is not a good choice. The Enterprise Edition has this ability to build segmented data and access it through a single access point, which reduces many management problems compared with the old method. A table/index partition table with a single access point name or index name can hide multiple data segments from the application code and allow administrators or developers to change partitions as needed, you do not need to adjust the code.

◆ The next biggest threat to application data is how to configure the data file size as the data volume increases day after day. In some cases, it is not enough to select the default value of 10%. Will cause application errors. My suggestion is that we can regularly compare the size of the data file. In some cases, we can select every 4 hours to see what is different ), this time benchmark and benchmark program will help you determine the appropriate value for the data file size and effectively optimize the data file size through the control mechanism.

◆ What users are interested in is whether they can give some suggestions. For how to monitor system execution using TSQL or GUI over a period of time, my answer is "Management Data Warehouse, it is the best feature in SOL2008.

The conclusion is that I chose the Enterprise Edition to implement the first two features. To configure the Management Data Warehouse, you can also use the development version. For more information about and comparison of SQL Server versions, see the differences between SQL Server versions and their selection. This article introduces SQL Server 2000, but it can also be used as a reference.

Original article: SQL Server Edition-which is the best one to choose for your database needs? By SQL Master

Read more]

1. Microsoft TechEd 2009 announces SQL Server R2's Christmas release
2. Topic: SQL Server 2008 deep application
3. Upgrading and deploying SQL Server 2008
4. Explain the differences and selection of SQL Server versions