Results 1 to 2 of 2
  1. #1
    Join Date
    Nov 2007
    Location
    Sydney, Australia
    Posts
    13

    Unanswered: Logical page size and performance

    Hi,

    I have inherited a 86G database which is loaded upon 86 1G devices and the logical page size on the server is 2K. Some of the large tables with data and indexes are more than 1.5 G in size. My questions are

    1. Is this the best pagesize to have and if not why?
    2. Does having so many devices make the database run slower?

    Thanks for the help

  2. #2
    Join Date
    Sep 2003
    Location
    Switzerland
    Posts
    443
    Quote Originally Posted by atapojha
    Hi,

    I have inherited a 86G database which is loaded upon 86 1G devices and the logical page size on the server is 2K. Some of the large tables with data and indexes are more than 1.5 G in size. My questions are

    1. Is this the best pagesize to have and if not why?
    2. Does having so many devices make the database run slower?

    Thanks for the help
    The basic rule of thumb to use larger page size is when you have larger row sizes. You really dont need larger page sizes on other scenarios.

    Having so many 1g devices may be a little overhead but more importantly a pain to maintain it.
    If your OS allows you to create larger devices, what you can do is sum up the sysusages entry for data and log and use the same large device.

    For eg.,
    If you have the following segmap, device, size

    1. 3, data1, 1g
    2. 3, data2, 1g
    3. 4, log1, 500m
    4. 4, log1, 500m
    4. 3, data3, 1g
    5. 3, data4, 1g
    6. 3, data4, 1g

    You can sum up all devices with the same segmap.

    create database mydb on newdata1=2g log on newlog1=1g
    alter database mydb on newdata1=3g

Posting Permissions

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