[h2_heading]What’s in a name?[/h2_heading]

We have all been there. Called in to look at an application having performance issues. One of the first things we do is take a look through the objects to familiarize ourselves with what data is stored in which entities only to find a lot of objects with the word TEMP in them.

Having a good naming scheme might seem like a trivial issue but when you have hundreds of tables and a vast number of them include the word TEMP this can mean different things to different people. Some SQL developers might read TEMP as the table is a temporary backup copy of a current table, needed only for a short time. Some BI developers might read the word TEMP as the data in the table is temporary and used as a staging table but the table object itself is needed for the application to work.

[h2_heading]Proper Object Naming Convention[/h2_heading]

When naming objects try to think about who might end up looking at the applications back end and chose a name to explain if the object is a temporary backup copy that can be removed after a certain time or if you mean the data in the table is temporary. By adding the word backup and a date or a change request number you can easily identify if something is needed or not which is much easier than just adding TEMP and leaving the next person to figure out what it is that you mean. If an object really is just temporary remember to drop it after it has been used and is no longer needed.

So the next time you are creating and naming objects think about having a Proper Object Naming Convention that you and all the developers use and make sure it is enforced.