Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On my SQL 2008 R2 active/passive cluster, I've received an error message regarding I/O requests on tempdb.mdf taking longer than 15seconds. Googled that and it as suggested I spread tempdb over several files. I have 2 4-core CPUs and figured I'd spreaad tempdb over 8 files. The current tempdb.mdf is 8GB in size, most of which is unused space. I figured I'd start out with all 8 files being 512MB with filegrowth set to 64MB increments.

Ive executed the T-SQL to create the extra files and set the original tempdb.mdf's initial size to 512MB. My question is:

If I now rollover the cluster to the other node, will the tempdb.mdf file shrink to 512MB? And will this allow the SQL server to spread tempdb across all 8 files?

Or must I perform any other operation?

Or - hope this is not the case - have I made a mistake that means the SQL server will crash when I rollover ?

share|improve this question

migrated from Oct 17 '13 at 11:14

This question came from our site for professional and enthusiast programmers.

Don't know if anyone will read this, but... I performed the rollover this weekend without problems. All 8 tempdb-files are now 512MB. "Case closed"

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.