Kevin,

We currently have 5,746 items checked into the SQL/Procedures node of VSS. I have only
been at this position for 4 months, and I find it extremely daunting. Trying to find
out what procedures exist that already do what I need to do is an exhausting process.

Now, having said that, this is partly because of my limited exposre to the procs here,
and because there are so many, but I don't find using procs overall as daunting.

I know my preferecnes on this, but let me ask you, what are your pro's & con's on using
procs verses pass-through?

Thanks
K





>Sure, many admonish stored procs. There are also people who claim that .NET can't do data munging. Trying to lend respectability to a point, by demonstrating google hits, is pretty unsophisticated.
>
>I've found that in the 'academic' world, the number of people who advocate SPs is greater than the number who reject them. Not by a huge amount, but definitely greater. In client sites [i.e., outside of academia], I find that SPs are heavily embraced. Why do you suppose that is?
>
>
>I know of multiple installations that generate at least 3 stored procedures per table as a practice.
>
>I've read just about everything that you and JVP have said on the subject.
>
>On your last point, just because something is 'daunting' to one ascending the learning curve, doesn't mean it's not practical. If one is using some kind of managed methodology for doing so, the number [900, or whatever] will often be irrelevant.
>
>Kevin