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 |
|
tfountain
Constraint Violating Yak Guru
491 Posts |
 Posted - 2008-01-25 : 12:00:36
|
We are going to implement either a replicated database or use log shipping to another database to support our reporting needs. Basically we are moving reporting over data off our transactional database.With this in mind, I have several questions: - Are there any special configurations in terms of disks for a database in this situation?
- What are the recommended raid types?
Also, we currently store our data in one filegroup and indexes in another so obviously I'll want those on 2 separate physical disks other than the C:\. What about the log files? Do I care where they go (on C:\ or another physical drive separate from C:\, data filegroup drive and index filegroup drive)?Thanks! |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-01-25 : 12:15:45
|
| Depends on what type of replication you are using.also its good idea to keep same disk partition as of current one .It is good idea to keep log files in seperate disk for performance gain. |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-01-26 : 00:19:58
|
| I'll put data file on raid5 for faster read. By the way, log shipping is not good choice for reporting db since sql can't restore log if db has user connections. |
|
|
|
tfountain
Constraint Violating Yak Guru
491 Posts |
Posted - 2008-01-28 : 14:20:46
|
| Thanks for your input. Just to provide feedback we have decided to go with 3 logical disks with each made up of 2 disks. Data will be on one logical disk, indexes will be on a second logical disk and logs will be on the 3rd logical disks. As far as RAID goes, we're going RAID 1+0 for all of them (maybe only mirroring for the logs). |
|
|
|
|
|
|
Disk configuration for replicated database