theres almost as many naming conventions as there are bacteria in the human intestine.
|generally I'd suggest find one that works locvally and stick to it.
whether that used CamelCase or underscores_to_separate words.
use obvious abbreviations (bear in mind soem SQL db's restrict the number of significant characters. table and column names shoudl be immediately obvious to the reader (not just the developer who made 'em up
some SQL shops prefer all lower case (avoids problems migrating table design from db to db as some are case sensitive, some aren't)
generally its good practice to avoid repeating the table name within the column defintions of that table, but good practice if the column is a foreign key
generally give table names the plural of waht they hold. so for student data use table: students
no syntactical reason just it looks ugly
to my mind looks fugly.. its over fussy
select students.student_id, students.students_forename, students.students_lastname from students
when you join tables its even worse
select students.id, students.forename, students.lastname from students
I'd rather be riding on the Tiger 800 or the Norton