Log File placement

Hi All,
We are using RAID5 for the data files and RAID 1 for the Log file.My assumption is that as long as you put only one Log file on the Log drive,you get the maximum performance as Sql Server does a Sequential Read/Write,there by gaining the performance,as compared to Random Read/Write.

My question here is that we are planning to put some dump file on the same drive where the log files are placed(RAID1).
Is this going to drag down the performance?Basically if I put any other file other than the one Log file then would it become a Random Read??Re: Hi All We are using RAID5 for the data files and RAID 1 for the Log file.My assumption is that as long as you put only one Log file on the Log drive,you get the maximum performance as Sql Server does a Sequential Read/Write,there by gaining the performance,as compared to Random Read/Write. My question here is that we are planning to put some dump file on the same drive where the log files are placed(RAID1).
Is this going to drag down the performance?Basically if I put any other file other than the one Log file then would it become a Random Read??

Q1 We are planning to put some dump file on the same drive where the log files are placed(RAID1). Is this going to drag down the performance?
A1 Whenever you actively dump to the RAID 1 volume, active transactions would be expected to be forced to share [disk IO resources] with the dump process(es) via the DB log files which (you stated) also reside there.

Q2 If I put any other file other than the one Log file then would it become a Random Read??
A2 As long as a given 'resident file' is not being subject to any IO operations (R/W)? it shouldn't force any shareing [of disk IO resources] with the DB log files which also reside there.