July 8, 2005 at 4:31 pm
I was lucky enough to get a new machine, but now I want to be sure I install SQL the right way the first time. I already have a plan but I want to run through what others would recommend.
Server Configuration
Win2003 Server | SQL 2000 Pro | Dual 3.8 Xeon | 3 GB RAM | C: (RAID 0) 34GB | D: (RAID 5) 100GB
Database Specs
10GB Main Db with 200 Users 6am - 5pm Mon - Fri | 5 smaller DB inconsistent usage | Simple Backup
The server will also host our CRM application that uses the SQL database. Ideally I would have at least 3 drives at maybe a better RAID config. I am stuck with what was provided so the Hardware configuration cannot change.
I am looking for advice for placing the following pieces of SQL:
1) SQL Server Install
2) System Databases (master, tempDB, etc)
3) Database files
4) Log Files (remember backup is SIMPLE)
5) Backups (are ran after hours)
Any tips would be greatly appreciated!
July 11, 2005 at 8:00 am
This was removed by the editor as SPAM
July 12, 2005 at 9:25 am
Anyone have any thoughts? Btw, the server ended up being a Quad 3.2 Xeon.
Thanks!
July 12, 2005 at 1:01 pm
Well 4 heads are better than 2 aren't they?
Just a quick off the top of my head look at your configuration makes me itch to do something different with the drive array. I'm reluctant to implement anything on Raid 0 if it's a production system where I might be forced to do a reinstall the OS in the middle of the night. Assuming you're working with 6 disks, I'd be more inclined to split this into 3 Raid 1's or one Raid 1, one Raid 5, and one hot spare.
That's really the first question to answer before you start installing. Trust me, it's a lot better to do this on the front end than trying to change it after it's built. Just my thoughts for what they're worth.
My hovercraft is full of eels.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply