Using SS2000. I'm having some timeouts on some queries from a web site and
I'm trying to figure out why they're occurring. We have some dts packages
that run every 30 minutes so there may be a conflict.
We have memory configured dynamically for min - 0 and max 3583MB. However,
when I look at System Monitor for SQL Server:Memory Manager:Total Server
Manager, the memory is always around 1,678,880(KB). It only seems to
fluctuate by a few MB. In looking at the Memory Object:% Committed Bytes in
Use for the system, it is always around 40%. Memory Object:Available MBytes
is about 1086. Between what SS is using and the system memory available,
about 2.5G is accounted for. I don't know where the other 1G has gone to.
I'm also wondering why SS never seems to get any more than 1.6G. Is it
actually using all of the 1.6G or only a part of it? We have a 4 processor
system and even when all 4 processors are around 80% processor time, the
memory doesn't change.
Any ideas or suggestions?
Thanks,
Dan
Did you turn on AWE flag?
Eric Li
SQL DBA
MCDBA
Dan wrote:
> Using SS2000. I'm having some timeouts on some queries from a web site and
> I'm trying to figure out why they're occurring. We have some dts packages
> that run every 30 minutes so there may be a conflict.
> We have memory configured dynamically for min - 0 and max 3583MB. However,
> when I look at System Monitor for SQL Server:Memory Manager:Total Server
> Manager, the memory is always around 1,678,880(KB). It only seems to
> fluctuate by a few MB. In looking at the Memory Object:% Committed Bytes in
> Use for the system, it is always around 40%. Memory Object:Available MBytes
> is about 1086. Between what SS is using and the system memory available,
> about 2.5G is accounted for. I don't know where the other 1G has gone to.
> I'm also wondering why SS never seems to get any more than 1.6G. Is it
> actually using all of the 1.6G or only a part of it? We have a 4 processor
> system and even when all 4 processors are around 80% processor time, the
> memory doesn't change.
> Any ideas or suggestions?
> Thanks,
> Dan
>
>
|||Do you have the Enterprise version of 2000?
-John Oakes
"Dan" <ddonahue@.archermalmo.com> wrote in message
news:OX1gKzKTEHA.3016@.tk2msftngp13.phx.gbl...
> Using SS2000. I'm having some timeouts on some queries from a web site and
> I'm trying to figure out why they're occurring. We have some dts packages
> that run every 30 minutes so there may be a conflict.
> We have memory configured dynamically for min - 0 and max 3583MB. However,
> when I look at System Monitor for SQL Server:Memory Manager:Total Server
> Manager, the memory is always around 1,678,880(KB). It only seems to
> fluctuate by a few MB. In looking at the Memory Object:% Committed Bytes
in
> Use for the system, it is always around 40%. Memory Object:Available
MBytes
> is about 1086. Between what SS is using and the system memory available,
> about 2.5G is accounted for. I don't know where the other 1G has gone to.
> I'm also wondering why SS never seems to get any more than 1.6G. Is it
> actually using all of the 1.6G or only a part of it? We have a 4 processor
> system and even when all 4 processors are around 80% processor time, the
> memory doesn't change.
> Any ideas or suggestions?
> Thanks,
> Dan
>
>
|||You need to set the /3GB switch in the Boot.ini file to get use of up to 3GB
of ram for SQL Server. What you are seeing is the 2Gb minus the memtoleave
area that is reserved up front. Your timeouts are most likely due to
blocking fromt eh DTS packages though. Running sp_who2 will give you a
start as to who is blocking.
Andrew J. Kelly
SQL Server MVP
"Dan" <ddonahue@.archermalmo.com> wrote in message
news:OX1gKzKTEHA.3016@.tk2msftngp13.phx.gbl...
> Using SS2000. I'm having some timeouts on some queries from a web site and
> I'm trying to figure out why they're occurring. We have some dts packages
> that run every 30 minutes so there may be a conflict.
> We have memory configured dynamically for min - 0 and max 3583MB. However,
> when I look at System Monitor for SQL Server:Memory Manager:Total Server
> Manager, the memory is always around 1,678,880(KB). It only seems to
> fluctuate by a few MB. In looking at the Memory Object:% Committed Bytes
in
> Use for the system, it is always around 40%. Memory Object:Available
MBytes
> is about 1086. Between what SS is using and the system memory available,
> about 2.5G is accounted for. I don't know where the other 1G has gone to.
> I'm also wondering why SS never seems to get any more than 1.6G. Is it
> actually using all of the 1.6G or only a part of it? We have a 4 processor
> system and even when all 4 processors are around 80% processor time, the
> memory doesn't change.
> Any ideas or suggestions?
> Thanks,
> Dan
>
>
|||We're running developer.
"John Oakes" <john@.nospam.networkproductions.net> wrote in message
news:Ov2dPRLTEHA.760@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Do you have the Enterprise version of 2000?
> -John Oakes
> "Dan" <ddonahue@.archermalmo.com> wrote in message
> news:OX1gKzKTEHA.3016@.tk2msftngp13.phx.gbl...
and[vbcol=seagreen]
packages[vbcol=seagreen]
However,[vbcol=seagreen]
> in
> MBytes
to.[vbcol=seagreen]
processor
>
|||It's not enabled. Do I need Enterprise version for that? We're running
Developer.
"Eric.Li" <anonymous@.microsoftnews.org> wrote in message
news:%23xaNDJLTEHA.1232@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Did you turn on AWE flag?
> --
> Eric Li
> SQL DBA
> MCDBA
> Dan wrote:
and[vbcol=seagreen]
packages[vbcol=seagreen]
However,[vbcol=seagreen]
in[vbcol=seagreen]
MBytes[vbcol=seagreen]
to.[vbcol=seagreen]
processor[vbcol=seagreen]
|||Will I be able to tell in profiler that blocking is going on? If so, can you
suggest what to look for? Otherwise, I'll have to get lucky and catch it in
current activity.
Thanks,
Dan
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OQZBBSLTEHA.3752@.TK2MSFTNGP12.phx.gbl...
> You need to set the /3GB switch in the Boot.ini file to get use of up to
3GB
> of ram for SQL Server. What you are seeing is the 2Gb minus the
memtoleave[vbcol=seagreen]
> area that is reserved up front. Your timeouts are most likely due to
> blocking fromt eh DTS packages though. Running sp_who2 will give you a
> start as to who is blocking.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Dan" <ddonahue@.archermalmo.com> wrote in message
> news:OX1gKzKTEHA.3016@.tk2msftngp13.phx.gbl...
and[vbcol=seagreen]
packages[vbcol=seagreen]
However,[vbcol=seagreen]
> in
> MBytes
to.[vbcol=seagreen]
processor
>
|||I can't remember if developer lets you use more than 2G, regardless of the
3G switch. Maybe someone here will remember?
-John Oakes
"Dan" <ddonahue@.archermalmo.com> wrote in message
news:%23Aar7nLTEHA.3552@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> We're running developer.
> "John Oakes" <john@.nospam.networkproductions.net> wrote in message
> news:Ov2dPRLTEHA.760@.TK2MSFTNGP12.phx.gbl...
> and
> packages
> However,
Server[vbcol=seagreen]
Bytes[vbcol=seagreen]
available,[vbcol=seagreen]
> to.
> processor
the
>
|||You need Enterprise Edition to access full 4GB RAM
Eric Li
SQL DBA
MCDBA
Dan wrote:
> It's not enabled. Do I need Enterprise version for that? We're running
> Developer.
> "Eric.Li" <anonymous@.microsoftnews.org> wrote in message
> news:%23xaNDJLTEHA.1232@.TK2MSFTNGP09.phx.gbl...
>
> and
>
> packages
>
> However,
>
> in
>
> MBytes
>
> to.
>
> processor
>
>
|||I see that we need to be running Advanced Server or Data Center. We don't have either.
Thanks,
Dan
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment