May 1, 2018 at 9:51 am
I am working on a server that all the databases are created in the default directory of when SQL Server was installed (so dumb). That means all data files and log files are on same drive and same directory. So of course I see all kinds of IO waits. This server also does not have any other drives to which I may move the log files (again dumb). My question is if I created a new directory on that drive and moved log files to that directory would it help a little bit with the IO (my guess is no). I need to ask to come up with some cleaver way to correct
May 1, 2018 at 10:22 am
keanyukas - Tuesday, May 1, 2018 9:51 AMI am working on a server that all the databases are created in the default directory of when SQL Server was installed (so dumb). That means all data files and log files are on same drive and same directory. So of course I see all kinds of IO waits. This server also does not have any other drives to which I may move the log files (again dumb). My question is if I created a new directory on that drive and moved log files to that directory would it help a little bit with the IO (my guess is no). I need to ask to come up with some cleaver way to correct
All of it really depends on what type of storage is being used. A lot of disk recommendations are still based on having direct attached storage which often is not the case these days. I/O waits are waits anywhere in the I/O subsystem, not limited to just the disks. A new directory on the same drive isn't going to help though. If you have I/O issues, you want to look at more than just the disks.
Sue
May 7, 2018 at 10:22 pm
As Sue mentioned, you won't get any improvement here. There is slight value with more files at times, and there are often better performance on different drives, but slight. Really you need to understand the underlying storage before you make a decision.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply