DaveWentzel.com All Things Data
Evolutionary Database Design
I came across this article on evolutionary database design. First, I don't particularly care for agile and related techniques. I believe the proponents of agile try to sell it as the answer to all of your prayers. It's not. There is no substitute for good people and processes. However, the underlying concepts work very well. This article basically covers everything I've been doing for at least 10 years and I never once called it agile database design/evolutionary database design/whatever else you want to call it to make is sound important. To me, it was just smart development practices. My database build process rigorously follows these design principles.
- Data Types
- Queue Processing Using SQL Server
- Hierarchical and Tree Designs
- Canonical Data Models
- the misuse of BIT flags
- "dynamic" data structures or EAV Models
- MUCK table designs
- XML as a persistence mechanism
- Column values that have different meanings based on context
- Circular references
ORM Tools and their issues, from many different perspectives.
SQL BI Methodology defines architecture and implementation decisions when deploying a BI solution on MS technologies.