Tables:- Tables represent the instances of an entity. For example, you store all your customer information in a table. Here, 'customer' is …show more content…
Otherwise, both stored procedures and UDFs are similar. So, the naming conventions discussed above for stored procedures, apply to UDFs as well. You could even use a prefix to logically group your UDFs. For example, you could name all your string manipulation UDFs as shown below. str_Make Proper Case str_ParseString Triggers:-Though triggers are a special kind of stored procedures, it won't make sense to follow the same naming convention as we do for stored procedures. While naming triggers we have to extend the stored procedure naming convention in two ways.Triggers always depend on a base table and can't exist on their own. So, it's better to link the base table's name with the trigger name. Triggers are associated with one or more of the following operations: Insert, Update, Delete. So, the name of the trigger should reflect it's nature.
So, here's how I would name the insert, update and delete trigger on titles tables. titles Validate Data_instrg