how many tablespaces

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Vissu
    #1

    how many tablespaces

    Hi ,

    We will have about 50 tables. Some tables will be huge (severel
    million rows) and some are small but most of them will have about a
    million rows. For best performance of the database, how many
    tablespace should I have. I was thinking of using Locally Managed
    tablespaces (uniform extents) for both data and indexes.

    Can anyone share some experiences? Any other tips on layout of the
    database will be appreciated. Thanks

    Vissu
    Tags: None
    • Jim Kennedy
      #2
      Re: how many tablespaces


      "Vissu" <vissuyk@yahoo. comwrote in message
      news:2bedd6a7.0 403032012.2899a 4a6@posting.goo gle.com...
      Hi ,
      >
      We will have about 50 tables. Some tables will be huge (severel
      million rows) and some are small but most of them will have about a
      million rows. For best performance of the database, how many
      tablespace should I have. I was thinking of using Locally Managed
      tablespaces (uniform extents) for both data and indexes.
      >
      Can anyone share some experiences? Any other tips on layout of the
      database will be appreciated. Thanks
      >
      Vissu
      What version? Use locally managed with auto managed extents and put the
      data all in one tablespace.
      Jim


        Comment

        • Mark D Powell
          #3
          Re: how many tablespaces

          "Jim Kennedy" <kennedy-downwithspammer sfamily@attbi.n etwrote in message news:<Tly1c.112 729$4o.138921@a ttbi_s52>...
          "Vissu" <vissuyk@yahoo. comwrote in message
          news:2bedd6a7.0 403032012.2899a 4a6@posting.goo gle.com...
          Hi ,

          We will have about 50 tables. Some tables will be huge (severel
          million rows) and some are small but most of them will have about a
          million rows. For best performance of the database, how many
          tablespace should I have. I was thinking of using Locally Managed
          tablespaces (uniform extents) for both data and indexes.

          Can anyone share some experiences? Any other tips on layout of the
          database will be appreciated. Thanks

          Vissu
          What version? Use locally managed with auto managed extents and put the
          data all in one tablespace.
          Jim
          How many tablespaces you should use to support your database depends
          on the expected size and number of your objects and the organization
          of your disk farm.

          I greatly favor organizing most applications into large and small
          object tablespaces. Generally two sizes will work for everything.
          The best sizes depend on the objects involved.

          I do not like autoallocate because it still can suffer from the free
          space fragmentation problem while a properly sized uniform extent
          tablespace will never suffer this problem. The only time I think
          autoallocate is useful is where you install a canned package and the
          vendor places everything into a single tablespace (usually the
          application owner default tablespace).

          It all comes down to judgment on which arrangement will provide the
          most effective managment options.

          IMHO -- Mark D Powell --

            Comment

            • Mark C. Stock
              #4
              Re: how many tablespaces


              "Mark D Powell" <Mark.Powell@ed s.comwrote in message
              news:2687bb95.0 403040733.54e2e 330@posting.goo gle.com...
              | "Jim Kennedy" <kennedy-downwithspammer sfamily@attbi.n etwrote in message
              news:<Tly1c.112 729$4o.138921@a ttbi_s52>...
              | "Vissu" <vissuyk@yahoo. comwrote in message
              | news:2bedd6a7.0 403032012.2899a 4a6@posting.goo gle.com...
              | Hi ,
              |
              | We will have about 50 tables. Some tables will be huge (severel
              | million rows) and some are small but most of them will have about a
              | million rows. For best performance of the database, how many
              | tablespace should I have. I was thinking of using Locally Managed
              | tablespaces (uniform extents) for both data and indexes.
              |
              | Can anyone share some experiences? Any other tips on layout of the
              | database will be appreciated. Thanks
              |
              | Vissu
              | What version? Use locally managed with auto managed extents and put the
              | data all in one tablespace.
              | Jim
              |
              | How many tablespaces you should use to support your database depends
              | on the expected size and number of your objects and the organization
              | of your disk farm.
              |
              | I greatly favor organizing most applications into large and small
              | object tablespaces. Generally two sizes will work for everything.
              | The best sizes depend on the objects involved.
              |
              | I do not like autoallocate because it still can suffer from the free
              | space fragmentation problem while a properly sized uniform extent
              | tablespace will never suffer this problem. The only time I think
              | autoallocate is useful is where you install a canned package and the
              | vendor places everything into a single tablespace (usually the
              | application owner default tablespace).
              |
              | It all comes down to judgment on which arrangement will provide the
              | most effective managment options.
              |
              | IMHO -- Mark D Powell --

              also should take into consideration grouping segments for similar
              availability / back-up schedules / transportabilit y / read-only and similar
              tablespace-specific operations

              ;-{ mcs


                Comment

                Previous template Next
                Working...