+ Post New Thread
Results 1 to 7 of 7
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 ...
  1. #1

    Join Date
    Jul 2006
    Location
    London
    Posts
    2,962
    Thank Post
    159
    Thanked 152 Times in 116 Posts
    Rep Power
    49

    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!

  2. #2
    apaton's Avatar
    Join Date
    Jun 2009
    Location
    Kings Norton
    Posts
    283
    Thank Post
    54
    Thanked 106 Times in 87 Posts
    Rep Power
    36
    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).

    Regards

    Andy

  3. #3
    rh91uk's Avatar
    Join Date
    Sep 2008
    Location
    UK
    Posts
    876
    Thank Post
    137
    Thanked 132 Times in 114 Posts
    Rep Power
    35
    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.

  4. #4
    mjs_mjs's Avatar
    Join Date
    Jan 2009
    Location
    bexleyheath, london
    Posts
    1,018
    Thank Post
    37
    Thanked 111 Times in 95 Posts
    Rep Power
    37
    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.

  5. #5

    Ric_'s Avatar
    Join Date
    Jun 2005
    Location
    London
    Posts
    7,590
    Thank Post
    109
    Thanked 762 Times in 593 Posts
    Rep Power
    180
    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!

  6. #6

    Join Date
    Jan 2009
    Location
    England
    Posts
    1,480
    Thank Post
    297
    Thanked 304 Times in 263 Posts
    Rep Power
    82
    Quote Originally Posted by Ric_ View Post
    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!
    Mainly because of the number of times MLS have to remote in to fix things for us . Unfortunately our librarian is very very picky and since we moved to Eclipse.net in September we've had no end of hassle (not MLS's fault I might add!) with Eclipse.net not working as she expected it would. MLS have been great with trying to fix the problems she's had, and implement the functionality she wants but it means every now and then they remote in and do things to the database for us. Easier to just keep it all on one VM so they can do their bits on the one server

  7. #7

    Join Date
    Jul 2006
    Location
    London
    Posts
    2,962
    Thank Post
    159
    Thanked 152 Times in 116 Posts
    Rep Power
    49
    Thanks guys, good to get some confirmation from other people!

SHARE:
+ Post New Thread

Similar Threads

  1. Installing Moodle on Windows Server, SQL Server, IIS
    By apearce in forum Virtual Learning Platforms
    Replies: 7
    Last Post: 11th October 2011, 04:34 PM
  2. Best Practices: LDAP/Active Directory and Account Provisioning
    By cgabbadon in forum How do you do....it?
    Replies: 5
    Last Post: 16th December 2010, 10:48 AM
  3. Replies: 0
    Last Post: 22nd June 2009, 10:17 AM
  4. European SharePoint Best Practices Conference
    By rpwillis in forum Virtual Learning Platforms
    Replies: 9
    Last Post: 3rd April 2009, 11:52 AM
  5. Locally hosted external presence - best practices
    By amfony in forum How do you do....it?
    Replies: 3
    Last Post: 11th June 2008, 01:25 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •