Best practice Name Convention when creating entities and attributes

By Ricardo Araújo on 7 Jul 2010
At least in entities and their attributes the Service Center Could force the best practice name convention 
J.7 Jul 2010

Should be in truechange(tm) imho, with ofcourse settings.

It would be great to enforce our developers to hold onto the name conventions.
Indexes naming should follow a standard aswell 

----------------------------------------------------------------------
Indexes:

All primary key indexes should be named in the following format:

PK_<Table name>

All alternative key indexes, clustered indexes and non-clustered indexes should be named in the following format:

<index type>_<Table name>_<2 digit incremental number>

All reference indexes should be named in the following format:

FK_<referenced table name>_<2 digit incremental number>_<Table name>

Where the table name matches the table or view to which the index is being applied. The index types are:
Primary Key – PK_
Alternative Key – AK_
Foreign Key – FK_
Clustered Index – IX_
Non-clustered Index – IX_

Examples:
• PK_Order
• AK_Product_01
• FK_AccountPhone_01_Account
• IX_ProductDetail_01