December 1, 2025 at 3:50 pm
Hello,
I am receiving multiple direction on deploying SQL Servers in AWS EC2. I've always separated SQL Server data and log files. I then separate the TempDB files onto different drives. A few times, I used the log file drive for database log files and TempDB log files.
Now, in an AWS Ec2 environment, do all files go on the same drive? What is best practice on where we place SQL Server files?
Just trying to learn the AWS environment and best practice to manage SQL Server environment in AWS.
Thanks.
Things will work out. Get back up, change some parameters and recode.
December 2, 2025 at 4:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
December 3, 2025 at 5:38 pm
Yeah, I'd still separate them. Same underlying issues are still there. Different levels and types of IO for each mechanism. Splitting them even lets you pick different levels of IOPs for each type of storage, saving money on, let's say logs, while you spend more money on tempdb. It's a great way to go.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 3, 2025 at 9:39 pm
I'd agree. In the cloud you often have software defined storage, so having more paths and being able to upgrade one is helpful.
December 4, 2025 at 5:07 pm
Thank you guys for that. I was thinking that, but this confirmation helps.
Things will work out. Get back up, change some parameters and recode.
February 3, 2026 at 12:05 pm
Yes even on AWS EC2, it’s best to separate data files, log files and TempDB into different volumes. They have different I/O patterns, and isolating TempDB in particular prevents it from becoming a bottleneck. This setup allows you to tune disk performance for each type and avoids contention.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply