I'm just going through an SP (sql2005) which has 101(!) sp_executeSQL calls. I think I'm going to scream...
Friday, October 05, 2007
That's not bad - try looking at a SP that calls sp_executeSQL for every record in a table (using a cursor of course...).
As you'd guess, the SP was taking a while to complete. I sped it up by replacing the cursor/sp_executeSQL with a relatively simple join.
The scary part is that the person who did it was 'teaching' Transact-SQL to a couple of other people in the group since he was the expert...
Tuesday, October 09, 2007
This topic is archived. No further replies will be accepted.Other recent topics
Powered by FogBugz