Just a doubt

  • Hii Frnds,

    I m having a doubt while creating multiple tempdb mdf files

    no. of tempdb files should be equal to No. of cores in processor ???

    OR

    no. of tempdb files should be equal to No. of Threads in processors??

    Sanket Ahir
    Don't run behind the success, Try to be eligible & success will run behind u......

  • have a look at: "A SQL Server DBA myth a day: (12/30) tempdb should always have one data file per processor core"http://www.sqlskills.com/BLOGS/PAUL/post/A-SQL-Server-DBA-myth-a-day-(1230)-tempdb-should-always-have-one-data-file-per-processor-core.aspx

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • If you have multiple physical drives, you might consider having a file on each separate drive to help with I/O. It might speed up processing a bit. But this is something that has to be tested for your specific server configuration.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Brandie Tarvin (4/27/2010)


    If you have multiple physical drives, you might consider having a file on each separate drive to help with I/O. It might speed up processing a bit. But this is something that has to be tested for your specific server configuration.

    Although, if you only have a single disk controller, you'll bottleneck there when the drives are under load.

    This is a real juggling act to get just right.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Grant Fritchey (4/27/2010)


    Brandie Tarvin (4/27/2010)


    If you have multiple physical drives, you might consider having a file on each separate drive to help with I/O. It might speed up processing a bit. But this is something that has to be tested for your specific server configuration.

    Although, if you only have a single disk controller, you'll bottleneck there when the drives are under load.

    This is a real juggling act to get just right.

    Hence the reason I made the testing comment. @=) Because multiple drives never help if it's a single controller.

    Though usually don't physical drives (as opposed to logical drives) have individual controllers for each disk? Or is that a wrong assumption?

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Brandie Tarvin (4/27/2010)


    Grant Fritchey (4/27/2010)


    Brandie Tarvin (4/27/2010)


    If you have multiple physical drives, you might consider having a file on each separate drive to help with I/O. It might speed up processing a bit. But this is something that has to be tested for your specific server configuration.

    Although, if you only have a single disk controller, you'll bottleneck there when the drives are under load.

    This is a real juggling act to get just right.

    Hence the reason I made the testing comment. @=) Because multiple drives never help if it's a single controller.

    Though usually don't physical drives (as opposed to logical drives) have individual controllers for each disk? Or is that a wrong assumption?

    Sorry, didn't mean to sound argumentative.

    In response, one three letter acronym, SAN.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Ahh. For some reason all the SANs I've come across use multiple disk controllers. I've never heard of one with only one controller, unless the SAN used logical drives only (for one particular cluster). Hence my confusion.

    Thanks for clearing that up, Grant.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Brandie Tarvin (4/27/2010)


    Ahh. For some reason all the SANs I've come across use multiple disk controllers. I've never heard of one with only one controller, unless the SAN used logical drives only (for one particular cluster). Hence my confusion.

    Thanks for clearing that up, Grant.

    100% true, but it's a question of whether or not it's configured correctly at the SAN level. From SQL Server's standpoint, they all look like valid drives. Whether or not it's all one drive, multiple drives, stripped, mirrored, whatever, is up to the SAN configuration. I don't know about you, but to a large degree, I have to simply have faith in my SAN administrators that they're not feeding my databases junk. We've had talks, so I know they know what I need, so usually I assume we're good. But I've heard tales about people who either never had that chat or simply have bad SAN admins.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • I know a SAN admin who holds on to information like a Scottish miser holds on to money. Anytime he's asked a question about setup, his first response is "Why? What problems are you having?"

    He acts like people are trying to get this info solely for setting him up for something later down the road. So never gives a straight, or complete, answer about the SAN set up.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Brandie Tarvin (4/27/2010)


    I know a SAN admin who holds on to information like a Scottish miser holds on to money. Anytime he's asked a question about setup, his first response is "Why? What problems are you having?"

    He acts like people are trying to get this info solely for setting him up for something later down the road. So never gives a straight, or complete, answer about the SAN set up.

    Yikes! People like that scare me. I know DBA's that behave that way. It's not good.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 10 posts - 1 through 9 (of 9 total)

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