Schema Design?

Discussion in 'Databases' started by meissnersdc, Jun 7, 2004.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. I am setting up a database of people plus a lot of data fields. I am trying to think of what is a good table schema.

    The data includes peoples names and addresses, but also a lot of
    fields with blanks, such as CanVolunteer ( a boolean - blank if false) or fields with multiple entries per person such a Payment ( amount and date ).


    The simplest design might be one big monolithic table. One row per person. Basically each data field would be a column. There are various ways to handle a list of things.

    The other schema I was thinking about was a star schema. There would be a central table of column ID and Name, which would index many other tables that index the tables by ID. So the CanVolunteer would be a one column table of ID, The Payment table would be ID, date, and amount. etc.

    Any thoughts about which design is better. Are there alternatives?


    Also which would be better to use. MS SQL or MySQL with ASP.NET?

    Karl


    Computer Consultant - www.meissnersd.com
     
  2. Bruce

    Bruce DiscountASP.NET Staff

    Karl,

    i'll leave your 1st question to some other DB guru.

    You want to use MS SQL with ASP.net. MySQL do not work best in MS environment.


    quote:Originally posted by meissnersdc

    I am setting up a database of people plus a lot of data fields. I am trying to think of what is a good table schema.

    The data includes peoples names and addresses, but also a lot of
    fields with blanks, such as CanVolunteer ( a boolean - blank if false) or fields with multiple entries per person such a Payment ( amount and date ).


    The simplest design might be one big monolithic table. One row per person. Basically each data field would be a column. There are various ways to handle a list of things.

    The other schema I was thinking about was a star schema. There would be a central table of column ID and Name, which would index many other tables that index the tables by ID. So the CanVolunteer would be a one column table of ID, The Payment table would be ID, date, and amount. etc.

    Any thoughts about which design is better. Are there alternatives?


    Also which would be better to use. MS SQL or MySQL with ASP.NET?

    Karl


    Computer Consultant - www.meissnersd.com
    </blockquote id="quote"></font id="quote">
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page