March 8, 2011 at 4:51 pm
Captain Proc, they've hit us in the injectors...
(In my best William Shatner:)
"DYYYYYYYyyyyyynaaaaaamiiiiiicc!!!!!"
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
March 8, 2011 at 10:27 pm
Rich Yarger (3/8/2011)
Who? My report writer? LOL! Nah - he thinks I'm a pain in the ace.I wish I had better news on that front - still pushing for it, but actually - this is pretty good news too in an of itself. My manager determined that - in fact - they were using...
DYNAMIC SQL!
So - guess what? They are going to redo their factories with sp_executesql. Now if I could only get them to do away with SELECT * from their factories, I wouldn't have to shoot them!
Just beware. Using sp_executesql doesn't mean that the queries will be parameterised. They can parameterise them, does not mean they will.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 8, 2011 at 11:07 pm
Gail, thank you so very much for all of your wisdom in this particular scenario. I will do my best to give them the best practices to go with, and then it's really up to them.
Thanks again, and I will let you all know how this pans out!
Rich
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply