Standards for a database design document [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.

Closed 5 years ago.

Improve this question

I am beginning the process of putting together a design document for my companies database. I am trying to use as many formal standards as I can. Does anyone know "Is there a standards document (like IEEE 1016 1998 IEEE Recommended Practice for Software Design Descriptions) for databases"? WIKI talks about a Database Design Document, but I can't seem to find any "good" examples of what a database design document should include.

There are a few other 开发者_StackOverflow社区questions on Stack Overflow that are close to this, but not exactly what I am after. I have been poking around on the web and cannot find a good answer to the question either. Does anyone know of such a standard or would I be better off just adapting IEEE 1016 1998 to meet my needs?

---

I grappled with this same problem a couple years ago. I resorted to using Joe Celko's excellent book SQL Programming Style to help me put together our company's database standards document.

http://www.amazon.com/Celkos-Programming-Kaufmann-Management-Systems/dp/0120887975/ref=sr_1_7?s=books&ie=UTF8&qid=1289941772&sr=1-7