Timeline for Can comments in stored procedures cause problems
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2017 at 3:39 | history | edited | Evan Carroll |
edited tags
|
|
| Apr 20, 2014 at 17:37 | comment | added | Mikael Eriksson | It could be as simple as a bad execution plan due to parameter sniffing that sorted itself out on the recompile that happened after you modified the stored procedure. | |
| Apr 20, 2014 at 8:31 | history | tweeted | twitter.com/#!/StackDBAs/status/457798659317694464 | ||
| Apr 17, 2014 at 0:59 | history | edited | TtT23 | CC BY-SA 3.0 |
added 60 characters in body
|
| Apr 16, 2014 at 13:25 | comment | added | Jon Seigel | It may not be related to this problem, but I'm going to throw in this link to one of my blog posts because IMO block comments should be used as a standard practice anyway. voluntarydba.com/post/2012/09/18/… | |
| Apr 16, 2014 at 12:35 | answer | added | Michael Green | timeline score: 2 | |
| Apr 16, 2014 at 5:46 | comment | added | user1822 |
I have seen situations where such comments caused trouble (it's been a while, can't recall the exact circumstances). After using block comments /* ... */ instead of line comment things were OK.
|
|
| Apr 16, 2014 at 4:32 | history | edited | TtT23 | CC BY-SA 3.0 |
added 53 characters in body
|
| Apr 16, 2014 at 4:18 | history | asked | TtT23 | CC BY-SA 3.0 |