I'm re-writing a couple of different Web-based apps using techniques I've learned over the past year, one of which is using stored procedures for increased scalability and security.

My question is: Is it overkill to convert [u]every single</u> query in my apps to stored procedures? That's my current goal, but I wonder just a bit if it's necessary for the smaller queries.

For a web app, I'd put them all in stored procs. It may seem like an overkill, but it adds a layer of security because your SQL is now on the backend, protecting the db schema.

Cool, thanks. It's good to know I'm not over doing it.

Any thoughts on what I'll see in terms of increased responsiveness and scalability as a result of these efforts?

Using Stored_Procedure increases the performance and scalability. If we use it, DataBase will not have to convert the query in a way which it can understand. Procedure takes less time.

It also add to the maintanence aspect of it. Suppose you don't convert all of the queries and leave some simple ones in some pages, then some table structures change(they shouldn't) or you need to pull different data. Now you would have to change the sql on every page. With SPs, you just change the code in one place.

Jim