Regarding the post "A lot of places require the use of stored procedures for data access, and use prefixes of sps_, spi_, spu_ and spd_ which potentially clashes with system procedures in SQL Server. Also, many times the stored procedure does an update or insert depending on what is necessary so spi_ and spu_ become confusing."

I use the prefixes upd_, ins_, and del_ for stored procedures that perform update functions.  To get around the conflict with system procedures that start with sp_, I use sel_ for simple selects.  This is very clear even to a non-programmer, and makes it easy to find procedures by their function.

Now if only Enterprise Manager would let us save sprocs in folders so we didn't have to scroll up and down a list with thousands of entries!