Brandie Tarvin (1/23/2015)
Have you tried recreating the proc without the versioning? (I.E. without the "; 1") and then executing it through your code that way? Then see if it still continues to cause this issue?Yeah, I know it doesn't answer your initial question, but I am curious if it does really make that much of a difference.
It wasn't created with ;1 in the first place. I wrote the SP and didn't even know about versioning until this issue came up. The versioning is applied by SQL server by default.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St