Does SQL release Ram when its needed

Does SQL release Ram when its needed elsewhere (like Exchange's store.exe)?
I have a server with 2.6 gigs of ram and SQL is using 1 GB idle.SQL will release RAM if the system starts paging. Otherwise, it will
continue to hold allocated memory.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Matt" <anonymous@.discussions.microsoft.com> wrote in message
news:BA71FDB6-DC93-43A1-9B47-B76DC485B5FF@.microsoft.com...
> Does SQL release Ram when its needed elsewhere (like Exchange's
store.exe)?
> I have a server with 2.6 gigs of ram and SQL is using 1 GB idle.|||"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:ey1xSF7$DHA.212@.TK2MSFTNGP12.phx.gbl...
> SQL will release RAM if the system starts paging. Otherwise, it will
> continue to hold allocated memory.
>
Just to follow up, this means that on machines which are not dedicated
database servers SQL Server should have an upper limit placed on its memory.
Just reserve 256M or 512M for Sql Server. If you reserve too little, then
you will have excessive physical IO. If you reserve more than enough, you
won't get any added benefit.
David

Does SQL release Ram when its needed

Does SQL release Ram when its needed elsewhere (like Exchange's store.exe)?
I have a server with 2.6 gigs of ram and SQL is using 1 GB idle.SQL will release RAM if the system starts paging. Otherwise, it will
continue to hold allocated memory.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Matt" <anonymous@.discussions.microsoft.com> wrote in message
news:BA71FDB6-DC93-43A1-9B47-B76DC485B5FF@.microsoft.com...
> Does SQL release Ram when its needed elsewhere (like Exchange's
store.exe)?
> I have a server with 2.6 gigs of ram and SQL is using 1 GB idle.|||Hi Matt,
Yes, SQL Server do release the memory when the OS asks
for. You can also tell SQL Server to use a fixed memory if
there are any other applications co-exist on the same Box.
Memory Architecture
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/architec/8_ar_sa_4rc5.asp
Server Memory Options
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/adminsql/ad_config_9zfy.asp
Regards
Thirumal
Sys Admin
www.sstil.com
>--Original Message--
>Does SQL release Ram when its needed elsewhere (like
Exchange's store.exe)?
>I have a server with 2.6 gigs of ram and SQL is using 1
GB idle.
>.
>|||"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:ey1xSF7$DHA.212@.TK2MSFTNGP12.phx.gbl...
> SQL will release RAM if the system starts paging. Otherwise, it will
> continue to hold allocated memory.
>
Just to follow up, this means that on machines which are not dedicated
database servers SQL Server should have an upper limit placed on its memory.
Just reserve 256M or 512M for Sql Server. If you reserve too little, then
you will have excessive physical IO. If you reserve more than enough, you
won't get any added benefit.
David

Does anyone use SSIS for database schema maintenance?

We currently use SSIS to build DTS packages in which we store changes
to our database schema, as well as scripts that need to be run upon
each release. This works well for small sets of changes that never
need to be updated or for architectures with only one database.

We store each of the changes included in the package in separate
files, which are tracked using version control. It is growing time
consuming to maintain parity between those files and what is in the
SSIS.

Furthermore, we have been unable to discover an easy way to load a
file's contents into a package SQL Task without opening the file and
copy-pasting the contents into a new SQL task.

ANY information at all would be extremely appreciated!On Feb 28, 2:54 pm, "Ben" <vanev...@.gmail.comwrote:

Quote:

Originally Posted by

We currently use SSIS to build DTS packages in which we store changes
to our database schema, as well as scripts that need to be run upon
each release. This works well for small sets of changes that never
need to be updated or for architectures with only one database.
>
We store each of the changes included in the package in separate
files, which are tracked using version control. It is growing time
consuming to maintain parity between those files and what is in the
SSIS.
>
Furthermore, we have been unable to discover an easy way to load a
file's contents into a package SQL Task without opening the file and
copy-pasting the contents into a new SQL task.
>
ANY information at all would be extremely appreciated!

Hi Ben,

There is a rock solid change management process for SQL Server
2000/2005 and it is provided by the DB Ghost toolset from
Innovartis.

The essence of the process is that you script out all the database
objects and lookup (static) data into individual CREATE / INSERT
scripts and put them under source control. The whole dev team then
checks these files out, makes the required changes to the CREATE
statements and checks them back in again (this can scale to thousand
of developers). Once you're ready to release the schema to the test
environment you use the DB Ghost Change Manager tool to make the
target database match the set of source scripts. If, for example, a
developer added a column to a table CREATE script then the Change
Manager would detect this and add the column to the target database
seamlessly.

Basically, DB Ghost enables you to develop in the same way as you do
for a greenfield (release 1) database for every subsequent release of
your schema without losing any data in the target database.

Our customers rave about DB Ghost and can't believe the cost savings
it brings - have a look for yourself :)

www.dbghost.com
Kind regards,

Malcolm

Does "MSDE 2000 Release A" only can support 2GB database?

It is very important to me. thank you.
Hi
Yes. Built in limitation for MSDE 2000.
For anything bigger, you need to use Standard Edition.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"kingou" <kingou@.huawei.com> wrote in message
news:262a01c4e991$c5827f10$a401280a@.phx.gbl...
> It is very important to me. thank you.