sam (10/22/2008)

---

I have a general database design question.

Our company has multiple hosted web applications. Each of those applications currently use a single sign solution that reads from a database with general client information in it. Our "Client" DB holds client information for each of our applications.

Each of our applications also has it's own own database.

My question is, is it better to manage all client information in a central client database as we are, and push client information to individual application databases? Or is it a better architecture to store individual client information in each application's DB and push that data to a central Client DB that can be read from for reporting, billing and such.

Does this make sense? Can anyone offer resources that help with making these kind of database design questions?

Thanks