MSDE Memory Usage for Desktop Users

Hi all,
We are developing an application that uses MSDE as the database backend
running on the client's computer. As I understand it, SQL Server's memory
management model allows it to basically use as much memory as it possible
can when under heavy load. Then having allocated that much memory, SQL
Server will not release it unless another program needs it. Does MSDE work
in the same way? Would it be possible to signal SQL Server to release some
memory? If so, then we could signal MSDE to release some memory after we
have finished our major data crunching. This might at least give our
clients some relief as they have a tendency to become disconcerted by
whatever Task Manager tells them, no matter how much I tell them that SQL
Server will easily give up memory to allow other programs to run.
Thanks for any insight.
Jonathan
hi Jonathan,
"Jonathan Van Eenwyk" <jonathanve@.myrealbox.com> ha scritto nel messaggio
news:10hfeqaftls4778@.corp.supernews.com...
> Hi all,
> We are developing an application that uses MSDE as the database backend
> running on the client's computer. As I understand it, SQL Server's memory
> management model allows it to basically use as much memory as it possible
> can when under heavy load. Then having allocated that much memory, SQL
> Server will not release it unless another program needs it. Does MSDE
work
> in the same way? Would it be possible to signal SQL Server to release
some
> memory? If so, then we could signal MSDE to release some memory after we
> have finished our major data crunching. This might at least give our
> clients some relief as they have a tendency to become disconcerted by
> whatever Task Manager tells them, no matter how much I tell them that SQL
> Server will easily give up memory to allow other programs to run.
> Thanks for any insight.
> Jonathan
>
you can't... SQL Server (and MSDE so far) are totally disregarding
application signal... you can only limit it' memory footprint overriding the
dynamic memory configuration, setting a fixed upperbound limit...
please have a look at
http://msdn.microsoft.com/library/de...onfig_9zfy.asp
for further info about fixing memory...
another article, by Ken Henderson, available at
http://msdn.microsoft.com/library/de...v_03252004.asp
is worth reading too...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
Alright. Thanks! Seems like that would be nice feature in a desktop
situation, but I guess that's not the real purpose of SQL Server.
Jonathan
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2nsbhvF46n5eU1@.uni-berlin.de...[vbcol=seagreen]
> hi Jonathan,
> "Jonathan Van Eenwyk" <jonathanve@.myrealbox.com> ha scritto nel messaggio
> news:10hfeqaftls4778@.corp.supernews.com...
memory[vbcol=seagreen]
possible[vbcol=seagreen]
> work
> some
we[vbcol=seagreen]
SQL
> you can't... SQL Server (and MSDE so far) are totally disregarding
> application signal... you can only limit it' memory footprint overriding
the
> dynamic memory configuration, setting a fixed upperbound limit...
> please have a look at
>
http://msdn.microsoft.com/library/de...onfig_9zfy.asp
> for further info about fixing memory...
> another article, by Ken Henderson, available at
>
http://msdn.microsoft.com/library/de...v_03252004.asp
> is worth reading too...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Jonathan,
"Jonathan Van Eenwyk" <jonathanve@.myrealbox.com> ha scritto nel messaggio
news:10hi63aggt5ja4b@.corp.supernews.com...
> Andrea,
> Alright. Thanks! Seems like that would be nice feature in a desktop
> situation, but I guess that's not the real purpose of SQL Server.
really not... =;-DD
SQL Server is suited to perform it's work the best it can and as quick it
can, with no regards (or little) to other boring users =;-DD
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply