Relational database field name design Are there design patterns for naming table fields? For example, I've always used user (table)> email (field), but I see other well-used modes like user (table)> user_email (field). Are there any rules / conventions to follow?
It doesn't really matter what naming convention you use, however it is really important to have one and stick to it. As long as you're strict about using it, you'll have a clean/readable database.

A couple of useful tips:


Using tbl_xx or v_ for tables/views might be a bad idea, cause tomorrow, you might change the view to a table or visa versa. Which could end up being really confusing a couple of years from now.
Try to give meaningful names to columns, for example an email field should not be named user_e, but user_email, or just email.
Correct use of underscores or capitalization, bigfieldbuthardtoread vs BigFieldButEasyToRead vs Big_Field_But_Easy_To_Read
Don't prefix procedures with sp_, can cause some performance issues (it will first look in the master for that sp)


If you don't want to make up your own system, you can always try to find one online and make that your own, for example this one