SQL Server Performance

SQL Server 2000 Standard / Windows 2003 Standard / 4gb Ram

Discussion in 'Performance Tuning for Hardware Configurations' started by Jam_Man, Sep 7, 2007.

  1. Jam_Man New Member

    Hi all,
    Im new to sql server so go easy with me :)
    Ive inherited a Windows 2003standard server that runs a db on SQL server 2000 standard edition.
    The server has 4gb physical RAM and at any given point is only utilising 2.2gb maximum.
    Can standard edition utilise more than 2gb as whilst Ive read how Enterprise edition can do so Ive not seen any evidence it can, but on another forum Ive told Standard can support up to 4gb with switches.
    Any enlightenment would be appreciated.
    thanks
    JM







    Jam_Man, Sep 7, 2007
    #2

  2. merrillaldrich New Member

    SQL Server 2000 Standard is "capped" at a memory limit that corresponds to the maximum practical memory use on a dedicated SQL box running Windows 32-bit OS with 4 GB RAM (the maximum addressable RAM for a 32-bit OS.)
    To access more RAM (you might not need to, which is something to very carefully investigate) you have these choices:
    1. SQL Server 2000 Enterprise, IMHO a waste of money at this point in time
    2. SQL Server 2005 Standard, which lifts the RAM limit totally. You can run this on Windows 32-bit + AWE and over 4GB RAM, or -- better -- on Windows 64-bit with more than 4 GB RAM
    Make sure you really need the RAM first, though, before spending a pile of money :)

    merrillaldrich, Sep 7, 2007
    #3

  3. satya Moderator

    As referred SQL 2000 standard edition is limited by default to 2GB, in this case you could look into SQL 2005 possibilities where you can be assured for next 3 years on the usage of resources for performance.
    satya, Sep 10, 2007
    #4

  4. Jam_Man New Member

    We actually do have sql std 2005, but our software developers dont yet support it which is really impressive.
    So whilst 2000 std is capped at 2gb by default is there a way to increase it to 3gb ?

    Jam_Man, Sep 11, 2007
    #5

  5. satya Moderator

    No chance as it is by default in SQL 2000 SE, you have better option in going to SQL 2005 SE in this case.
    satya, Sep 11, 2007
    #6

Share This Page