Other reasons why they are not used:<br>4. A huge pain to debug<br>5. Not portable (this might be a big deal if you need to support multiple databases in which case it'll mean having the multiple versions of the same procedures for every database that needs to be supported).
<br>6. Some developers simply don't want to add another layer and another language in the mix (because their projects are complex enough without the extra stored procedure headaches).<br><br><br><div><span class="gmail_quote">
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Why don't more people just use Parameterized Stored Proceedures? Is it
<br>> because there are implimentation issues or because people don't know<br>> about them? Whats your opinion?<br><br>I wonder that too. Also, why don't people just not write integer overflows?<br><br>With the snark bit cleared, I'll point out: lots of projects use
<br>stored procedures, but have some patches of functionality (like query<br>builders) that are easiest to write with raw SQL.<br></blockquote></div><br>