Many times we come across situations where in due to inconsistent coding/naming standards it becomes very difficult to debug the code or to maintain the code in a long run. Especially from a maintenance standpoint it is very essential that we follow coding standards. A little extra effort/time for incorporating coding standards results in an easy to maintain code.

Defining and following Naming/Coding Conventions/Standards, helps in maintaining consistent standards accross Projects/Organization. During the process of implementing the changes/CR's/debugging, these standards make the life of developers/testers lot more simpler :-)



Here are few tips on coding standards.

• As soon as you drop a Task/Component/Transformation on the designer Name It.
• Use Standard Naming Conventions for every object in the package (Like Package, Task, Component, Transformation, Configurations, Checkpoint & Configuration files, Variable Names etc).
• Update the Descriptions for Tasks/Components/Transformations etc. Names & Descriptions will be helpful especially while debugging a package.
• Use meaningful names/phrases for Task Precedence Constraints and Output from each of the Components/Transformations within the Data Flow Task.
• Use Annotations with a brief Description/Write up at the Package level and also inside each of the Data Flow Task. This will be helpful from a maintenance standpoint and will server as a short documentation. 

This list is updated as & when there is something relevant & worth mentioning.