Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I recently ran into an interesting situation with a client. They were reporting that the application we support was having performance issues, namely it was running very slowly.

Upon investigation we found that their system partition (C:) only had 20GB total of space. To make matters worse it was also where the MSSQL DB was being stored as well. When asked what else they'd done, they reported that in order to fix the space issue they enabled compression on the system volume.

As you can imagine, the compressing and decompressing of data to run SQL queries against is most likely the cause of their performance issues.

My question is: can we resize the compressed partition just like any other without breaking everything? Keep in mind that windows refuses to do so from diskmgmt.msc (the option is grayed out).

share|improve this question
    
It might be grayed out because there is no unallocated space on the physical disk just after the C partition. Is that the case? –  charnley Mar 22 '11 at 13:50

1 Answer 1

What kind of server is this, physical or virtual? A simpler, more sustainable solution might be to add a second drive and move the database and log file.

share|improve this answer
    
It's a physical server. Yes that would be the ideal solution for many reasons, however for whatever reason, the current HW is set in stone. I'm still curious as to whether a compressed volume can be resized just like any other, or not. –  Tarek Fadel Mar 24 '11 at 10:09

Your Answer

 
discard

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.