Hi Craig,

Can you expand on your reasons for not having unique names on fields. Is it purely for readability or is there some other motive?

>As Mike said, there are no standards. IMO, it's a waste to do field naming as Mike described, but he has his opinion of how to do it and I have mine. The only convention I use is for the PK, where I use PK+table, so for example, PKEmployees. That same field name is then used in all tables that need a foreign key into the Employees table. For example, in a Sales table, you might see something like PKSales and PKEmployees.

>>Does anyone have a link or recommendations on standard naming conventions for SQL server tables, fields etc?
>>
>>I have seen plenty of recommendations but everyone seems to have a different take on it. I guess I am looking for some "industry standard" conventions (if there are any.)