Should I isolate the Tempdb or Fulltext catalogs on their own volume.

  • I am running short of drive space on my shared array and I have to make a decision. Please advise bewteen option A,B or C below. For maximum performance should I...

    A.) Keep the tempdb with the other databases and isolate the full-text catalogs on their own array

    B.) Keep the fulltext catalogs with the other databases and isolate the tempdb on its own array

    C.) Keep the fulltext catalogs and tempdb on their own array and leave all the other databases on their array

    This is a 2005 cluster setup, the shared array will have fast 15K SAS drives. The application running will have many users running inserts and select queries (that use fulltext indexes)

    I'm just looking for general opinions here, please help

  • The more distributed the I/O, the better - you already know that 😉

    In regards to which option is the better that's something only you can tell... check I/O for specific items and load balance it the best you can.

    _____________________________________
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at Amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
  • I would second Paul's advice. Figure out if tempdb or the FT catalogs take more IO and move them. I'd be betting on tempdb, but check it.

  • What is a good method for checking the I/O on a specific file? Thanks

  • I think there are performance monitor counters for reads/writes for tempdb and full text.

  • Or use DMV's.

    "Keep Trying"

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

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