Post reply

DB Design

  • June 4, 2010 at 9:58 am

    #236078

    Hello folks i am assigned a task to design a plan of action for a DB design for a new project.

    I jotted this down as far as my knowledge, i would like you guys to please critique this and correct it.

    Plan of Action

    I DESIGN

    Make a list of entities

    Relationships

    ERD/ Data Model

    II DEVELOPMENT

    List of querries we want out of DB

    Reduce Data Redundancy

    Do some Data restructuring

    List Data I/O Sources

    List out Contraints

    Normalization

    Decide upon keys

    Analysis of all fields (data types)

    II PHYSICAL IMPLEMENTATION

    Create Schema

    Naming COnventions

    Implement Referential Integrity

    Triggers/Constraints

    Querries/Stored Procedures

    Data I/P mechanisms(Selcet * INTO)

    IV TESTING

    Load Sample data

    Test out all Queries

    -- Please help/Critique/Comment/Suggest

    [font="Verdana"]
    Today is the tomorrow you worried about yesterday:-)    [/font]

  • June 4, 2010 at 10:27 am

    #1176630

    Don't forget your security and performance requirements/considerations 🙂

  • June 4, 2010 at 10:52 am

    #1176643

    DR, Backups, Log Shipping etc. 🙂

  • June 4, 2010 at 12:38 pm

    #1176701

    Business rules. Business Rules.. Business Rules.. 😀

    Ideally if you can get them in words, not just entites and relationships. That way that business folks can review them for accuracy.

    For example, "A campaign is always managed by an Advertiser" or "An Advertiser is the entity which pays us", etc.

    Often times strange rules come out of these exercises, like “well, sometimes a Campaign IS an Advertiser” or other strange rules... (note: purposely ridiculous for illustrative purposes)

  • June 7, 2010 at 2:24 am

    #1176959

    Disaster recovery...

  • June 7, 2010 at 2:35 am

    #1176963

    Index Design

    Thanks,

    Deepak.a

  • July 30, 2010 at 10:06 pm

    #1200599

    Shouldn't you have the list of queries or what questions need to be answered before designing the ERD? I'm in the middle of a project now and every time someone thinks of a new question they want to answer I have to change the design. (yes, I try to predict these, but I'm in Development and don't think very much like some of the marketing people.)

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply