Well guys this may be the wrong place but an earlier post by an
"expert" about how a table was poorly designed has piqued my interest.
The question is this. What are the do's and don'ts of sql development?
Please list what you consider to be good and bad practices in general
and/or specific or list links to resources that would be considered
under this topic.
When I consider best practices myself of course there is always the
standards of 3nf and such but what about when it comes to standard
table structures and field sizes for say a Name (first, last, etc) and
contacts table. What about naming conventions and common entities and
structures.
It seems to me that every SQL Developer that enters this field starts
out with the basics of how the technology works and a little of the
practices. Yet from there I see many different directions that they
go.
To start this conversation out let me propose some things that I have
questions about. Feel free to expand and add to this list.
1. What would you consider the standard/best way to represent a
gender.
2. Field Size for Names and address First/Last Etc.
3. Include or don't include City/State in an address/contact list.
4. Structure of a Generic Contact list.
5. Practices for dealing with pictures and documents as well as
related table structures.
6. Level of normalization to aim for. (My minimum is 3 but I
generally hit Boyce Codd myself)
7. What datatypes to avoid and why.
Two requests.
1. Keep it polite.
2. Be constructive and complete.
"expert" about how a table was poorly designed has piqued my interest.
The question is this. What are the do's and don'ts of sql development?
Please list what you consider to be good and bad practices in general
and/or specific or list links to resources that would be considered
under this topic.
When I consider best practices myself of course there is always the
standards of 3nf and such but what about when it comes to standard
table structures and field sizes for say a Name (first, last, etc) and
contacts table. What about naming conventions and common entities and
structures.
It seems to me that every SQL Developer that enters this field starts
out with the basics of how the technology works and a little of the
practices. Yet from there I see many different directions that they
go.
To start this conversation out let me propose some things that I have
questions about. Feel free to expand and add to this list.
1. What would you consider the standard/best way to represent a
gender.
2. Field Size for Names and address First/Last Etc.
3. Include or don't include City/State in an address/contact list.
4. Structure of a Generic Contact list.
5. Practices for dealing with pictures and documents as well as
related table structures.
6. Level of normalization to aim for. (My minimum is 3 but I
generally hit Boyce Codd myself)
7. What datatypes to avoid and why.
Two requests.
1. Keep it polite.
2. Be constructive and complete.
Comment