|
|
You're in the
sql server msde
group:sqlservr.exe doesn't relase the memory
sql server msde:
[quoted text, click to view] Sreedhar wrote: > Hi Gijs, > > Thanks for the response. If this is the case that SqlServr.exe uses > the memory and is a normal behaviour, then how can i minimize it "on > exit of the application". I have already saw the solution saying to > set min and max memory. But, can't I minimize on exit? Pls help me. you cant... SQL Server is not dependent on your application behavior... it's a separate application/service running on it's own, eventually serving your application as well, among others, if any... what is the problem of SQL Server not releasing it's memory? -- Andrea Montanari (Microsoft MVP - SQL Server) http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0 (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual interface) --------- remove DMO to reply
Hello,
We are using MSDE for our application. The service MSSQL$App will start automatically or when the application is started. While using the application, the memory usage by sqlservr.exe will be increasing and when the application is closed, the sqlservr.exe is not releasing the memory or atleast the memory usage is not coming down. Can any one help on this? Is this a MSDE bug or our application should manually release the memory used by
Hi Gijs,
Thanks for the response. If this is the case that SqlServr.exe uses the memory and is a normal behaviour, then how can i minimize it "on exit of the application". I have already saw the solution saying to set min and max memory. But, can't I minimize on exit? Pls help me. -Sreedhar [quoted text, click to view] "Gijs Beukenoot" wrote:
> From Sreedhar : > > Hello, > > > > We are using MSDE for our application. The service MSSQL$App will start > > automatically or when the application is started. While using the > > application, the memory usage by sqlservr.exe will be increasing and when the > > application is closed, the sqlservr.exe is not releasing the memory or > > atleast the memory usage is not coming down. Can any one help on this? Is > > this a MSDE bug or our application should manually release the memory used by > > sqlservr.exe > > That is 'normal' behaviour of SQL, see > http://support.microsoft.com/default.aspx?scid=kb;en-us;321363 > >
From Sreedhar :
[quoted text, click to view] > Hello, > > We are using MSDE for our application. The service MSSQL$App will start > automatically or when the application is started. While using the > application, the memory usage by sqlservr.exe will be increasing and when the > application is closed, the sqlservr.exe is not releasing the memory or > atleast the memory usage is not coming down. Can any one help on this? Is > this a MSDE bug or our application should manually release the memory used by > sqlservr.exe That is 'normal' behaviour of SQL, see http://support.microsoft.com/default.aspx?scid=kb;en-us;321363
Hello Experts,
Your information was very useful. But, still i have some problem. My application runs on MSDE and not the SQLServer. And it is the only application that runs on this instance (MSSQL$APPNAME). I checked out an article at http://support.microsoft.com/default.aspx?scid=kb;en-us;321363 . This article applies to SQL 7.0 and SQL 2000. It does not mention MSDE. Is this applicable to MSDE also? If so, where can I find some thing more specific to MSDE. Please help me. -Sreedhar [quoted text, click to view] "Hugo Kornelis" wrote:
> On Thu, 8 Sep 2005 03:55:03 -0700, Sreedhar wrote: > > >Hi Gijs, > > > >Thanks for the response. If this is the case that SqlServr.exe uses the > >memory and is a normal behaviour, then how can i minimize it "on exit of the > >application". I have already saw the solution saying to set min and max > >memory. But, can't I minimize on exit? Pls help me. > > Hi Sreedhar, > > If your application is the only application taht requires the instance > of MSDE to be running, then you can modify the application to issue a > shutdown command on exit. But beware: there are several pitfalls: > > 1. If some other application unexpectedly also relies on the SQL Server > service being up and running, shutting it down won't make you many new > friends :-) > > 2. The SHUTDOWN command can only be issued by members of the sysadmin or > serveradmin fixed server roles. Having your application running with > that level of authority is a tremendous risk. > > I'd say, as Andrea also writes, that it's much better to just leave the > server running. If you're left with too little memory for your other > applications, get some extra memory or buy an extra machine to serve as > a dedicated database server. Hardware is cheap nowadays. > > Or you can just terminate the SQL Server service manually if you need to > free the memory occasionally. > > Best, Hugo > -- > > (Remove _NO_ and _SPAM_ to get my e-mail address)
[quoted text, click to view]
On Thu, 8 Sep 2005 03:55:03 -0700, Sreedhar wrote: >Hi Gijs, > >Thanks for the response. If this is the case that SqlServr.exe uses the >memory and is a normal behaviour, then how can i minimize it "on exit of the >application". I have already saw the solution saying to set min and max >memory. But, can't I minimize on exit? Pls help me. Hi Sreedhar, If your application is the only application taht requires the instance of MSDE to be running, then you can modify the application to issue a shutdown command on exit. But beware: there are several pitfalls: 1. If some other application unexpectedly also relies on the SQL Server service being up and running, shutting it down won't make you many new friends :-) 2. The SHUTDOWN command can only be issued by members of the sysadmin or serveradmin fixed server roles. Having your application running with that level of authority is a tremendous risk. I'd say, as Andrea also writes, that it's much better to just leave the server running. If you're left with too little memory for your other applications, get some extra memory or buy an extra machine to serve as a dedicated database server. Hardware is cheap nowadays. Or you can just terminate the SQL Server service manually if you need to free the memory occasionally. Best, Hugo --
From Hugo Kornelis :
[quoted text, click to view] > If your application is the only application taht requires the instance > of MSDE to be running, then you can modify the application to issue a > shutdown command on exit. But beware: there are several pitfalls: You could check the number of users, if you're the only active user, shutdown it down and start it again. That way, SQL willl start again at 'minimun' memory usage.
hi Sreedhar,
[quoted text, click to view] Sreedhar wrote: > Your information was very useful. But, still i have some problem. My > application runs on MSDE and not the SQLServer. And it is the only > application that runs on this instance (MSSQL$APPNAME). I checked out > an article at > http://support.microsoft.com/default.aspx?scid=kb;en-us;321363 . This > article applies to SQL 7.0 and SQL 2000. It does not mention MSDE. Is > this applicable to MSDE also? If so, where can I find some thing more > specific to MSDE. Please help me. > MSDE "IS" SQL Server... it's one of the available editions, with some limitations and without standard SQL Server Client Tools... -- Andrea Montanari (Microsoft MVP - SQL Server) http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0 (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual interface) --------- remove DMO to reply
On Fri, 09 Sep 2005 07:47:52 +0200, "Gijs Beukenoot"
[quoted text, click to view] <Gijs.DOT.Beukenoot@AT@Wanadoo.DOT.nl> wrote: >From Hugo Kornelis : >> If your application is the only application taht requires the instance >> of MSDE to be running, then you can modify the application to issue a >> shutdown command on exit. But beware: there are several pitfalls: > >You could check the number of users, if you're the only active user, >shutdown it down and start it again. That way, SQL willl start again at >'minimun' memory usage. > Hi Gijs, There are a few reasons why I would definitely NOT do it this way: - The number of active users (by which I presume you mean: connections) is a dangerous indication of (lack of) activity, to say the least. Many client programs are progrmmed to drop a connection when it's no longer used, reconnecting when they need to send data or execute a query. - If you MUST shutdown MSDE to reclaim the memory (and as I already stated in my previous message, that would NOT be my first choice - nor my second or third), then don't do it when you start the application, but when you terminate it. Doing it at start means that the time to start the application will rise (shutdown and startup of MSDE cost quite some time). Plus all data that might have bene in cache wil be flushed from memory, all memory will have to be allocated again, etc etc. Don't release the resources just before you're gooing to use it - release them when you're done using them. Best, Hugo --
From Hugo Kornelis :
[quoted text, click to view] > On Fri, 09 Sep 2005 07:47:52 +0200, "Gijs Beukenoot" <snap> <Gijs.DOT.Beukenoot@AT@Wanadoo.DOT.nl> wrote: > >> From Hugo Kornelis : >>> If your application is the only application taht requires the instance >>> of MSDE to be running, then you can modify the application to issue a >>> shutdown command on exit. But beware: there are several pitfalls: >> >> You could check the number of users, if you're the only active user, >> shutdown it down and start it again. That way, SQL willl start again at >> 'minimun' memory usage. >> > > Hi Gijs, > > There are a few reasons why I would definitely NOT do it this way: > [quoted text, click to view] > Best, Hugo I absolutely agree, it would be sort of a last resort... More memory in the machine would be my first and second choice, followed by a more dedicated server (running less other applications).
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |