Dynamic Memory Problem

Hello,
I have a SQL install that I only want to use 4098MB of memory. I originally
configured the server to dynamically use between 0 and 4096MB of RAM. This
was working fine. I then decided to experiment with a fixed amount to see
how the server would perform at peak memory usage, so I set the fixed amount
to 4096MB. After testing I switched the memory back to dynamic and the
original settings of 0 minimum and 4096 Maximum. Problem is, this SQL
install ALWAYS uses the full 4096MB now. I have tried restarting the
service, rebooting the server, but whenever the SQL service starts it
immediately eats up 4096MB of RAM.
Any ideas on how to fix this?
btw - server is running SP3a with all the latest critical hotfixes.
Thanks,
JBaileyI figured this out.
I ended up having to disable AWE in SQL, restart the SQL service, and then
reenable AWE
Everything is working normally now.
Wonder why it happened though
"JBailey" <abc@.123.com> wrote in message
news:OX6mN8BlDHA.2272@.tk2msftngp13.phx.gbl...
> Hello,
> I have a SQL install that I only want to use 4098MB of memory. I
originally
> configured the server to dynamically use between 0 and 4096MB of RAM. This
> was working fine. I then decided to experiment with a fixed amount to see
> how the server would perform at peak memory usage, so I set the fixed
amount
> to 4096MB. After testing I switched the memory back to dynamic and the
> original settings of 0 minimum and 4096 Maximum. Problem is, this SQL
> install ALWAYS uses the full 4096MB now. I have tried restarting the
> service, rebooting the server, but whenever the SQL service starts it
> immediately eats up 4096MB of RAM.
> Any ideas on how to fix this?
> btw - server is running SP3a with all the latest critical hotfixes.
> Thanks,
> JBailey
>|||Actually I was wrong. Rebooted the box and I'm still having the same issue.
:(
Any ideas?
"JBailey" <abc@.123.com> wrote in message
news:OX6mN8BlDHA.2272@.tk2msftngp13.phx.gbl...
> Hello,
> I have a SQL install that I only want to use 4098MB of memory. I
originally
> configured the server to dynamically use between 0 and 4096MB of RAM. This
> was working fine. I then decided to experiment with a fixed amount to see
> how the server would perform at peak memory usage, so I set the fixed
amount
> to 4096MB. After testing I switched the memory back to dynamic and the
> original settings of 0 minimum and 4096 Maximum. Problem is, this SQL
> install ALWAYS uses the full 4096MB now. I have tried restarting the
> service, rebooting the server, but whenever the SQL service starts it
> immediately eats up 4096MB of RAM.
> Any ideas on how to fix this?
> btw - server is running SP3a with all the latest critical hotfixes.
> Thanks,
> JBailey
>|||With AWE enabled, SQL server will take as much memory it can get -- if there
is a max, it goes to the max, else it goes to the max the system allows it.
So what you see is the standard behavior.
Quentin
"JBailey" <abc@.123.com> wrote in message
news:Ol40$QClDHA.2488@.TK2MSFTNGP12.phx.gbl...
> Actually I was wrong. Rebooted the box and I'm still having the same
issue.
> :(
> Any ideas?
>
> "JBailey" <abc@.123.com> wrote in message
> news:OX6mN8BlDHA.2272@.tk2msftngp13.phx.gbl...
> > Hello,
> >
> > I have a SQL install that I only want to use 4098MB of memory. I
> originally
> > configured the server to dynamically use between 0 and 4096MB of RAM.
This
> > was working fine. I then decided to experiment with a fixed amount to
see
> > how the server would perform at peak memory usage, so I set the fixed
> amount
> > to 4096MB. After testing I switched the memory back to dynamic and the
> > original settings of 0 minimum and 4096 Maximum. Problem is, this SQL
> > install ALWAYS uses the full 4096MB now. I have tried restarting the
> > service, rebooting the server, but whenever the SQL service starts it
> > immediately eats up 4096MB of RAM.
> >
> > Any ideas on how to fix this?
> >
> > btw - server is running SP3a with all the latest critical hotfixes.
> >
> > Thanks,
> >
> > JBailey
> >
> >
>|||When you use AWE it will fix the memory at what the Max Memory setting is.
That is how AWE works. You can not dynamically allocate memory with AWE set
on.
--
Andrew J. Kelly
SQL Server MVP
"JBailey" <abc@.123.com> wrote in message
news:OX6mN8BlDHA.2272@.tk2msftngp13.phx.gbl...
> Hello,
> I have a SQL install that I only want to use 4098MB of memory. I
originally
> configured the server to dynamically use between 0 and 4096MB of RAM. This
> was working fine. I then decided to experiment with a fixed amount to see
> how the server would perform at peak memory usage, so I set the fixed
amount
> to 4096MB. After testing I switched the memory back to dynamic and the
> original settings of 0 minimum and 4096 Maximum. Problem is, this SQL
> install ALWAYS uses the full 4096MB now. I have tried restarting the
> service, rebooting the server, but whenever the SQL service starts it
> immediately eats up 4096MB of RAM.
> Any ideas on how to fix this?
> btw - server is running SP3a with all the latest critical hotfixes.
> Thanks,
> JBailey
>|||Alright, I understand that, but I have a follow up.
I have three instances of SQL installed on a 2 node cluster.
One instance is set to use AWE and a max memory of 4096. This is the
instance that immediately takes up the 4GB of RAM
Two other instances are set to use AWE, and both are set to use max memory
of 2048. Neither of these instances use up the RAM immediately like the
first instance. Is this because neither of them are set to use more than 4GB
of RAM?
Thanks,
JBailey
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eQFsviClDHA.2244@.TK2MSFTNGP12.phx.gbl...
> When you use AWE it will fix the memory at what the Max Memory setting is.
> That is how AWE works. You can not dynamically allocate memory with AWE
set
> on.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "JBailey" <abc@.123.com> wrote in message
> news:OX6mN8BlDHA.2272@.tk2msftngp13.phx.gbl...
> > Hello,
> >
> > I have a SQL install that I only want to use 4098MB of memory. I
> originally
> > configured the server to dynamically use between 0 and 4096MB of RAM.
This
> > was working fine. I then decided to experiment with a fixed amount to
see
> > how the server would perform at peak memory usage, so I set the fixed
> amount
> > to 4096MB. After testing I switched the memory back to dynamic and the
> > original settings of 0 minimum and 4096 Maximum. Problem is, this SQL
> > install ALWAYS uses the full 4096MB now. I have tried restarting the
> > service, rebooting the server, but whenever the SQL service starts it
> > immediately eats up 4096MB of RAM.
> >
> > Any ideas on how to fix this?
> >
> > btw - server is running SP3a with all the latest critical hotfixes.
> >
> > Thanks,
> >
> > JBailey
> >
> >
>|||Sorry for the late reply. AWE is not used in the other 2 instances since
the memory can only be 2 GB. There are times when SQL Server just ignores
the AWE settings when they don't make sense and can not be used.
--
Andrew J. Kelly
SQL Server MVP
"JBailey" <abc@.123.com> wrote in message
news:%23Fhk%23zKlDHA.2512@.TK2MSFTNGP09.phx.gbl...
> Alright, I understand that, but I have a follow up.
> I have three instances of SQL installed on a 2 node cluster.
> One instance is set to use AWE and a max memory of 4096. This is the
> instance that immediately takes up the 4GB of RAM
> Two other instances are set to use AWE, and both are set to use max memory
> of 2048. Neither of these instances use up the RAM immediately like the
> first instance. Is this because neither of them are set to use more than
4GB
> of RAM?
> Thanks,
> JBailey
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eQFsviClDHA.2244@.TK2MSFTNGP12.phx.gbl...
> > When you use AWE it will fix the memory at what the Max Memory setting
is.
> > That is how AWE works. You can not dynamically allocate memory with AWE
> set
> > on.
> >
> > --
> >
> > Andrew J. Kelly
> > SQL Server MVP
> >
> >
> > "JBailey" <abc@.123.com> wrote in message
> > news:OX6mN8BlDHA.2272@.tk2msftngp13.phx.gbl...
> > > Hello,
> > >
> > > I have a SQL install that I only want to use 4098MB of memory. I
> > originally
> > > configured the server to dynamically use between 0 and 4096MB of RAM.
> This
> > > was working fine. I then decided to experiment with a fixed amount to
> see
> > > how the server would perform at peak memory usage, so I set the fixed
> > amount
> > > to 4096MB. After testing I switched the memory back to dynamic and the
> > > original settings of 0 minimum and 4096 Maximum. Problem is, this SQL
> > > install ALWAYS uses the full 4096MB now. I have tried restarting the
> > > service, rebooting the server, but whenever the SQL service starts it
> > > immediately eats up 4096MB of RAM.
> > >
> > > Any ideas on how to fix this?
> > >
> > > btw - server is running SP3a with all the latest critical hotfixes.
> > >
> > > Thanks,
> > >
> > > JBailey
> > >
> > >
> >
> >
>