714 reputation
418
bio website petermcclymont.blogspot.com
location Auckland
age 35
visits member for 2 years, 4 months
seen Oct 21 '13 at 2:38

Commercial C# Developer. Experience with WPF / Winforms / ASP .NET / Silverlight / Design Patterns / OO.


Dec
10
awarded  Popular Question
Nov
29
awarded  Yearling
Nov
5
awarded  Popular Question
Oct
20
awarded  Popular Question
Oct
1
awarded  Popular Question
Aug
26
awarded  Notable Question
Aug
15
awarded  Notable Question
May
31
awarded  Popular Question
Mar
17
awarded  Popular Question
Mar
1
awarded  Popular Question
Dec
17
revised Working Around Filtering Problems in Merge Replication
added 19 characters in body
Dec
17
revised Working Around Filtering Problems in Merge Replication
added 354 characters in body
Dec
17
accepted Working Around Filtering Problems in Merge Replication
Dec
17
answered Working Around Filtering Problems in Merge Replication
Dec
4
accepted Estimated versus actual query plan with function calls
Dec
4
comment Estimated versus actual query plan with function calls
Thanks. I have brought it up with microsoft on the connect website. I think it could be inlined, but I am not 100% sure. Thanks for your help. SQL Sentry Plan Explorer looks interesting.
Dec
4
comment Estimated versus actual query plan with function calls
So in your opinion is the query I am profiling a bad query based on the fact that it calls the function for every row returned. This query comes from sp_MSsetupbelongs and so I am surprised that MS would create a query like that. That query has caused a performance issue in merge replication for us. This is the conclusion I came to by using profiler as I described.
Dec
4
revised Estimated versus actual query plan with function calls
added 121 characters in body
Dec
4
revised Estimated versus actual query plan with function calls
added 142 characters in body
Dec
4
revised Estimated versus actual query plan with function calls
deleted 374 characters in body