Bad Database Standards
Today's blog post is a metapost, of sorts. I am using my DB2 blog to point you to a series of posts I made in my other blog (Data and Technology Today). You see, I write for two blogs, this one that focuses on DB2 and mainframe topics, and another one on data and database management topics in general.
One of my more popular series of posts on Data and Technology Today was the one on bad database standards. The general idea of these posts is to dissect and criticize standards that are outdated, or simply wrong. The seven part series ran about a year ago and has generated a bunch of comments. And it will be useful to DB2 folks to read these posts, too.
So without any further ado, here are links to the seven bad database standards:
- Limiting the number of indexes.
- Too Many Columns!
- Limiting The Number of Tables in “Online” Joins
- Duplication of Data
- None Shall Pass!
- What’s In A Name?
- What Does Support Mean?
Take a moment to click through to these links and peruse the "bad" standards and, if you are so inclined, post a comment (either here on this blog, or over on the other one) to share your "favorite?" bad standards.