September 3, 2002 at 8:45 am
Hello all,
I'm building a database/VB front end for a place that's running SQL Server 7.0 on a Win2K server with a RAID 5 configuration, that's partitioned as C: and D: drives. I realize that the transaction log really should be on a separate physical disk. Unfortunately, my only option is to place the data file on C and the T-Log on D of this RAID 5. There will be only up to 10 users at any given moment, and reading and writing data is about equal. Will I see a huge impact on performance running the whole shebang on a partitioned RAID 5, or should I see if they can add an inexpensive XXgb drive just for the transaction log?
September 3, 2002 at 9:42 am
Depends on load. For smaller apps, I've dropped everything on the same RAID 5 and no big deal. Nice to separate out, so if you move the hardware later, the drives are the same. Not a big deal with SS2K, though, you can easily move stuff later.
Steve Jones
September 3, 2002 at 9:49 am
Thanks, Steve. If it ever happens that another drive is acquired, I can always reassign the log to the new drive with the ALTER DATABASE command, correct?
September 3, 2002 at 9:56 am
Either that or detach/attach. Raul Sharma has an article on usnig that on this site.
Steve Jones
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply