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!