Results 1 to 10 of 10
  1. #1
    Join Date
    Jan 2003
    Location
    Pittsburgh, PA
    Posts
    86

    Unanswered: SQL Server - Memory Usage

    I am using SQL Server 7.0 on a Windows NT machine. We have been having problems with SQL Server not releasing the memory after it has utilized it.

    Currently it is configured to allow a max of 511MB memory (1024 is total on the machine). I had some advice that my best solution would be to reduce the Max Memory to a lower value (say 400 MB) to help reduce the problem.

    Is this not counter-intuitive? Or is this the correct solution?

    Thanks.

  2. #2
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322

    Re: SQL Server - Memory Usage

    Originally posted by acg_ray
    I am using SQL Server 7.0 on a Windows NT machine. We have been having problems with SQL Server not releasing the memory after it has utilized it.
    Is that the problem? Why?
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  3. #3
    Join Date
    Jan 2003
    Location
    Pittsburgh, PA
    Posts
    86

    Re: SQL Server - Memory Usage

    I'll phrase my concern/question another way: over a period of time, I start to see a sluggish performance in the SQL Server. Is the fact that SQL Server is not releasing memory an issue for SQL Server's performance, or would that only be an issue for the other applications (very few) running on the same machine?

  4. #4
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    It actually shouldn't be an issue for either. The way SQL Server is supposed to work is by gobbling up as much memory as it needs, until the operating system starts telling it that other applications want to play too. So long as these other applications are relatively static in their memory needs, a sort of balance will be achieved. But if the upstart applications storms in, eats 100MB of memory, then closes in under a few minutes, then SQL Server will not have enough time to give up its memory, and you may encounter some page file usage.

    As for SQL Seeming to be sluggish after tme, not sure what that could be. Have you set up perfmon to monitor the box? Maybe some sort of resource (memory) leak?

  5. #5
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    I never run apps on the db server...all I know is, give sql all it needs and don't worry about it.

    Seems like you've even carved out some....

    What do you mean by "sluggish"

    tempdb getting full...lock escalation...those will make sql server look sluggish

    you get a lot of transactions?

    How do user connect to the database?

    IS it sluggish from a user or admin perspective?

    Is it cold in Pittsburgh?
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  6. #6
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Provided Answers: 1
    "over a period of time"

    What does this mean? That it works fast after you reboot and then slows down, or that it has slowed down continuously since the database was added?

    How have you been fixing the problem?

    blindman

  7. #7
    Join Date
    Feb 2002
    Posts
    2,232
    Probably restart the sql server service. What other applications are running on this server ? How often are you rebooting/restarting the server/sql server service ? When is it not cold in pittsburgh ?

  8. #8
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Provided Answers: 1
    ...and what kind of maintenance do you do?

    blindman

  9. #9
    Join Date
    Jan 2004
    Posts
    1

    Arrow Re: SQL Server - Memory Usage

    i suggest create maintenance plan for optimisation my friend. and also u havent mentioned db size temp db info . run this index tuning wizard... remove or add proper indexes.. it will ease down stress on sql server

  10. #10
    Join Date
    Jan 2003
    Location
    Pittsburgh, PA
    Posts
    86

    Re: SQL Server - Memory Usage

    Thanks for all the responses.

    After a period of 9-11 days, I'll see the response time to user requests slow down; a restart clears this up.

    I have a DB Maintenance plan than runs every weekend to reduce the DB size, reset the indexes, etc. Pretty much all the standard features.

    The total size of the 5 DBs is only 4GB, so we're not talking about anything significant in terms of size. Number of transactions is low (thousands, instead of millions...). Number of users is relatively small (two dozen).

    DB Backup is every evening.

    The responses here have lowered my concerns that the SQL server memory is the issue, and will allow me to focus on the application connection, and other aspects to the server.

    Thanks.

Posting Permissions

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