You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- I have tried the formatting and performance arguments, but they still aren't convinced.Rune Grimstad– Rune Grimstad2009-05-26 12:53:13 +00:00Commented May 26, 2009 at 12:53
- 5Actually, sql server can re-use the query plan whether you use parameters or not. I agree with the other arguments, but for most cases the performance argument for parameterized sql doesn't fly anymore.tnyfst– tnyfst2009-05-26 15:07:14 +00:00Commented May 26, 2009 at 15:07
- 1@tnyfst: it can reuse the execution plan when the query string changes for every combination of parameter values? I did not think that possible.John Saunders– John Saunders2009-05-26 16:29:32 +00:00Commented May 26, 2009 at 16:29
- 4The query plan will be reused if the query text is IDENTICAL to an earlier query text. So if you send the EXACT SAME query twice, it will be reused. However, if you change even just a space or a comma or something, a new query plan will have to be determined.marc_s– marc_s2009-05-26 18:44:04 +00:00Commented May 26, 2009 at 18:44
- 1@Marc: I'm not sure you are entirely correct. SQL Servers caching hueristics are a little weird. The parser is capable of identifying constants in the text and can convert the SQL string to one the uses parameters artificially. It can then insert into the cache the text of this new parameterised query. Subsequent similar SQL may find its parameterised version matched in the cache. However, parameterised versions aren't always used with the originaly SQL versions being cached instead, I suspect SQL has a zillion performance related reasons to choose between the two approaches.AnthonyWJones– AnthonyWJones2009-05-28 12:35:31 +00:00Commented May 28, 2009 at 12:35
| Show 4 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. python-3.x), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
default