0
  • What is database schema decomposition?
  • Why do we need decompositions?
Jonathan Leffler
  • 730,956
  • 141
  • 904
  • 1,278
Md Nasir Uddin
  • 2,130
  • 8
  • 38
  • 59
  • 4
    When you did a Google search on 'database schema decomposition', did none of the top three entries help you? The ones I saw all looked relevant, especially the [third](http://crpit.com/confpapers/CRPITV62Koehler.pdf): _A common approach in designing relational databases is to start with a universal relation schema, which is then decomposed into multiple subschemas._ This is using the term 'decomposition' to describe the process of 'normalization', for which you'd find an enormous number of hits. – Jonathan Leffler May 06 '12 at 17:31

1 Answers1

1

Probably what is meant by this is that you start with one general schema for your database and decompose this into more specific schemas.

A good choice of more specific schemas can be determined using FK constraints defined on the schema, like join dependencies etc.

Why do you need it? I believe it significantly helps with normalization and manageability.

Randy Minder
  • 47,200
  • 49
  • 204
  • 358