Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Aleph_0
Yak Posting Veteran
79 Posts |
 Posted - 2012-01-26 : 19:11:51
|
| I've read the term/phrase a few times now and haven't been able to find a clear explanation. Is it a technique? A concept? A product?And then, of course, the follow-up: What are SQL Design Anti-Patterns? A different technique? An opposing school of thought? A clever name?Thanks! |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2012-01-26 : 21:33:07
|
| Design patterns are generally accepted methods for accomplishing a certain task. They typically have been tested in real-world scenarios and have had various bugs, flaws and other problems worked out, and/or present the overall best example of how to do that particular scenario.Anti-patterns are things that are generally recognized as bad or less than ideal, and should be avoided. My #1 personal anti-pattern are cursors. Most database books will caution about tables that do not meet First Normal Form, or are lacking primary keys. They tend to be beginner-level mistakes, or symptoms of a rushed implementation, but generally indicate a lack of "design" in the data model.I believe O'Reilly has a book on SQL Design Patterns, and someone also has a SQL Anti-Patterns book, they're both worthwhile. Check Google or Amazon and you'll find them. |
 |
|
|
|
|
|
What are SQL Design Patterns?