Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
DBADave
Constraint Violating Yak Guru
366 Posts |
 Posted - 2007-03-07 : 16:53:14
|
| Do you see any issues with the data (500GB) being on a RAID 10 SAN partition and log files being stored on SCSI drives?Thanks, Dave |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2007-03-07 : 17:47:06
|
| One of the benefits of SAN is that you can just move the LUNS intact to another server if the server they are on dies. If your transaction log is not on the SAN, you will not be able to do that.I have used this feature to bring up a warm standby server in an hour or so after a server failed.CODO ERGO SUM |
 |
|
|
rlaubert
Yak Posting Veteran
96 Posts |
Posted - 2007-03-08 : 10:35:13
|
| What kind of transaction processing does this database have. If it is extensive insert/update/delete than this should be pretty good. If on the other hand you are more concerned about recoverability, than the SAN may be a better place to put the Transaction Log. Remember all transactions write to the Transaction log FIRST then to the database as the system requires. A heavily used SANs may also affect performance if the request are queued up.Raymond LaubertMCDBA, MCITP:Administration, MCT |
|
|
|
|
|
|
Data Files on SAN and Log Files on SCSI