Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Final say: Field Naming Convention
Message
From
24/01/2002 08:46:22
 
 
General information
Forum:
Microsoft SQL Server
Category:
Database design
Miscellaneous
Thread ID:
00608378
Message ID:
00609633
Views:
23
>1) Column names should be fully qualified whenever possible for future scalability and performance reasons. Yes, it's tedious to always add the server.tablename prefix, but if you ever have to connect to another database and/or server, it will be INSTANTLY beneficial. Plus it's self-documenting. This eliminates the need to prefix column names with abbreviations (and removes the potential for running out of two & three-letter combinations).

I use a column prefix because it avoids a name conflict (SELECT customer.fullname, salemen.fullname ...) without changing field names with the AS clause. Plus, when you get in the resulting cursor, it becomes easy to know where that field came from (cuFullname, slFullname).
Sylvain Demers
Previous
Reply
Map
View

Click here to load this message in the networking platform