Hi,
I open one of the modules in my program and then close
it. I did not end the program. The memory usage in the
SQL server does not decrease or remove from it. I check
it from the Process Info at the Management folder in the
database. How to release the memory from the SQL server?
Is it the programming method that I am using or this
behaviour is normal?
Please help. Thanks
If you are referring to the database server, this behaviour is normal. SQL
Server will try to claim all system memory for itself, less ~5 MB, upon
startup. It works more efficiently that way, hence the often repeated
advice that you should try to use a dedicated database sever. Thus, you
might have 100 connections and close all of them, but the memory used by SQL
Server will not decrease.
If you want to, you can limit the min. and max. amount of memory SQL Server
can use from Enterprise Manager.
Peter Yeoh
http://www.yohz.com
Need smaller backups? Try MiniSQLBackup
"carina" <carina_a@.yahoo.com> wrote in message
news:19fd501c44ddd$038649a0$a501280a@.phx.gbl...
> Hi,
> I open one of the modules in my program and then close
> it. I did not end the program. The memory usage in the
> SQL server does not decrease or remove from it. I check
> it from the Process Info at the Management folder in the
> database. How to release the memory from the SQL server?
> Is it the programming method that I am using or this
> behaviour is normal?
> Please help. Thanks
Showing posts with label decrease. Show all posts
Showing posts with label decrease. Show all posts
Monday, March 19, 2012
Memory usage increasing
Hi,
I open one of the modules in my program and then close
it. I did not end the program. The memory usage in the
SQL server does not decrease or remove from it. I check
it from the Process Info at the Management folder in the
database. How to release the memory from the SQL server?
Is it the programming method that I am using or this
behaviour is normal?
Please help. ThanksIf you are referring to the database server, this behaviour is normal. SQL
Server will try to claim all system memory for itself, less ~5 MB, upon
startup. It works more efficiently that way, hence the often repeated
advice that you should try to use a dedicated database sever. Thus, you
might have 100 connections and close all of them, but the memory used by SQL
Server will not decrease.
If you want to, you can limit the min. and max. amount of memory SQL Server
can use from Enterprise Manager.
Peter Yeoh
http://www.yohz.com
Need smaller backups? Try MiniSQLBackup
"carina" <carina_a@.yahoo.com> wrote in message
news:19fd501c44ddd$038649a0$a501280a@.phx.gbl...
> Hi,
> I open one of the modules in my program and then close
> it. I did not end the program. The memory usage in the
> SQL server does not decrease or remove from it. I check
> it from the Process Info at the Management folder in the
> database. How to release the memory from the SQL server?
> Is it the programming method that I am using or this
> behaviour is normal?
> Please help. Thanks
I open one of the modules in my program and then close
it. I did not end the program. The memory usage in the
SQL server does not decrease or remove from it. I check
it from the Process Info at the Management folder in the
database. How to release the memory from the SQL server?
Is it the programming method that I am using or this
behaviour is normal?
Please help. ThanksIf you are referring to the database server, this behaviour is normal. SQL
Server will try to claim all system memory for itself, less ~5 MB, upon
startup. It works more efficiently that way, hence the often repeated
advice that you should try to use a dedicated database sever. Thus, you
might have 100 connections and close all of them, but the memory used by SQL
Server will not decrease.
If you want to, you can limit the min. and max. amount of memory SQL Server
can use from Enterprise Manager.
Peter Yeoh
http://www.yohz.com
Need smaller backups? Try MiniSQLBackup
"carina" <carina_a@.yahoo.com> wrote in message
news:19fd501c44ddd$038649a0$a501280a@.phx.gbl...
> Hi,
> I open one of the modules in my program and then close
> it. I did not end the program. The memory usage in the
> SQL server does not decrease or remove from it. I check
> it from the Process Info at the Management folder in the
> database. How to release the memory from the SQL server?
> Is it the programming method that I am using or this
> behaviour is normal?
> Please help. Thanks
Memory usage increasing
Hi,
I open one of the modules in my program and then close
it. I did not end the program. The memory usage in the
SQL server does not decrease or remove from it. I check
it from the Process Info at the Management folder in the
database. How to release the memory from the SQL server?
Is it the programming method that I am using or this
behaviour is normal?
Please help. ThanksIf you are referring to the database server, this behaviour is normal. SQL
Server will try to claim all system memory for itself, less ~5 MB, upon
startup. It works more efficiently that way, hence the often repeated
advice that you should try to use a dedicated database sever. Thus, you
might have 100 connections and close all of them, but the memory used by SQL
Server will not decrease.
If you want to, you can limit the min. and max. amount of memory SQL Server
can use from Enterprise Manager.
Peter Yeoh
http://www.yohz.com
Need smaller backups? Try MiniSQLBackup
"carina" <carina_a@.yahoo.com> wrote in message
news:19fd501c44ddd$038649a0$a501280a@.phx
.gbl...
> Hi,
> I open one of the modules in my program and then close
> it. I did not end the program. The memory usage in the
> SQL server does not decrease or remove from it. I check
> it from the Process Info at the Management folder in the
> database. How to release the memory from the SQL server?
> Is it the programming method that I am using or this
> behaviour is normal?
> Please help. Thanks
I open one of the modules in my program and then close
it. I did not end the program. The memory usage in the
SQL server does not decrease or remove from it. I check
it from the Process Info at the Management folder in the
database. How to release the memory from the SQL server?
Is it the programming method that I am using or this
behaviour is normal?
Please help. ThanksIf you are referring to the database server, this behaviour is normal. SQL
Server will try to claim all system memory for itself, less ~5 MB, upon
startup. It works more efficiently that way, hence the often repeated
advice that you should try to use a dedicated database sever. Thus, you
might have 100 connections and close all of them, but the memory used by SQL
Server will not decrease.
If you want to, you can limit the min. and max. amount of memory SQL Server
can use from Enterprise Manager.
Peter Yeoh
http://www.yohz.com
Need smaller backups? Try MiniSQLBackup
"carina" <carina_a@.yahoo.com> wrote in message
news:19fd501c44ddd$038649a0$a501280a@.phx
.gbl...
> Hi,
> I open one of the modules in my program and then close
> it. I did not end the program. The memory usage in the
> SQL server does not decrease or remove from it. I check
> it from the Process Info at the Management folder in the
> database. How to release the memory from the SQL server?
> Is it the programming method that I am using or this
> behaviour is normal?
> Please help. Thanks
Monday, March 12, 2012
Memory Usage
Hi
When you start SQL Server, SQL Server memory usage may continue to steadily increase and not decrease, even when activity on the server is low. Additionally, the Task Manager and Performance Monitor may show that the physical memory available on the compu
ter is steadily decreasing until the available memory is between 4 to 10 MB.
This behavior alone does not indicate a memory leak. This behavior is normal and is an intended behavior of the SQL Server buffer pool.
Any solution
Thanks
Vinod
Solution to what ? What you just stated is normal from a SQL server memory
consumption .
"Vinod" <Vinod@.discussions.microsoft.com> wrote in message
news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> Hi
> When you start SQL Server, SQL Server memory usage may continue to
steadily increase and not decrease, even when activity on the server is low.
Additionally, the Task Manager and Performance Monitor may show that the
physical memory available on the computer is steadily decreasing until the
available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
normal and is an intended behavior of the SQL Server buffer pool.
> Any solution
> Thanks
> Vinod
|||Hi Vinod,
This is a normal situation and will not be an issue if your server is
dedicated for SQL server alone. SQL Server
will release the memory if operating system requires more physical memory.
To restrict the memory usage you can set the memory to static. Set the "min
server memory and max server memory" to the same value.
See the details in "memory, max server memory option" in books online.
Thanks
Hari
MCDBA
"Vinod" <Vinod@.discussions.microsoft.com> wrote in message
news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> Hi
> When you start SQL Server, SQL Server memory usage may continue to
steadily increase and not decrease, even when activity on the server is low.
Additionally, the Task Manager and Performance Monitor may show that the
physical memory available on the computer is steadily decreasing until the
available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
normal and is an intended behavior of the SQL Server buffer pool.
> Any solution
> Thanks
> Vinod
|||Hi Hari Prasad,
Thank you, I will try setting the min and max memory usage
Regards
Vinod
"Hari Prasad" wrote:
> Hi Vinod,
> This is a normal situation and will not be an issue if your server is
> dedicated for SQL server alone. SQL Server
> will release the memory if operating system requires more physical memory.
> To restrict the memory usage you can set the memory to static. Set the "min
> server memory and max server memory" to the same value.
> See the details in "memory, max server memory option" in books online.
> --
> Thanks
> Hari
> MCDBA
> "Vinod" <Vinod@.discussions.microsoft.com> wrote in message
> news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> steadily increase and not decrease, even when activity on the server is low.
> Additionally, the Task Manager and Performance Monitor may show that the
> physical memory available on the computer is steadily decreasing until the
> available memory is between 4 to 10 MB.
> normal and is an intended behavior of the SQL Server buffer pool.
>
>
|||If there aren't any performance issues currently on the Server then let the memory be managed dynamically instead of setting min and max values.
IN general leaving dynamic settings for memory on SQL is preferrable for better performance. If other application are sharing the server resources then you may test and set the values.
HTH
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Performance topic.
"Vinod" wrote:
[vbcol=seagreen]
> Hi Hari Prasad,
> Thank you, I will try setting the min and max memory usage
> Regards
> Vinod
> "Hari Prasad" wrote:
When you start SQL Server, SQL Server memory usage may continue to steadily increase and not decrease, even when activity on the server is low. Additionally, the Task Manager and Performance Monitor may show that the physical memory available on the compu
ter is steadily decreasing until the available memory is between 4 to 10 MB.
This behavior alone does not indicate a memory leak. This behavior is normal and is an intended behavior of the SQL Server buffer pool.
Any solution
Thanks
Vinod
Solution to what ? What you just stated is normal from a SQL server memory
consumption .
"Vinod" <Vinod@.discussions.microsoft.com> wrote in message
news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> Hi
> When you start SQL Server, SQL Server memory usage may continue to
steadily increase and not decrease, even when activity on the server is low.
Additionally, the Task Manager and Performance Monitor may show that the
physical memory available on the computer is steadily decreasing until the
available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
normal and is an intended behavior of the SQL Server buffer pool.
> Any solution
> Thanks
> Vinod
|||Hi Vinod,
This is a normal situation and will not be an issue if your server is
dedicated for SQL server alone. SQL Server
will release the memory if operating system requires more physical memory.
To restrict the memory usage you can set the memory to static. Set the "min
server memory and max server memory" to the same value.
See the details in "memory, max server memory option" in books online.
Thanks
Hari
MCDBA
"Vinod" <Vinod@.discussions.microsoft.com> wrote in message
news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> Hi
> When you start SQL Server, SQL Server memory usage may continue to
steadily increase and not decrease, even when activity on the server is low.
Additionally, the Task Manager and Performance Monitor may show that the
physical memory available on the computer is steadily decreasing until the
available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
normal and is an intended behavior of the SQL Server buffer pool.
> Any solution
> Thanks
> Vinod
|||Hi Hari Prasad,
Thank you, I will try setting the min and max memory usage
Regards
Vinod
"Hari Prasad" wrote:
> Hi Vinod,
> This is a normal situation and will not be an issue if your server is
> dedicated for SQL server alone. SQL Server
> will release the memory if operating system requires more physical memory.
> To restrict the memory usage you can set the memory to static. Set the "min
> server memory and max server memory" to the same value.
> See the details in "memory, max server memory option" in books online.
> --
> Thanks
> Hari
> MCDBA
> "Vinod" <Vinod@.discussions.microsoft.com> wrote in message
> news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> steadily increase and not decrease, even when activity on the server is low.
> Additionally, the Task Manager and Performance Monitor may show that the
> physical memory available on the computer is steadily decreasing until the
> available memory is between 4 to 10 MB.
> normal and is an intended behavior of the SQL Server buffer pool.
>
>
|||If there aren't any performance issues currently on the Server then let the memory be managed dynamically instead of setting min and max values.
IN general leaving dynamic settings for memory on SQL is preferrable for better performance. If other application are sharing the server resources then you may test and set the values.
HTH
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Performance topic.
"Vinod" wrote:
[vbcol=seagreen]
> Hi Hari Prasad,
> Thank you, I will try setting the min and max memory usage
> Regards
> Vinod
> "Hari Prasad" wrote:
Memory Usage
Hi
When you start SQL Server, SQL Server memory usage may continue to steadily
increase and not decrease, even when activity on the server is low. Addition
ally, the Task Manager and Performance Monitor may show that the physical me
mory available on the compu
ter is steadily decreasing until the available memory is between 4 to 10 MB.
This behavior alone does not indicate a memory leak. This behavior is normal
and is an intended behavior of the SQL Server buffer pool.
Any solution
Thanks
VinodSolution to what ? What you just stated is normal from a SQL server memory
consumption .
"Vinod" <Vinod@.discussions.microsoft.com> wrote in message
news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> Hi
> When you start SQL Server, SQL Server memory usage may continue to
steadily increase and not decrease, even when activity on the server is low.
Additionally, the Task Manager and Performance Monitor may show that the
physical memory available on the computer is steadily decreasing until the
available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
normal and is an intended behavior of the SQL Server buffer pool.
> Any solution
> Thanks
> Vinod|||Hi Vinod,
This is a normal situation and will not be an issue if your server is
dedicated for SQL server alone. SQL Server
will release the memory if operating system requires more physical memory.
To restrict the memory usage you can set the memory to static. Set the "min
server memory and max server memory" to the same value.
See the details in "memory, max server memory option" in books online.
Thanks
Hari
MCDBA
"Vinod" <Vinod@.discussions.microsoft.com> wrote in message
news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> Hi
> When you start SQL Server, SQL Server memory usage may continue to
steadily increase and not decrease, even when activity on the server is low.
Additionally, the Task Manager and Performance Monitor may show that the
physical memory available on the computer is steadily decreasing until the
available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
normal and is an intended behavior of the SQL Server buffer pool.
> Any solution
> Thanks
> Vinod|||Hi Hari Prasad,
Thank you, I will try setting the min and max memory usage
Regards
Vinod
"Hari Prasad" wrote:
> Hi Vinod,
> This is a normal situation and will not be an issue if your server is
> dedicated for SQL server alone. SQL Server
> will release the memory if operating system requires more physical memory.
> To restrict the memory usage you can set the memory to static. Set the "mi
n
> server memory and max server memory" to the same value.
> See the details in "memory, max server memory option" in books online.
> --
> Thanks
> Hari
> MCDBA
> "Vinod" <Vinod@.discussions.microsoft.com> wrote in message
> news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> steadily increase and not decrease, even when activity on the server is lo
w.
> Additionally, the Task Manager and Performance Monitor may show that the
> physical memory available on the computer is steadily decreasing until the
> available memory is between 4 to 10 MB.
> normal and is an intended behavior of the SQL Server buffer pool.
>
>|||If there aren't any performance issues currently on the Server then let the
memory be managed dynamically instead of setting min and max values.
IN general leaving dynamic settings for memory on SQL is preferrable for bet
ter performance. If other application are sharing the server resources then
you may test and set the values.
HTH
--
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Perform
ance topic.
"Vinod" wrote:
[vbcol=seagreen]
> Hi Hari Prasad,
> Thank you, I will try setting the min and max memory usage
> Regards
> Vinod
> "Hari Prasad" wrote:
>
When you start SQL Server, SQL Server memory usage may continue to steadily
increase and not decrease, even when activity on the server is low. Addition
ally, the Task Manager and Performance Monitor may show that the physical me
mory available on the compu
ter is steadily decreasing until the available memory is between 4 to 10 MB.
This behavior alone does not indicate a memory leak. This behavior is normal
and is an intended behavior of the SQL Server buffer pool.
Any solution
Thanks
VinodSolution to what ? What you just stated is normal from a SQL server memory
consumption .
"Vinod" <Vinod@.discussions.microsoft.com> wrote in message
news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> Hi
> When you start SQL Server, SQL Server memory usage may continue to
steadily increase and not decrease, even when activity on the server is low.
Additionally, the Task Manager and Performance Monitor may show that the
physical memory available on the computer is steadily decreasing until the
available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
normal and is an intended behavior of the SQL Server buffer pool.
> Any solution
> Thanks
> Vinod|||Hi Vinod,
This is a normal situation and will not be an issue if your server is
dedicated for SQL server alone. SQL Server
will release the memory if operating system requires more physical memory.
To restrict the memory usage you can set the memory to static. Set the "min
server memory and max server memory" to the same value.
See the details in "memory, max server memory option" in books online.
Thanks
Hari
MCDBA
"Vinod" <Vinod@.discussions.microsoft.com> wrote in message
news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> Hi
> When you start SQL Server, SQL Server memory usage may continue to
steadily increase and not decrease, even when activity on the server is low.
Additionally, the Task Manager and Performance Monitor may show that the
physical memory available on the computer is steadily decreasing until the
available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
normal and is an intended behavior of the SQL Server buffer pool.
> Any solution
> Thanks
> Vinod|||Hi Hari Prasad,
Thank you, I will try setting the min and max memory usage
Regards
Vinod
"Hari Prasad" wrote:
> Hi Vinod,
> This is a normal situation and will not be an issue if your server is
> dedicated for SQL server alone. SQL Server
> will release the memory if operating system requires more physical memory.
> To restrict the memory usage you can set the memory to static. Set the "mi
n
> server memory and max server memory" to the same value.
> See the details in "memory, max server memory option" in books online.
> --
> Thanks
> Hari
> MCDBA
> "Vinod" <Vinod@.discussions.microsoft.com> wrote in message
> news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> steadily increase and not decrease, even when activity on the server is lo
w.
> Additionally, the Task Manager and Performance Monitor may show that the
> physical memory available on the computer is steadily decreasing until the
> available memory is between 4 to 10 MB.
> normal and is an intended behavior of the SQL Server buffer pool.
>
>|||If there aren't any performance issues currently on the Server then let the
memory be managed dynamically instead of setting min and max values.
IN general leaving dynamic settings for memory on SQL is preferrable for bet
ter performance. If other application are sharing the server resources then
you may test and set the values.
HTH
--
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Perform
ance topic.
"Vinod" wrote:
[vbcol=seagreen]
> Hi Hari Prasad,
> Thank you, I will try setting the min and max memory usage
> Regards
> Vinod
> "Hari Prasad" wrote:
>
Friday, March 9, 2012
Memory Usage
Hi
When you start SQL Server, SQL Server memory usage may continue to steadily increase and not decrease, even when activity on the server is low. Additionally, the Task Manager and Performance Monitor may show that the physical memory available on the computer is steadily decreasing until the available memory is between 4 to 10 MB.
This behavior alone does not indicate a memory leak. This behavior is normal and is an intended behavior of the SQL Server buffer pool.
Any solution
Thanks
VinodSolution to what ? What you just stated is normal from a SQL server memory
consumption .
"Vinod" <Vinod@.discussions.microsoft.com> wrote in message
news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> Hi
> When you start SQL Server, SQL Server memory usage may continue to
steadily increase and not decrease, even when activity on the server is low.
Additionally, the Task Manager and Performance Monitor may show that the
physical memory available on the computer is steadily decreasing until the
available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
normal and is an intended behavior of the SQL Server buffer pool.
> Any solution
> Thanks
> Vinod|||Hi Vinod,
This is a normal situation and will not be an issue if your server is
dedicated for SQL server alone. SQL Server
will release the memory if operating system requires more physical memory.
To restrict the memory usage you can set the memory to static. Set the "min
server memory and max server memory" to the same value.
See the details in "memory, max server memory option" in books online.
--
Thanks
Hari
MCDBA
"Vinod" <Vinod@.discussions.microsoft.com> wrote in message
news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> Hi
> When you start SQL Server, SQL Server memory usage may continue to
steadily increase and not decrease, even when activity on the server is low.
Additionally, the Task Manager and Performance Monitor may show that the
physical memory available on the computer is steadily decreasing until the
available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
normal and is an intended behavior of the SQL Server buffer pool.
> Any solution
> Thanks
> Vinod|||Hi Hari Prasad,
Thank you, I will try setting the min and max memory usage
Regards
Vinod
"Hari Prasad" wrote:
> Hi Vinod,
> This is a normal situation and will not be an issue if your server is
> dedicated for SQL server alone. SQL Server
> will release the memory if operating system requires more physical memory.
> To restrict the memory usage you can set the memory to static. Set the "min
> server memory and max server memory" to the same value.
> See the details in "memory, max server memory option" in books online.
> --
> Thanks
> Hari
> MCDBA
> "Vinod" <Vinod@.discussions.microsoft.com> wrote in message
> news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> > Hi
> >
> > When you start SQL Server, SQL Server memory usage may continue to
> steadily increase and not decrease, even when activity on the server is low.
> Additionally, the Task Manager and Performance Monitor may show that the
> physical memory available on the computer is steadily decreasing until the
> available memory is between 4 to 10 MB.
> >
> > This behavior alone does not indicate a memory leak. This behavior is
> normal and is an intended behavior of the SQL Server buffer pool.
> >
> > Any solution
> >
> > Thanks
> >
> > Vinod
>
>|||If there aren't any performance issues currently on the Server then let the memory be managed dynamically instead of setting min and max values.
IN general leaving dynamic settings for memory on SQL is preferrable for better performance. If other application are sharing the server resources then you may test and set the values.
HTH
--
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Performance topic.
"Vinod" wrote:
> Hi Hari Prasad,
> Thank you, I will try setting the min and max memory usage
> Regards
> Vinod
> "Hari Prasad" wrote:
> > Hi Vinod,
> >
> > This is a normal situation and will not be an issue if your server is
> > dedicated for SQL server alone. SQL Server
> > will release the memory if operating system requires more physical memory.
> >
> > To restrict the memory usage you can set the memory to static. Set the "min
> > server memory and max server memory" to the same value.
> >
> > See the details in "memory, max server memory option" in books online.
> >
> > --
> > Thanks
> > Hari
> > MCDBA
> >
> > "Vinod" <Vinod@.discussions.microsoft.com> wrote in message
> > news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> > > Hi
> > >
> > > When you start SQL Server, SQL Server memory usage may continue to
> > steadily increase and not decrease, even when activity on the server is low.
> > Additionally, the Task Manager and Performance Monitor may show that the
> > physical memory available on the computer is steadily decreasing until the
> > available memory is between 4 to 10 MB.
> > >
> > > This behavior alone does not indicate a memory leak. This behavior is
> > normal and is an intended behavior of the SQL Server buffer pool.
> > >
> > > Any solution
> > >
> > > Thanks
> > >
> > > Vinod
> >
> >
> >
When you start SQL Server, SQL Server memory usage may continue to steadily increase and not decrease, even when activity on the server is low. Additionally, the Task Manager and Performance Monitor may show that the physical memory available on the computer is steadily decreasing until the available memory is between 4 to 10 MB.
This behavior alone does not indicate a memory leak. This behavior is normal and is an intended behavior of the SQL Server buffer pool.
Any solution
Thanks
VinodSolution to what ? What you just stated is normal from a SQL server memory
consumption .
"Vinod" <Vinod@.discussions.microsoft.com> wrote in message
news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> Hi
> When you start SQL Server, SQL Server memory usage may continue to
steadily increase and not decrease, even when activity on the server is low.
Additionally, the Task Manager and Performance Monitor may show that the
physical memory available on the computer is steadily decreasing until the
available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
normal and is an intended behavior of the SQL Server buffer pool.
> Any solution
> Thanks
> Vinod|||Hi Vinod,
This is a normal situation and will not be an issue if your server is
dedicated for SQL server alone. SQL Server
will release the memory if operating system requires more physical memory.
To restrict the memory usage you can set the memory to static. Set the "min
server memory and max server memory" to the same value.
See the details in "memory, max server memory option" in books online.
--
Thanks
Hari
MCDBA
"Vinod" <Vinod@.discussions.microsoft.com> wrote in message
news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> Hi
> When you start SQL Server, SQL Server memory usage may continue to
steadily increase and not decrease, even when activity on the server is low.
Additionally, the Task Manager and Performance Monitor may show that the
physical memory available on the computer is steadily decreasing until the
available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
normal and is an intended behavior of the SQL Server buffer pool.
> Any solution
> Thanks
> Vinod|||Hi Hari Prasad,
Thank you, I will try setting the min and max memory usage
Regards
Vinod
"Hari Prasad" wrote:
> Hi Vinod,
> This is a normal situation and will not be an issue if your server is
> dedicated for SQL server alone. SQL Server
> will release the memory if operating system requires more physical memory.
> To restrict the memory usage you can set the memory to static. Set the "min
> server memory and max server memory" to the same value.
> See the details in "memory, max server memory option" in books online.
> --
> Thanks
> Hari
> MCDBA
> "Vinod" <Vinod@.discussions.microsoft.com> wrote in message
> news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> > Hi
> >
> > When you start SQL Server, SQL Server memory usage may continue to
> steadily increase and not decrease, even when activity on the server is low.
> Additionally, the Task Manager and Performance Monitor may show that the
> physical memory available on the computer is steadily decreasing until the
> available memory is between 4 to 10 MB.
> >
> > This behavior alone does not indicate a memory leak. This behavior is
> normal and is an intended behavior of the SQL Server buffer pool.
> >
> > Any solution
> >
> > Thanks
> >
> > Vinod
>
>|||If there aren't any performance issues currently on the Server then let the memory be managed dynamically instead of setting min and max values.
IN general leaving dynamic settings for memory on SQL is preferrable for better performance. If other application are sharing the server resources then you may test and set the values.
HTH
--
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Performance topic.
"Vinod" wrote:
> Hi Hari Prasad,
> Thank you, I will try setting the min and max memory usage
> Regards
> Vinod
> "Hari Prasad" wrote:
> > Hi Vinod,
> >
> > This is a normal situation and will not be an issue if your server is
> > dedicated for SQL server alone. SQL Server
> > will release the memory if operating system requires more physical memory.
> >
> > To restrict the memory usage you can set the memory to static. Set the "min
> > server memory and max server memory" to the same value.
> >
> > See the details in "memory, max server memory option" in books online.
> >
> > --
> > Thanks
> > Hari
> > MCDBA
> >
> > "Vinod" <Vinod@.discussions.microsoft.com> wrote in message
> > news:43141E1A-70EB-46E1-BF26-298541492B3A@.microsoft.com...
> > > Hi
> > >
> > > When you start SQL Server, SQL Server memory usage may continue to
> > steadily increase and not decrease, even when activity on the server is low.
> > Additionally, the Task Manager and Performance Monitor may show that the
> > physical memory available on the computer is steadily decreasing until the
> > available memory is between 4 to 10 MB.
> > >
> > > This behavior alone does not indicate a memory leak. This behavior is
> > normal and is an intended behavior of the SQL Server buffer pool.
> > >
> > > Any solution
> > >
> > > Thanks
> > >
> > > Vinod
> >
> >
> >
Subscribe to:
Posts (Atom)