Post reply

SQL Enterprise questions

  • October 30, 2006 at 7:02 am

    #61565

    Hi,

    I recently took over all SQL Instances at my company, and were currently trying to cut down our servers. I have many SQL Standard 2000 servers running only one small database. We are looking into running multiple Enterprise servers instead. Can someone tell me what the memory/database limit is on an enterprise server and any other recommendations you would make instead of this? Thanks in advance.

  • October 30, 2006 at 7:27 am

    #668703

    I think it's whatever OS you have. Pretty sure you also need Windows 2000 Adv Server or Windows 2003 Enterprise also.

  • October 30, 2006 at 7:33 am

    #668705

    Well I figured that also, I plan on using Server 2003 Ent with 8GB of ram in each. I just wanted to know how much memory or how many databases I should use.

    Also, anyone know if I install a second SQL Instance on the same box if it costs another license?

  • October 31, 2006 at 12:57 pm

    #669055

    I'm not aware of a limit to the number of databases you can have on a single server (there probably is, but there are people who have hundreds of DBs on a single server). If you don't require multiple instances, there is no point in doing that. The question about number is tough without knowing your usage patterns. If it were me, I'd transfer them one at a time, and use Profiler to watch activity and performance.

    So long, and thanks for all the fish,

    Russell Shilling, MCDBA, MCSA 2K3, MCSE 2K3

  • October 31, 2006 at 1:55 pm

    #669070

    yes, of course it would be another license for another instance.

    Thank-you,
    David Russell
    Any Cloud, Any Database, Oracle since 1982

  • October 31, 2006 at 2:18 pm

    #669077

    There are so many questions to ask in order to begin to perform a high level analysis of the situation. It's a project in and of itself to gather all of the information that you'll probably need to attempt to determine your proposed server architecture and plans for implementatinon. Well let's give it a kick start:

    • How many SQL Servers are there ?
    • Are the SQL Servers all the same version and service pack (possibly hot fix as well) ?
    • Are your SQL Servers 'dedicated' servers ?

    • Do your SQL Servers they have application software installed on them ?
    • Do your SQL Servers have IIS installed on them ?

  • How many databases do you have ?
  • How 'large' are your databses (and how many) ?

    • Less than 10 Gb
    • Less than 100 Gb
    • Greater than 100 Gb

  • How are your database applications split ?

    •  -OLTP - Online Transaction Processing
    •  -Batch
    •  -DSS - Decision Support Systems

  • Are any of your applications using:

    • DTS
    • Full Text Search
    • Analysis Server
    • Reporting Services

  • How would you categorize your applications ?

    • Available 24x7
    • Available 9 to 5
    • Available 'other' hours

  • What kind of 'maintenance window' or SLA (Service level agreement) do you have for each application ?
  • How are you performing database backups ?

    • Directly to tape ?
    • To disk, then to tape ?

  • What kind of storage do your SQL Servers use ?

    • Internal disks
    • DAS - Direct attached storage
    • SAN storage
    • Some 'other' combination

  • Are you using SAN storage today ?
  • If you are not using SAN storage today, will this server consolidation include SAN storage ?
  • Are you looking for high-availabilty using clustering ?
  • Are you looking for DR (disaster recovery) capability using 'hot' spare servers and log shipping ?

    • RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply