Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Connection memory usage is growing steadily Expand / Collapse
Author
Message
Posted Monday, January 28, 2013 10:06 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, January 29, 2013 5:19 AM
Points: 4, Visits: 14
Issue: SQL connection memory usage is growing steadily (8G after only 2 days). It can keep increasing to use all rest system memory.

System: SQL 2008 R2 on Windows R2 with 64G RAM. Max SQL memory setting: 56G. Both Buffer Cache and Procedure Cache are normal. CPU usage is normal. Average number of user connection 70-100.

Is there a way we can find out the connection memory usage details? Can we release connection memory usage without restart SQL?
Post #1412527
Posted Monday, January 28, 2013 10:15 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, January 29, 2013 5:19 AM
Points: 4, Visits: 14
Sorry it is a sql 2008 question. Moved to 2008 forums.
Post #1412537
Posted Monday, January 28, 2013 10:59 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 9:14 AM
Points: 12,918, Visits: 32,088
that is by design, and the normal behaviour for SQL server:

SQL tries to keep everything in memory to support subsequent queries. if you leave an installation at it's default settings(2 Terabytes?,which is more memory than anyone realistically will ever own), it will use ALL of the memory, and possibly starve the operating system for memory as well.

The whole idea is to keep everything in memory, instead of going to disk, as that IO operation slows things down.

it is not like other programs, that give memory back when it is "done"...it's never done, as far as SQL is concerned.

you can limit the amount of memory int eh memory settings under the server properties in the SSMS Object Explorer:



Lowell

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #1412565
Posted Monday, January 28, 2013 11:16 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, January 29, 2013 5:19 AM
Points: 4, Visits: 14
Lowell (1/28/2013)
that is by design, and the normal behaviour for SQL server:

SQL tries to keep everything in memory to support subsequent queries. if you leave an installation at it's default settings(2 Terabytes?,which is more memory than anyone realistically will ever own), it will use ALL of the memory, and possibly starve the operating system for memory as well.

The whole idea is to keep everything in memory, instead of going to disk, as that IO operation slows things down.

it is not like other programs, that give memory back when it is "done"...it's never done, as far as SQL is concerned.

you can limit the amount of memory int eh memory settings under the server properties in the SSMS Object Explorer:



Thanks Lowell.

As mentioned in the post, we set the max memory. Buffer Cache and Procedure Cache both are fine. But the connection memory keeps increasing and eventually eat all 56G memory and none process can be going on.

Post #1412572
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse