Server Fault is a question and answer site for system and network administrators. 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

When running a server on amazon aws, is there any point to placing a sql server transaction log on a separate volume from the database? Of course if I had control of the physical environment I'd place the tlog on a separate spindle or raid array. But in AWS-EC2, the windows volumes will be mapped to any number of physical drives in some unknown configuration so I'm thinking no, there's no point in it.

share|improve this question

Well, if the db and logs are on the same EBS volume, you know they'll be competing for spindle time. At least if they're on separate EBS volumes, even if you don't know with certainty that they're on different spindles, at least there's a chance that they're on different hardware.

In addition to performance, there are several other benefits to separating them out.

share|improve this answer
Besides performance, what are the benefits? – Elroy Flynn Feb 3 '12 at 3:01

I recommend you read up SQL Server in EC2, there is also a video available Configuring SQL Server in Amazon EC2: Training Video.

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.