locked
Master Database Modelling RRS feed

  • Question

  • The question is related to Database Modelling.

    We want to create a Master Contact Database (I am even confused whether this should be Master Contact or Master Customer). We dont have Enterprise edition so cannot user MDM solution of SQL Server. We have a lot of Contacts coming from various sources. We want to maintain history preserving all the data we get. The main important List for us will be

    1. Master Contact (Like FirstName,LastName,Marital Status...etc)

    2.Master Companies (Like the Companies they belong to)

    3.Master Address (Physical Addresses)

    4. Master EmailAddress,Phone,Fax etc...

    All of this lists will have many to many relationships...I dont know whether I should break these down into other tables or merge some of this tables and make few number of tables. I am also thinking about the link table that should be maintained.

    Basically I am looking for a Sample Database Model which would fulfil my requirement. Do you experts know any of such samples ? Or, Can you provide me of such sample model.

    Thanks alot!!!!!!!!!!!

    Monday, August 22, 2011 12:16 AM

Answers

  • I just meant that its a shame you can't use MDS...

    The first two links that I mentioned above should be fairly close to what you're after, and should hopefully provide some good pointers.

    In addition, the link below seems to be a good resource for all sorts of data models, including several for customers:

    http://www.databaseanswers.org/data_models/

    HTH

    Jeremy


    http://blogs.adatis.co.uk/blogs/jeremykashel/default.aspx If a post answers your question, please click the Mark As Answer button.
    Tuesday, August 30, 2011 9:00 AM

All replies

  • Hi Nadir,

    That's a shame that you can't upgrade to Enterprise Edition.

    If you are looking to roll your own MDM solution/database, then I would probably steer towards a normalised database, so keep Customer names and Customer countries/region seperate. This will allow you to more easily re-use the individual components (e.g. country) of an MDM subject area. You could then have a global counties list (for example) that you could share across multiple MDM subject areas, which is something that you can't easily do with MDS.

    You're also correct that a bridge/link table would need to be maintained - but if you're writing a custom front end then you should be able to handle that.

    Hopefully the following will be of some help:

    http://www.databaseanswers.org/data_models/customers_and_addresses/index.htm

    http://www.agiledata.org/essays/dataModeling101.html (see customer examples half way down)

    http://efreedom.com/Question/1-648463/Best-Way-Model-Customer-Address

    HTH

    Jeremy


    http://blogs.adatis.co.uk/blogs/jeremykashel/default.aspx If a post answers your question, please click the Mark As Answer button.
    Tuesday, August 23, 2011 3:45 PM
  • Thanks alot for the reply!!!!

    I did not understand why it would be shame that I cant upgrade it into Enterprise Edition.

    Can you provide me a sample diagram of such Database Model?

     

    Tuesday, August 23, 2011 5:26 PM
  • I just meant that its a shame you can't use MDS...

    The first two links that I mentioned above should be fairly close to what you're after, and should hopefully provide some good pointers.

    In addition, the link below seems to be a good resource for all sorts of data models, including several for customers:

    http://www.databaseanswers.org/data_models/

    HTH

    Jeremy


    http://blogs.adatis.co.uk/blogs/jeremykashel/default.aspx If a post answers your question, please click the Mark As Answer button.
    Tuesday, August 30, 2011 9:00 AM