Results 1 to 7 of 7
  1. #1
    Join Date
    Apr 2004
    Posts
    79

    Unanswered: Physical RAM stress test

    Hi,

    I have a new server where 32GB of RAM is installed and I have user databases on this server.I am using SQL server 2000 Enterprise edition and Platform is Windows 2003 adv server, which supports upto 128GB of memory.

    sp_configure 'awe enabled' is set to 1 and at OS level, AWE is enabled as well.

    max server memory (MB) is 2147483647

    I was doing some stress test on this server but memory usage doesn't go beyond 180MB....can someone suggest a test for physical RAM ?

    How can I make sure that application will make full use of available physical memory?

    Rgds
    Wilson

  2. #2
    Join Date
    May 2004
    Location
    Seattle
    Posts
    1,313
    what sorts of stress tests?

    sql server will cache pages in memory - if your database is so small that the entire thing will fit in RAM, then it's not big enough. You need a db at least several gb in size.

    site below has lots of good articles on sql server perf:
    http://www.sql-server-performance.com

    for example, on stress testing:
    http://www.sql-server-performance.co..._lessons_3.asp

  3. #3
    Join Date
    Nov 2006
    Posts
    1

    SQL Stress Test Tools

    There are some 3rd party SQL server stress testing tools out there that can enable you to do what you need. I believe Reg-gate has one, www.redgate.com, and Agilist has one called SQL Stress Test, www.agilist.com. There are probably a few more out there. Good luck.

  4. #4
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    Did you enable /PAE ? Without it, AWE is unusable.

    Just for what it is worth, have you considered using the 64 bit version of SQL Server? At least in our experience we can only use about 12 Gb or so via AWE before we reach a point of diminishing returns. The 64 bit version can use as much memory as we've been able to throw at it.

    -PatP

  5. #5
    Join Date
    Apr 2004
    Posts
    79
    Quote Originally Posted by Pat Phelan
    Did you enable /PAE ? Without it, AWE is unusable.

    Just for what it is worth, have you considered using the 64 bit version of SQL Server? At least in our experience we can only use about 12 Gb or so via AWE before we reach a point of diminishing returns. The 64 bit version can use as much memory as we've been able to throw at it.

    -PatP
    AWE is enabled as well..
    I guess we need to do following..

    Customers with this configuration should apply this hotfix after upgrading to SQL Server 2000 Service Pack 4.

    http://www.microsoft.com/downloads/d...DisplayLang=en

    Rgds

  6. #6
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    Oh yeah, I'd forgotten that little weasel. We don't run sp4 on any of our high end 32 bit servers. It caused us WAY too many problems when we tried to run it.

    -PatP

  7. #7
    Join Date
    Apr 2004
    Posts
    79
    Quote Originally Posted by Wilson77
    http://www.microsoft.com/downloads/d...DisplayLang=en

    Oh yeah, I'd forgotten that little weasel. We don't run sp4 on any of our high end 32 bit servers. It caused us WAY too many problems when we tried to run it.

    Rgds
    Yes, now I can see SQL server taking up 32GB of memory after applying above mentioned hotfix...

    Well so far, I have not seen any issues using SP4....(have been using it for a month or so for a UAT server).

Posting Permissions

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