October 27, 2010 at 10:09 am
Looking at the Actual Execution Plan of the query may not tell you the internals of what the UDF is doing, but it should give you an idea of how much the join is costing you relative to the batch. If that doesn't help, or if you determine the UDF is the bottleneck, then try pulling the SQL out of the UDF and constructing a simplified version of the query that returns the same columns but joins straight to the tables. Sometimes deconstructing a problem one level at a time helps identify the solution.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
Viewing post 31 (of 30 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy