New Server - Dont Like My Options
-
I just want some other opinions. I have already setup several SQL servers in our offices but they have been real basic, mostly with defaults, and the data and logs are all either residing on the same RAID5 disk array with everything on the server or they are on a NAS server.
We are getting a new server and I put together a configuration plan that would provide optimal performance BUT I was told it was too expensive and I was told what we can get and that is what we are getting. I don't like it but there is nothing I can do about it.
Our server is going to have one controller that is split into two channels for two disk arrays. We are going to have a RAID5 array and a RAID1 array.
Initially, we are going to set this up by putting the OS, SQL engine, pagefile, system databases and our single major database on the RAID5 array. We are going to put the major database's transaction log on the RAID1 array.
Any other databases that will be controlled from this SQL engine will be minor and they will have to have their data and log files on our NAS server.
This major database is a transactional system and not a data warehouse so there is a lot of read/write activity going on.
My question is about the TempDB database files. Should I leave them on the RAID5? I would really like to keep the transaction log for our major database on it's own disk. I know that if I put anything else on the disk with the transaction log, my benefit is lost.
Is this the right thing to do, considering I only have the two disk arrays?
I appreciate all feedback.
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
-
This was removed by the editor as SPAM
-
That's a toughie.
I don't know the best answer for this, what you would probably be best doing is to run performance monitors against the server and db with it in both scenarios and then find which is performing best and go with that.
-
Your basic setup is fairly acceptable.
Consider making the Raid1 bigger with 2 logical drives and moving OS etc to one drive, and the logs to the other. The OS files will not benefit from RAID5 and are best separated from the DB(s). Use the RAID5 for the DB(s) only. I would even put Master / Model etc on one of the RAID1s.
Logs on Raid1 is perfect.
TempDB, you indicate the DB is mostly transational, so there will probably be limited use of TempDB. Initially, I would vote for the the same drive as the Logs.
You could consider 3 logicals in the Raid1. OS, Logs, TempDB but that will create some disk space issue's.
KlK -
When you say make the RAID 1 bigger, I assume you are talking about disk size or number of disks. Is that correct?
Even if I made it into 2 logical drives, won't that defeat the benefit of fast writes for the log? It seems to me that the actual drive heads would still have to jump around to find the right location for each write, depending on whether or not it is for the OS, log, TempDB, or system databases.
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply