Database Desgin

Discussion in 'Databases' started by js_best4u, Jul 17, 2010.

  1. #1
    How to design consistent & effective database,which software are used to design database,
     
    js_best4u, Jul 17, 2010 IP
  2. aquilax

    aquilax Member

    Messages:
    126
    Likes Received:
    4
    Best Answers:
    0
    Trophy Points:
    33
    #2
    The software usually depends on the database engine, you use.
     
    aquilax, Jul 20, 2010 IP
  3. mrx345

    mrx345 Peon

    Messages:
    68
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    Well, you can use ErWin

    actually you will use database design tools only for very very big projects where you have thousands of tables and you need to manage them.

    In most cases it’s more than enough to use a tool like TOAD or SQLNavigator
     
    mrx345, Jul 23, 2010 IP
  4. Deacalion

    Deacalion Peon

    Messages:
    438
    Likes Received:
    11
    Best Answers:
    0
    Trophy Points:
    0
    #4
    Follow the forms of database normalization.
     
    Deacalion, Jul 24, 2010 IP
  5. jemagee

    jemagee Peon

    Messages:
    9
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #5
    I personally have never used any kind of database software aside from a pencil and paper to diagram relationships. Like Deacalion side, use the forms of database normalization to get to 4NF. If you don't know what 4NF is then you need to research more the concepts of database design and relational databases, tool or no tool being used.
     
    jemagee, Jul 25, 2010 IP
  6. skytide

    skytide Peon

    Messages:
    25
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #6
    Learn database normalization and the different normal forms to create relational databases. Just get a beginners book on SQL databases, and it should teach you that stuff.
     
    skytide, Jul 30, 2010 IP
  7. TheWiseGuy

    TheWiseGuy Member

    Messages:
    113
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    28
    #7
    if you're not building a database with hundreds of tables you'll be fine with no design tools, pen and paper maybe ( if necessary ).
    You should be more worried about understanding what normalization is. Basically you should always avoid redundant data. If you think a field will often contain the same text value, then probably there's a better way to do it. ( This is just an idea of it, search google for database normalization practices ). If your db is not normalized it will require way more space than necessary, it will be a hell to maintain it and correctly update everything, and will be slower than it could be.
     
    TheWiseGuy, Aug 10, 2010 IP
  8. dodolls

    dodolls Well-Known Member

    Messages:
    282
    Likes Received:
    3
    Best Answers:
    0
    Trophy Points:
    108
    #8
    First and foremost, you should understand and analyze your requirements. The DB design must be able to meet the requirements of the application that will use the database later, and solve record keeping problems that require a database to answer. A well designed database is useless unless it is able to meet the requirements, but a simple yet properly crafted DB is always best.
     
    dodolls, Aug 12, 2010 IP
  9. ksrao

    ksrao Peon

    Messages:
    5
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #9
    Hi,

    I will suggest some simple steps to do the data base design manually if your
    tables are considerably less.

    1. Analyze the situation to gather information about the proposed Data Base.
    2. Decide on columns, data types,and lengths of data.
    3. Normalize the data into tables.[ist NF,II NF,IIINF,IV NF,VNF]
    4. Create the Data base and tables.

    If your data base is small use SQL Server, If it is bigger use <a href="http://www.wiziq.com/online-tests/895-free-practice-test-oca-oracle-certified-associate"> Oracle.</a>

    Regards
    Kolla Sanjeeva Rao OCP[Oracle 9i]
     
    ksrao, Aug 14, 2010 IP