Results 1 to 8 of 8
  1. #1
    Join Date
    Oct 2010
    Posts
    37

    Spreadsheet to Database conversion

    I am doing a project of converting a spreadsheet to database. Currently the spreadsheet contains 12 pages of general information (attribute) as follows:

    ImageShack® - Online Photo and Video Hosting

    Each table represents a page

    I am not too sure how to approach converting this into a database. My first attempt was putting everything into one table but this solution hasn't worked.

    Any help would be great.

  2. #2
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Upload the data directly to tables. One table per page/dataset.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

  3. #3
    Join Date
    Oct 2010
    Posts
    37
    Quote Originally Posted by blindman View Post
    Upload the data directly to tables. One table per page/dataset.
    This may lead to redundancy an inconsistency as many attribute would be repeated among tables.... is there a more efficient way of doing this?

  4. #4
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    If you want to redesign your database to implement foreign keys, constraints, normalization, etc, do it after you have the data loaded into your tables.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

  5. #5
    Join Date
    Oct 2010
    Posts
    37
    I rather redesign the database to implement foreign keys, constraints, normalization before I attempting anything else.


    What I am asking is how to organise the tables and develop a ERD.

  6. #6
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    If you redesign your database first, then:
    1) You are going to be doing it without the benefit of looking directly at the actual data.
    2) You are going to need to create additional staging tables or transformation processes to convert your old schema to your new one.

    So unless uploading this data needs to be a repeatable process, if you have a green field development project why would you create additional work for yourself?
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

  7. #7
    Join Date
    Oct 2010
    Posts
    37
    Quote Originally Posted by blindman View Post
    If you redesign your database first, then:
    1) You are going to be doing it without the benefit of looking directly at the actual data.
    2) You are going to need to create additional staging tables or transformation processes to convert your old schema to your new one.

    So unless uploading this data needs to be a repeatable process, if you have a green field development project why would you create additional work for yourself?

    I understand your point now...thanks for the help. I will directly upload the data to tables and take it from there. I will keep this thread updated if I come across any problems.

  8. #8
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Glad to help.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •