The default is 16, with a valid range of 1 to This value is used to determine the amount of directory information that can be cached by the client. Increasing the value can reduce network traffic and increase performance when large directories are accessed.
The default is , with a valid range of 1 to This value is used to determine the amount of file name information that can be cached by the client. Increasing the value can reduce network traffic and increase performance when a large number of file names are accessed. The default is This parameter limits the number of outstanding requests on a session. Increasing the value can use more memory, but it can improve performance by enabling a deeper request pipeline. Increasing the value in conjunction with MaxMpxCt can also eliminate errors that are encountered due to large numbers of outstanding long-term file requests, such as FindFirstChangeNotification calls.
This parameter does not affect connections with SMB 2. This parameter specifies the maximum number of files that should be left open on a shared resource after the application has closed the file. The general tuning parameters for client computers can optimize a computer for accessing remote file shares, particularly over some high-latency networks such as branch offices, cross-datacenter communication, home offices, and mobile broadband.
The settings are not optimal or appropriate on all computers. You should evaluate the impact of individual settings before applying them. Registry-only settings can be configured by using Windows PowerShell as well. The service descriptions identifies those that should be in Manual vice Disabled. Me Features: Windows Service Configurations! Includes explanations of each service and advice on which services you can safely disable.
Windows 10 Services Windows 8. Application Management. Automatic Updates. Background Intelligent Transfer Service. Computer Browser. Distributed Link Tracking Client. Distributed Transaction Coordinator. FTP Publishing Service. IIS Admin Service.
Indexing Service. Internet Connection Sharing. Logical Disk Manager. Logical Disk Manager Administrative Service. Windows Professional Retail [Trad Chinese].
Windows Professional Retail [Turkish]. Windows Professional Select [German]. Windows Professional Select [Korean]. Windows Professional Upgrade. Windows Professional with SP4 Retail. Windows Professional with SP4 Select. Windows Professional with SP4 [Norwegian]. Windows Professional with SP4 [Spanish]. Windows Server. Windows Server Retail [Italian].
Windows Server Retail [Smp Chinese]. It will show you, step-by-step, how the Query Optimizer executed the query. The execution plan should be read right to left, as the right part of the plan indicates the first step taken by the Query Analyzer, and you continue reading the plan, from right to left, until you get to the left side of the screen, which indicates the very last step taken by the Query Analyzer.
While the graphical representation of the execution plan is interesting, the most useful and powerful part of this tool is somewhat hidden.
If you move the cursor on top of each of the steps in the query plan, a pop-up box appears with detailed information exactly what the Query Optimizer did in each step as the query was executed. The information displayed in the pop-up box is sometimes obvious, such as telling you that a "Clustered Index Scan" was performed, or it may very obscure, such as the "Subtree Cost" was. The details provided not only often need further explaining, they need interpreting. The explanations can be found in the Books Online, but the interpretation takes experience using and performance tuning SQL Server, a topic beyond the scope of this article.
If the query you are working with takes a long time to run, and you want to experiment with your query, you don't have to actually run the query each time. Query Analyzer also has an option to create and display an Execution Plan without actually running the query. This option is also available under the Query menu, and it is called "Display Estimated Execution Plan". When this option is selected, the Query Optimizer creates and displays the execution plan, but does not actually run it.
Notice that this is referred to as an "estimated" execution plan. This means the resulting query plan may not be the exact one the Query Optimizer will use if the query is really run.
It will be close though, and it is a good tool if you are doing a lot of experimenting with long running queries. Once you have the query fine-tuned using this feature, you can turn it off and then run it for real, and see how it actually performs. This is the same type of information that is captured by the SQL Server Profiler, described later in this article. The main difference is that you only see the communications to SQL Server that are instigated by the query or script you are running in Query Analyzer.
The Show Server Trace feature can be turned on from the Query menu on the main menu of Query Analyzer, and must be turned on before the query is executed. Once the query is executed, the results of the trace are displayed in a new window available from a tab that appears below the query results window on the screen.
The results of the trace are in the form of rows, with each row representing a distinct communication from Query Analyzer to SQL Server.
Each row includes the text of the communication, such as Transact-SQL code; the Event Class, which describes the type of communication being sent; the duration of the communication; the amount of CPU time used, and how many reads or writes that were performed for the event.
This information can be very valuable when analyzing query performance, and when comparing the performance of one variation of a query against another.
Show Client Statistics Like the Show Server Trace feature, the Show Client Statistics can be very helpful when performance tuning queries, stored procedures, and scripts. What this option does is provide you with application profile, network, and time statistics of whatever Transact-SQL you are running in Query Analyzer.
This statistics provide additional information you can use to see how efficiently a query is running, and also allows you to easily compare one query against another. The Show Client Statistics feature can be turned on from the Query menu on the main menu of Query Analyzer, and must be turned on before the query is executed.
Once the query is executed, the results of the trace are displayed in a new window that is available from a tab that appears below the query results window on the screen. The results of the Show Client Statistics feature are a series of three tables, each containing a set of statistics on how the query performed. For example, some of the statistics include:. These statistics can be valuable roadmaps to how a particular query is running, helping you to diagnose performance-related problems.
Manage Indexes The SQL Analyzer Manage Index tool is not designed to help you diagnosis performance, but it allows you to easily experiment with your table's indexes as you are fine-tuning your queries using the other tools we have already described.
The Manage Indexes option is available from the Tools menu, and allows you to add, edit, or delete indexes on any table. This way, you can experiment with indexing, and test your indexes, all in one central location. Manage Statistics Without you doing anything, SQL Server automatically creates and maintains internal statistics on the rows of data in all of your tables.
Most of the time, SQL Server does a fine job of maintaining these statistics, and the Query Optimizer has the necessary information it needs to do its job. This tool, available from the Tools menu of Query Analyzer, allows you to modify how SQL Server automatically creates and maintains statistics. You can add, edit, or delete the various statistics maintained by SQL Server. And because this tool is available from the Query Analyzer, you can experiment with different sets of statistics and see how it affects the query optimizer's execution plans.
Selecting the proper statistics is a difficult task, and your time would most likely be better spent elsewhere performance tuning SQL Server. Index Tuning Wizard for Individual Queries A little later in this article you will learn about a tool called the Index Tuning Wizard, which can be used to recommend optimal indexes for an entire database.
But for now, you need to know that the Index Tuning Wizard can also be run from the Query Analyzer and be used to recommend indexes for specific queries.
0コメント