Quote Originally Posted by Hack
I understand and completely support the use, in general, of stored procedures over inline SQL, but there are times when inline SQL fits the bill nicely. An example would be a query that you would never need to change, like obtaining the next sequential record id. I fail to see the need to put something like that in a stored procedure.
Then you are giving direct table access to the user. If using windows authentication, then you are giving the username access to the table.

From there anyone with EXCEL can connect to the database and look at any record.

We develop HIPAA certified health processing software - that would be a breach of security. And since Windows security is the only security model permitted in our industry that's a fact (and also the only model that makes sense for use!).

So there is the need for a SPROC in the situation you just described.