SQL Server Execution Plans - Red Gate Software

Chapter 7: Special Datatypes and Execution Plans
The number of operators involved does make this plan more complicated. It's worth
noting that the query without an index ran in about 2.2 seconds and in only 87ms with
a spatial index.
While these functions are complex and require a lot more knowledge to implement, you
can see that the execution plans still use the same tools to understand these operations.
That's the point I'm trying to get across here, not specifically how spatial indexing works
in all regards.
Summary
The introduction of these complex data types, XML, Hierarchical and Spatial, radically
expands the sort of data that we can store in SQL Server and the sort of operations that
we can perform on this data.
XML provides mechanisms for storage and retrieval of XML data and, as we covered
earlier in the book, with XQuery we can retrieve information from execution plans
directly from the procedure cache. The other data types don't have as profound an impact
on what you should expect to see in execution plans, but their use does introduce some
additional issues and concerns that you need to learn to keep an eye out for within
execution plans. However, as you can see, generating and interpreting the plan still uses
the same mechanisms and methods we've been working with throughout the book.
286