New answers tagged naming-convention
The default roles all have db_ and then something descriptive of the roles permissions. I would stick with that.
You can skip table name prefix in the status column, You can have all the tables with same column name and same datatype, that will make your naming uniform through out the tables in the database I have seen Database with 2000 of tables, and most of them have column status with same datatype. TINYINT in our case. Let say a query. SELECT ...
This could become confusing - but it's not difficult to make it work if you really wanted to. Say you had two tables, TASK and PROJECT. If both tables have fields called status and id, you can still access them without conflict by referring to them as either TASK.status or PROJECT.status. E.g: SELECT TASK.id, TASK.status, PROJECT.id FROM TASK, PROJECT WHERE ...
Top 50 recent answers are included