Timeline for Code creates different plan when ran ad-hoc vs. in a stored procedure
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 3, 2022 at 16:43 | history | edited | Hannah Vernon♦ | CC BY-SA 4.0 |
improved formatting, removed unnecessary commentary (i.e. edit <xxx>), corrected spelling of optimizer to match that used by Microsoft in their documentation.
|
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Oct 14, 2011 at 11:09 | history | edited | gbn | CC BY-SA 3.0 |
after chat testing
|
| Oct 12, 2011 at 1:55 | history | edited | gbn | CC BY-SA 3.0 |
added 822 characters in body
|
| Oct 12, 2011 at 1:50 | history | edited | gbn | CC BY-SA 3.0 |
added 822 characters in body
|
| Oct 5, 2011 at 18:23 | history | edited | gbn | CC BY-SA 3.0 |
added 1397 characters in body
|
| Oct 4, 2011 at 17:17 | vote | accept | msgisme | ||
| Oct 4, 2011 at 16:53 | comment | added | Nick Chammas |
Re: point 3. You can also run the statement with OPTION (RECOMPILE) or the whole proc WITH RECOMPILE to force SQL Server to disregard existing plans.
|
|
| Oct 4, 2011 at 16:38 | history | edited | gbn | CC BY-SA 3.0 |
added 139 characters in body
|
| Oct 4, 2011 at 16:13 | history | answered | gbn | CC BY-SA 3.0 |