While coding with sqlite everytime i always had the exact number of parameters and when i executed the query i always had 0 parameters after it. I kept using the cmd object and it worked fine.
Now while porting to use sql server (2008) my SqlConnection has parameters left over from a successful command. Why? I seem to be able to create tables without the problem (then again i may have use a clone of an empty cmd since i use recursion). Does SqlCommand always leave the parameters in after a query? This always breaks the following query unless i do parameter.clear().
Should i create a new SqlCommand object? or use parameter.clear() each time? I’m somewhat confused.
Sure it leaves those there – you never told it otherwise.
What if you need to call the same SqlCommand hundreds of times in a row – do you want to keep re-creating all the parameters after each call?? Doesn’t make a lot of sense to me….
My advice: use one SqlCommand per “command” or “query” you want to execute and set up its parameters as needed. I wouldn’t “recycle” a single SqlCommand for a dozen different queries… just create a new one! That’s definitely not an expensive operation.