![]() In addition to the optimizer version being different the compile timings are different and some of the estimated values are different. The first thing we can see is that the Cardinality Estimation Model Version (second value from the top) is different for the two plans: 130 for the SQL Server 2016 optimizer and 70 for the SQL Server 2008 Optimizer. ![]() When the Showplan Comparison tab is initially displayed the SELECT operator is selected and the Properties window shows the execution plan properties for the SELECT operation (overall query). Both queries are based on the AdvnetureWorks database. In the following example we compare a SQL Server 2008 execution plan with a SQL Server 2016 execution plan. sqlplan file by right clicking on the plan and selecting Save Execution Plan As. You can save a query execution plan to a. On selection of the Compare Showplan option a file manager dialog will open enabling you to navigate to a saved query execution plan. The new Compare Showplan tool is available by right clicking on a query execution plan in SSMS: In some cases we may find that one server has more CPU or memory resource, or faster disks or logical volumes with more disks in a RAID volume, but differences will also often come down to database version (or compatability version) and optimizer differences. Frequently we can find that a query runs faster on one SQL Server instance than another and it can be quite puzzling as to why when on the surface the servers and software appear to be configured identically.
0 Comments
Leave a Reply. |