Firstly <a href="http://codebalance.blogspot.com/2011/07/20-database-design-best-practices.html">read this</a>.
- Adding a prefix is a much better idea. Using a schema is fine also. A prefix will separate transaction tables from lookup/static data table. Grouping tables that work together is a better practice.
2.I’m 50/50 on this. Tables have many records, a plural wont hurt.
3.D’Uh
4.Unnecessary prefix should be avoided but necessary and useful ones should be kept,
-
There is more to it than this. Use Google and get some good advice.
-
Use bigInts please.
-
Um no. That wont happen. A big int is 8 bytes and your varChar can be smaller.
-
No question ever has a yes/no answer ever. You will always want a third choice so choose an int now and save time latter. Using an int means all choice fields are of the same type, not matter how many choices.
-
OK. We have a winner
-
This better performance is a myth but generally a good idea.
-
This does not belong in the list
-
Actually do this for the highly used tables to spread out IO.
-
Do this for all databases unless you have one you can lose.
-
If you add a constraint you will need an index.
15 or use dbknow.com (coming soon)
-
Google this, there is a lot more to it, choosing the order of fields in the index is crucial
-
Or save money if you do not need it.
-
The database will do this for you. Never mind carry on
-
Huh. This is not helpful or correct.
20 Huh.