Timeline for Procedure showing different duration / reads in Profiler vs. SSMS
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 14, 2016 at 17:47 | history | edited | Aaron Bertrand |
edited tags
|
|
| Nov 18, 2014 at 16:17 | history | edited | Geoff Bowden | CC BY-SA 3.0 |
added 8 characters in body
|
| Nov 18, 2014 at 16:13 | history | edited | Aaron Bertrand | CC BY-SA 3.0 |
added 12 characters in body; edited title
|
| Nov 18, 2014 at 16:01 | history | edited | Aaron Bertrand | CC BY-SA 3.0 |
deleted 14 characters in body
|
| S Nov 18, 2014 at 16:01 | history | suggested | LowlyDBA - John M | CC BY-SA 3.0 |
formatting :)
|
| Nov 18, 2014 at 16:00 | answer | added | Aaron Bertrand | timeline score: 2 | |
| Nov 18, 2014 at 15:59 | comment | added | Aaron Bertrand |
Possibly the two executions are getting different plans, maybe because there are different set settings, or you have a different default schema (you really should say exec dbo.SM_SP...). Who/what is running the instance of the procedure that is getting captured by trace?
|
|
| Nov 18, 2014 at 15:51 | review | Suggested edits | |||
| S Nov 18, 2014 at 16:01 | |||||
| Nov 18, 2014 at 15:48 | history | asked | Geoff Bowden | CC BY-SA 3.0 |