to facalitate the 32 GB production db
-
Hi Seniors,
We are going to plan to deploy a server to manage a 32 GB database. Can any tell/suggest me the aspests that should b consider in planning.
related to hard disk,RAM,Processor or any one Branded server name ? -
look at an HP DL385 G5 (AMD chips) or the HP DL380 G5 (Intel chips)... they have the same chassis, the only difference being the chipset... these boxes are nice for standalone database servers with no SAN connectivity... its a 2U server that can take 8 SAS drives, with an integrated RAID controller with 320Mb cache on the controller...
Create 3 drive arrays, 2 mirrors (RAID-1), and one striped mirror(RAID-1+0). Put your OS on the one mirror, partition that up within Windows, to an OS and data drive, and stick your tempdb on the non-OS partition on that Mirror... On the striped mirror stick the data file(mdf), and on the other mirror, stick your log file (ldf)... sorted...
oh yes, stick a 4 GB page file on each logical drive... Windows accesses page files simultaneously, so if you have 4 page files, it will do 4 writes simultaneously...
-
HP's are good machines. We were on HP's, then moved to Dell's, and now are going back to HP's.
We're similar. We are now purchasing 2-way or 4-way boxes that are Dual-Core (and, I'm sure we'll go Quad-Core on new boxes as we get more and they become more available). Generally our memory ranges from 4 GB (not common), to 8 and 16 GB (more common), and even up to 32 GB and a few 64 GB machines. When we're not running clustered boxes on a SAN, but are just running individual boxes, our disk configuration is generally something like this:
Channel 0 (Raid 1; 15k rpm): Partition for the Operating System, and Partition for SQL Server Binaries and system DB's.
Channel 1 (Raid 1; 15k rpm): For TempDB Data (MDF) file
Channels 2 & 4 (Raid 1 + 0; 15k rpm): For User Database MDF files.
Channels 3 & 5 (Raid 1 + 0; 15k rpm): For User Database LDF files.
Also on Channel 3 (Raid 1; 15k rpm): For TempDB Log (LDF) file
Also on Channel 5 (Raid 5; 10k rpm): For Database Backups to disk, prior to going to Tape.
We, however, generally put anywhere from 30 to 100 databases per server, ranging anywhere from a few MB in size up to 110 GB in size. Size of the database is only one factor to consider; another is activity level. For instance, you could have a 100 GB database, but if it is very low activity (low CPU, low I/O), you wouldn't need as powerful a server as say a 10 GB database with high activity.
If you're only going to have one database on the server, and it is ranging around 32 GB, you probably wouldn't need something this powerful and compartmentalized. You know your DB / application better than us though, so you'd know if it is high activity or not, and that is a judgement you'll have to make. I would always recommend splitting the MDF and LDF files onto separate drives / channels however, for performance reasons, and next, if you can split off TempDB (and even split that MDF and LDF), that will increase performance - that is, if you have the performance-gain needs. If you don't, then you may not notice a change in performance by doing that. If you need a further increase in performance, you can also split off the database indexes onto their own drive / channel. Also, don't forget, generally, the more disks you have in an array, the better performance you'll get.
Also, generally, your disks (your I/O) are generally the bottleneck - especially for database servers.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply