Table size

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • jrbareta

    Table size

    Is it better to have a table with 10,000 row or 10 tables of 100 rows?


  • jrbareta

    #2
    Re: Table size


    "jrbareta" <jrbareta@texom a.net> wrote in message
    news:brr59m0k8l @enews3.newsguy .com...[color=blue]
    > Is it better to have a table with 10,000 row or 10 tables of 100 rows?
    >
    >[/color]

    I should say that the single table would need a three field index and the 10
    tables would need a single field index.


    Comment

    • Greg D. Moore \(Strider\)

      #3
      Re: Table size


      "jrbareta" <jrbareta@texom a.net> wrote in message
      news:brr59m0k8l @enews3.newsguy .com...[color=blue]
      > Is it better to have a table with 10,000 row or 10 tables of 100 rows?[/color]

      It depends.

      If you have one entity that has 10,000 rows, a single table is better.

      If you have 10 entities, than 10 tables are better.

      i.e. you don't normally design the number of tables based on how many rows
      it will contain.

      [color=blue]
      >
      >[/color]


      Comment

      • Greg D. Moore \(Strider\)

        #4
        Re: Table size


        "jrbareta" <jrbareta@texom a.net> wrote in message
        news:brr5qb0kup @enews3.newsguy .com...[color=blue]
        >
        > "jrbareta" <jrbareta@texom a.net> wrote in message
        > news:brr59m0k8l @enews3.newsguy .com...[color=green]
        > > Is it better to have a table with 10,000 row or 10 tables of 100 rows?
        > >
        > >[/color]
        >
        > I should say that the single table would need a three field index and the[/color]
        10[color=blue]
        > tables would need a single field index.[/color]

        How about posting your DDL. That might work better.

        Again, it comes down to what entities you are modelling.

        [color=blue]
        >
        >[/color]


        Comment

        • jrbareta

          #5
          Re: Table size

          Hope this helps to clerify the question.

          In the single table case:

          Indexes patientid, major test type, minor test type

          in multiple table case: each table being a specific minor test type

          Index patientid:

          data contained in all tables:

          patientid, test date, test results, notes




          Comment

          • Greg D. Moore \(Strider\)

            #6
            Re: Table size


            "jrbareta" <jrbareta@texom a.net> wrote in message
            news:brrdpt0tkb @enews3.newsguy .com...[color=blue]
            > Hope this helps to clerify the question.[/color]

            Again, w/o a DDL, no it doesn't really.

            [color=blue]
            >
            > In the single table case:
            >
            > Indexes patientid, major test type, minor test type
            >
            > in multiple table case: each table being a specific minor test type
            >
            > Index patientid:
            >
            > data contained in all tables:
            >
            > patientid, test date, test results, notes
            >
            >
            >
            >[/color]


            Comment

            • Daniel Morgan

              #7
              Re: Table size

              jrbareta wrote:[color=blue]
              > Is it better to have a table with 10,000 row or 10 tables of 100 rows?[/color]

              It is better to not ask the question in the first place.

              Tables are sets. And unless one confronts a specific reason based on
              testing to violate that rule one should always create tables in a
              relational database to correspond with the basic rules underlying
              relational database design practices. I'd suggest you might want to read
              a bit of Date and Cobb before Mr. Celko finds you.

              Thus the answer to your question is ... if the set is identical
              then it should be in a single table. And if you don't understand the
              concept of what constitutes a set you shouldn't be designing tables and
              you probably don't even belong in your current occupation.

              Also you'd best have a very good reason, based on hard facts and by
              facts I mean metrics, for violating the rules unless you want to watch
              those persons responsible for architecture, front-end form development,
              and perhaps most importantly report writers, wish to string you up from
              a very short rope.

              Needless to say, you would fail any course in relational databases of
              which I can imagine and I have a very good imagination.

              --
              Daniel Morgan
              We make it possible for you to keep learning at the University of Washington, even if you work full time or live outside of the Seattle area.

              We make it possible for you to keep learning at the University of Washington, even if you work full time or live outside of the Seattle area.

              damorgan@x.wash ington.edu
              (replace 'x' with a 'u' to reply)

              Comment

              • jrbareta

                #8
                Re: Table size



                Thank you for your information. Looking through it, I think I can find
                some small nuggets of wisdom and an indication of your character.
                Times change, it used to be that there were very few dumb questions, for
                they showed some confusion on the part of the questioner. The DB table sizes
                I was referring to are a fraction of the real potential sizes.
                Yes, I know set theory. I cannot imagine in any course that you might
                teach that the students would get the maximum value that they should for the
                course.


                Comment

                • --CELKO--

                  #9
                  Re: Table size

                  >> Is it better to have a table with 10,000 row or 10 tables of 100
                  rows? <<

                  The question makes no sense.

                  A table is part of a data model, and represents one entity or
                  relationship. If you have ten different things to model, then you
                  need ten different tables. If you have only one thing to model, then
                  you need one table. Size has absolutely nohting to do with it!

                  Comment

                  Working...