Đang chuẩn bị liên kết để tải về tài liệu:
Brad’s Sure Guide to SQL Server Maintenance Plans- P42

Không đóng trình duyệt đến khi xuất hiện nút TẢI XUỐNG Tải xuống

Brad’s Sure Guide to SQL Server Maintenance Plans- P42: SQL Server has a reputation as being a simple database application to install, configure, and maintain. This is a little misleading. SQL Server is a powerful relational database that can handle the needs of the largest organizations and, as such, its proper maintenance almost certainly requires the attention of an experienced DBA. | Chapter 17 Configuring Maintenance Tasks Using the Designer Figure 17.3 We have seen this database selection screen many times before. For the purposes of this demo select the AdventureWorks database and then click on OK. The Check Database Integrity Task screen should now look as shown in Figure 17.4. Figure 17.4 A specific database AdventureWorks has been selected although we can t see the database name from this screen. Now that a database selection has been made the Include indexes option is available which is checked by default and means that both tables and indexes will be included in the check. As discussed in Chapter 5 this makes the task a little more resource-intensive but in most cases 1 recommend you leave it checked. 206 Chapter 17 Configuring Maintenance Tasks Using the Designer You have probably noticed a button on this screen that you have not seen before namely the View T-SQL button. When you click on it you get to see but not modify the T-SQL code that will be run when the task executes as currently configured see Figure 17.5 . Figure 17.5 The Maintenance Plan Wizard allows you to view the T-SQL that will be run for each maintenance task. If you re unfamiliar with T-SQL then this screen isn t much use to you but most DBAs like to understand what T-SQL will be executed when they run a given task. Notice however the warning under the T-SQL code indicating that the T-SQL you see may not be the exact T-SQL that is actually executed due to the potential inclusion of further conditional logic that could alter the T-SQL that is executed or mean that it is not executed at all. We ll cover this in more detail in Chapter 18 but suffice to say that the only way to really know what T-SQL was run for a particular task is to check the text file report that is created after a Maintenance Plan executes see Chapter 3 . When you return to the design surface you ll see that the Check Database Integrity task looks slightly different as shown in Figure 17.6. Figure .