SQL Server Performance

"AWE enabled" memory usage question.

Discussion in 'Performance Tuning for DBAs' started by aristobrat, Jul 14, 2006.

  1. aristobrat New Member

    I've recently "inherited" a SQL Server at work that I didn't build myself, so I was poking around yesterday.

    It's SQL 2000 Enterprise (SP3), running on Windows 2000 Server Enterprise box that has 8GB of RAM. SQL is the only application running on that box.

    I noticed that the server's boot.ini included the "/pae" switch to enable access to all of the RAM, but "awe enabled" *wasn't* configured in SQL.

    After enabling awe in SQL (and restarting the SQL service), the amount of memory that SQL uses doesn't appear to have changed.

    Before enabling AWE, it's using 1.59GB out of 6.98GB.
    After AWE, it's using 1.60GB out of 6.98GB.

    Does anything sound fishy there?

    This server hosts ~60 databases, typically has 300-400 sessions (but usually only 20-30 active ones), and the batches per second ranges from 200-400.

  2. joechang New Member

    go to Entprise Manager -> your server -> Manamgement -> SQL Server Logs

    look for an entry like: user rights .. lock pages in memory

    then for the user account that SQL Server started under, grant that right
  3. joechang New Member

  4. aristobrat New Member

    I appreciate the quick reply -- that was exactly what was wrong.

    Little embarassed I didn't see bj007's thread when I searched earlier though!

    Thanks again!!!!!!

Share This Page