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 have an EBS backed EC2 instance, I've heard it's good to store your SQL on another attached EBS volume for

"sustain many more random IOPS than instance disks (good for typical workloads) and they live independently of your instances. "

How does one do this? Is it just a case of in SQL management studio pointing the MDF storage location for the database on the attached EBS? SO essentially ALL the attached EBS has, is one MDF file? Is there no decrease in speed from this approach?

share|improve this question
    
Where is that quote from? Perhaps with more context it will make better sense. –  TTT Mar 5 '13 at 19:23

1 Answer 1

It's definitely better to store your SQL Server data and log files on separate volume or you could even consider storing data and log files on separate attached EBS volumes. They indeed "live independently of your instances" if you didn't set DeleteOnTerminate flag. That gives you some freedom configuring storage for your database server, for example:

  1. With provisioned IOPS you could create volumes with guaranteed performance.
  2. You could increase performance even more using striped volumes
  3. You could create on-fly snapshots to backup your data - be sure to use VSS to guarantee consistency of data files
  4. If you run out of storage you could attach another volume and create new data/log files there
  5. etc

Cloud makes lots of new scenarios possible... :)

share|improve this answer

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.