Post reply

SQL 2000 SP4 Partition

  • January 31, 2010 at 10:10 pm

    #229526

    Hi Guys,

    I am MSSQL newbie and have a DL380G5 with 2 CPUs, 4 x 146 10K SAS HDD, 18GB RAM and Enterprise 32bit Server OS.

    I setup 2 x RAID 1 for my 4 x 146 10K SAS HDD so i have 2 logical drive around 135GB each

    i setup my OS on first logical drive (C:\ 40GB). I know that separate out the data files and transaction log is best practice but i don't have budget to add on another hdd.

    So i',m th seek for help for best SQL 2000 partition configuration in my environment.

    what i'm think before is.

    1st logical drive - 40GB (C: OS), 40GB (D: Transaction logs), 40GB (E: Keep others file for sharing)

    2nd logical drive - 40GB (F: MSSQL binary + tempdb), 80GB (G: Data files)

    is it ok? Thanks

    Seek for help and suggestion

    Brillian thanks

  • February 1, 2010 at 3:22 am

    #1111488

    anyone? please..

    appreciate any help and suggestion.

    thanks

  • February 1, 2010 at 3:51 pm

    #1111998

    As your OS is using one of the drives it is going to be hard to get any kind of great performance (in my opinion) as you will have some kind of contention on any kind of setup you choose.

    You could store the OS and trans logs on one drive with the .mdb files and temp db on the other. However, if there is a lot of write activity to the database then having the log files on the same drive as the OS is probably not the best idea.

    I think you are going to have to evaluate what the database is going to be used for and design the best you can from there. Do you have a development/test environment that this can be planned on before bringing a new untested and unsure design into production?

    No chance your environment has a SAN, huh?

    Joie Andrew
    "Since 1982"

  • February 2, 2010 at 3:05 am

    #1112150

    Hi,

    Thanks for replied.

    Ya. I will not going to have a SAN (budget....budget....)

    anyway, we have a same dev setup which using a 3 years old server which same setup. But the data files and transaction log sit on same disks while OS sit on another disks.

    the performance is not really good.

    I do know the in my environment, any of my setup is not going to be best practice.....thats why i looking for best setup suggestion from other i can configure with my current hardware spec...

    thanks

  • February 2, 2010 at 1:08 pm

    #1112505

    In that case I think it is going to be tough either way you design it, as there is going to be contention with multiple requests trying to read/write to the disks at the same time.

    Others may have some better suggestions, but I think if your database sees more reads than writes, then the mdb files should be on the second disk and have the logs on the OS drive. If you experience more writes than reads though, I would say put the logs on the separate drive and the mdb files on the OS drive.

    This is just my opinion though. Other's may have more experience in similar setups and can offer different/better tips.

    Joie Andrew
    "Since 1982"

  • February 2, 2010 at 8:37 pm

    #1112632

    Hi Andrew,

    Thanks.

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply