One of our senior developers has stated that we should be using a naming convention for stored procedures with an objectVerb style of naming such as (MemberGetById) instead of a verbObject type of naming (GetMemberByID). The reasoning for this standard is that all related stored procedures would be grouped together by object rather than by the action.While I see the logic for this way of naming things, this is the first time that I have seen stored procedures named this way. My opinion of the naming convention is that the name can not be read naturally and takes some time to determine what the words are saying and what the procedure might do.What are your takes on this? Which way is the more common way of naming a stored proc, and does a what types of stored proc naming conventions have you used or go by?
Stored procedure Naming conventions?
naming;database development;stored procedures
Look at it like this.  How are your methods organized in code?  By object, with the methods hanging off.MyObject.GetById(int)MyObject.Save()By having your stored procs mimic that naming, it will be much easier to see how they relate to your source code.MyObjectGetByIdMyObjectSave