|
|||||
|
I would like very much to have some of the currently cached plans saved so I can compare them to the newly generated cached plans after the restart. Why would I like to do that? There are several reasons: to be able to query the currently cached plans – I would like to work with the cached . . . → Read More: How to take a “snapshot” of your cached plans Note: Do not disable parallelism before understanding the mechanics of it and before testing the query performance. There are several ways to control the parallel execution of queries, i.e. you can use a hint within the query (OPTION(MAXDOP 1)), or you can set the “Cost threshold for parallelism” on the server level. Also, there is an . . . → Read More: How to interpret parallelism on your SQL Server As it was discussed earlier, the Hash bails and Sort warnings can actually cause a significant performance degradation in your SQL Server. The Hash Bails are explained in more detail here. When it comes to determining if you have hash and sort warnings in your system currently, you can run the following script: * keep in mind the . . . → Read More: Find out the Hash and Sort warnings on your server You have the following challenge: you have a large environment and you are making some changes to your schemas. You need to know what code will be affected by the changes and you have to make sure that nothing breaks. You can easily search the code within your databases by using the syscomments (or by using . . . → Read More: Find T-SQL in your report server Here is a good one – look at the operators and notice that one is at 304% and there is another one at 100%. . . . → Read More: SQL Server execution plan with 304% operator cost  |
 |
||||
|
Copyright © 2010 Feodor Georgiev's blog - All Rights Reserved |
|||||
|
|
|||||
