How do you do....it? Thread, SQL Server best practices in Technical; At the moment, we have SQL running on various servers for various applications - Sophos, BackupExec, Auditwizard, PCE etc. Works ...
17th May 2010, 02:19 PM #1
SQL Server best practices
At the moment, we have SQL running on various servers for various applications - Sophos, BackupExec, Auditwizard, PCE etc. Works well enough but I'm guessing it isnt the most effiiciant method.
We will soon be centralising storage with a SAN, and so that will leave some servers, which currently do little more than serve files, free. One in particular is filled with 15k SAS drives, so together with a load of RAM chucked in will be a seriously decent server (and is probably vastly underused by being a file server)
So at that point, would utilising that one server for pretty much all our databases be a sensible idea? Because it would give me the flexibility to virtualise the servers running the applications themselves, then just connect them to the SQL server, knowing that it was running on something with fast drives and dedicated.
Sensible? Or better not to have it all on one (or 2) server(s)?
* I'm leaving out SIMS from all of this since it is managed by the LEA and wouldnt want to step on their toes by moving the database, nor do I want to give ourselves the responsibility!
19th May 2010, 12:02 AM #2
The answer for me is yes, centralise to a single server.
Its almost like virtualisation for SQL, why run on many servers when a single one will do. Less hardware and maintenance, fewer MS SQL and backup licenses etc...
If you don't like all your eggs in one basket, then add High Availability via a MS cluster or a SQL mirror(s).
19th May 2010, 07:55 AM #3
Yes, I would centralise to a signle server but have no other services running on it. We plan to do the same in the summer with a lot of our SQL services. The only thing we are keeping seperate are Eclipse.Net and SIMS.
SIMS, I would almost certainly keep to it's own box.
19th May 2010, 09:30 AM #4
Sounds like a plan to me. I certainly would have a database server, storage (SAN) and then all the hosts virtual. A bit datacente esk.
19th May 2010, 09:59 AM #5
Again, I'm another one in favour of hosting all the SQL on one box... it will seriously cut licensing costs if nothing else. Make sure you use seperate physical disks for OS, databases and transaction logs for maximum performance though.
@rh91k: Why do you keep your Eclipse.net DB seperate? I run the Eclipse.net DB on the same server as by XenApp DBs and our attendance DB and it causes no problems... it's even running on SQL 2000!
19th May 2010, 11:20 AM #6
21st May 2010, 04:53 PM #7
Thanks guys, good to get some confirmation from other people!
By apearce in forum Virtual Learning Platforms
Last Post: 11th October 2011, 05:34 PM
By cgabbadon in forum How do you do....it?
Last Post: 16th December 2010, 11:48 AM
Last Post: 22nd June 2009, 11:17 AM
By rpwillis in forum Virtual Learning Platforms
Last Post: 3rd April 2009, 12:52 PM
By amfony in forum How do you do....it?
Last Post: 11th June 2008, 02:25 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)