Hello Everyone,
I am running SQL2K with sp3, continuous merge replication, only one
subscriber.
My current setting for Subscription expiration is the default of 7, I
have just recently changed this from the default of 14 days, as our
Subscriber is basically always available.
I am still trying to figure out how to cleanup my merge metadata. From
what I have read and from what I understand ,
sp_mergemetadataretentioncleanup is automatically run, if the agent
running Merge has the Parameter for MetadataRententionCleanup set to 1
I am under the assumption that if I have has the Parameter for
MetadataRententionCleanup set to 1 it should automatically be cleaning
up my metadata. Even though I have it set to 1 it does not appear
like it is actually cleaning out MSmerge_contents or MSmerge_tombstone.
These tables just keep growing.
Now if I had this parameter set to 0 then I would need to use
sp_mergecleanupmetadata to clean up MSmerge_contents or
MSmerge_tombstone.
Would there ever be a reason for running both?
I did go to BOL but I read the following about using
sp_mergecleanupmetadata:
If you want to run sp_mergecleanupmetadata without the subscriptions
being marked for reinitialization:
Stop all updates to the publication and subscription databases.
Unfortunately, I cannot stop all updates as our servers need to be
available 24/7.
Does anyone run this without stopping replication first? And if you do
run it do you have MetadataRententionCleanup set to 0?
If anyone can help I truly would appreciate it.
Thanks,
Barbara
*** Sent via Developersdex http://www.codecomments.com ***
are you using anonymous subscribers? Merge replication does not clean
up the metadata as efficiently with anonymous subscrptions as opposed
to named subscriptions.
|||Thanks Hilary.
Unfortunately no, we do not have any anonymous subscriptions only one
named subscriptions.
Any other ideas?
Barbara
*** Sent via Developersdex http://www.codecomments.com ***
|||I believe I have my answer:
1) sp_mergecleanupmetadata
2) sp_mergemetadataretentioncleanup
The First should be used for topologies with SQL Server 2000 SP1 or less
(which is not my case)
The Second one is the one to control the process manually for SQL Server
> SP1 which is your case and when the MetadataretentionCleanup is set to
0 (not automatic)
There is also a catch though the second sp is executed automatically by
merge Agent at at startup! when MetadataretentionCleanup is set to 1
therefore when in continuous mode it will be called only once.
So I'll need to manually run sp_mergemetadataretentioncleanup or setup a
job that will do it for me on a scheduled basis.
Thanks for your help Hilary.
Barbara
*** Sent via Developersdex http://www.codecomments.com ***
Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts
Friday, March 30, 2012
Monday, March 26, 2012
Merge Agent retrying forever
We have a Merge Replication with Publisher and Distributor on SQL Server 2000 SP3 and Subscribers running Personal SQL Server 2000 SP2 synchronizing through VPN phone lines.
From time to time one or more subscribers can't reconnect to the Publisher. By inspecting their Merge Agents (through the Replication Monitor) in the Publisher Server we see that they are marked as retrying forever. In the distribution database MSmerge_hi
story table these agents have the "runstatus" column marked with 5 (retry).
We are not able to stop the agents. We have shut down the Publisher server but still the agents show the same status. We have noticed that in order to solve the problem we must synchronize those subscribers through UTP fast cables.
Any help will be appreciated
Righth click on the merge agent and click on Agent Properties. Click on the
Steps tab and double click on a step. On the Edit Step window, click on
the Advanced tab and change the number of retry attempts to a number other
than the default (usually 10 for the run Agent step and 0 for the other
two). I put 2 for all of my steps. You should also change the retry
interval, I put 1 for mine. Click apply and next to set the next step.
Hope this helps.
"Tony2000" <anonymous@.discussions.microsoft.com> wrote in message
news:F71724A8-457A-4B2F-BB8D-B92B0EC3ADD2@.microsoft.com...
> We have a Merge Replication with Publisher and Distributor on SQL Server
2000 SP3 and Subscribers running Personal SQL Server 2000 SP2 synchronizing
through VPN phone lines.
> From time to time one or more subscribers can't reconnect to the
Publisher. By inspecting their Merge Agents (through the Replication
Monitor) in the Publisher Server we see that they are marked as retrying
forever. In the distribution database MSmerge_history table these agents
have the "runstatus" column marked with 5 (retry).
> We are not able to stop the agents. We have shut down the Publisher server
but still the agents show the same status. We have noticed that in order to
solve the problem we must synchronize those subscribers through UTP fast
cables.
> Any help will be appreciated
sql
From time to time one or more subscribers can't reconnect to the Publisher. By inspecting their Merge Agents (through the Replication Monitor) in the Publisher Server we see that they are marked as retrying forever. In the distribution database MSmerge_hi
story table these agents have the "runstatus" column marked with 5 (retry).
We are not able to stop the agents. We have shut down the Publisher server but still the agents show the same status. We have noticed that in order to solve the problem we must synchronize those subscribers through UTP fast cables.
Any help will be appreciated
Righth click on the merge agent and click on Agent Properties. Click on the
Steps tab and double click on a step. On the Edit Step window, click on
the Advanced tab and change the number of retry attempts to a number other
than the default (usually 10 for the run Agent step and 0 for the other
two). I put 2 for all of my steps. You should also change the retry
interval, I put 1 for mine. Click apply and next to set the next step.
Hope this helps.
"Tony2000" <anonymous@.discussions.microsoft.com> wrote in message
news:F71724A8-457A-4B2F-BB8D-B92B0EC3ADD2@.microsoft.com...
> We have a Merge Replication with Publisher and Distributor on SQL Server
2000 SP3 and Subscribers running Personal SQL Server 2000 SP2 synchronizing
through VPN phone lines.
> From time to time one or more subscribers can't reconnect to the
Publisher. By inspecting their Merge Agents (through the Replication
Monitor) in the Publisher Server we see that they are marked as retrying
forever. In the distribution database MSmerge_history table these agents
have the "runstatus" column marked with 5 (retry).
> We are not able to stop the agents. We have shut down the Publisher server
but still the agents show the same status. We have noticed that in order to
solve the problem we must synchronize those subscribers through UTP fast
cables.
> Any help will be appreciated
sql
Wednesday, March 21, 2012
Memory Utilization
Guys,
I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
can use the whole memory for the SQL Server service...
Just as a 2GB server that I had before, monitoring with Task Manager I see
that the memory utilization don't grow up more than 1,84gb... Even with huge
processing and disk reading... So my question is, is there any kind of
special configuration that you must set to let server use the whole memory?
I know about AWE, but I thought AWE is just for servers who break the 4GB
boundary... Would like to know why the memory utilization don't go upper than
1,84gb, even setting this as a fixed value in Server configuration...
Thx,
Rafa
Hi,
What edition of SQL Server you are using? Only Enterprise or Developer
editions of SQL server supports more than 2 GB memory.
Sheck the version of SQL Server using
Select @.@.version
Thanks
Hari
SQL Server MVP
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||According to Books Online
(mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL% 20Server\80\Tools\Books\architec.chm::/8_ar_ts_8dbn.htm)
the Standard Edition of SQL Server will not use more than 2GB of RAM.
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Take a look at the following URL
http://support.microsoft.com/default...b;en-us;274750
There is a \3GB switch
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Hi,
Try /3gb switch in boot.ini
"Rafa?" wrote:
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Well, it's the Enterprise Edition...
What does /3gb in boot.ini?
"Wayne Snyder" wrote:
> Take a look at the following URL
> http://support.microsoft.com/default...b;en-us;274750
> There is a \3GB switch
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Dual-Xeon
> huge
> memory?
> than
>
>
|||Since you are running on Enterprise Edition you could try using /3GB and or
/PAE within boot.ini.
You will then probably want to specify the memory usage within SQL Server
Using AWE Memory on Windows 2000
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
Managing AWE Memory
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Keith,
Why would you use the /PAE and AWE switches if his server only has 4 GB RAM.
Those settings are for servers with more than 4GB.
"Keith Kratochvil" wrote:
> Since you are running on Enterprise Edition you could try using /3GB and or
> /PAE within boot.ini.
> You will then probably want to specify the memory usage within SQL Server
> Using AWE Memory on Windows 2000
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
> Managing AWE Memory
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
> --
> Keith
>
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
>
>
I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
can use the whole memory for the SQL Server service...
Just as a 2GB server that I had before, monitoring with Task Manager I see
that the memory utilization don't grow up more than 1,84gb... Even with huge
processing and disk reading... So my question is, is there any kind of
special configuration that you must set to let server use the whole memory?
I know about AWE, but I thought AWE is just for servers who break the 4GB
boundary... Would like to know why the memory utilization don't go upper than
1,84gb, even setting this as a fixed value in Server configuration...
Thx,
Rafa
Hi,
What edition of SQL Server you are using? Only Enterprise or Developer
editions of SQL server supports more than 2 GB memory.
Sheck the version of SQL Server using
Select @.@.version
Thanks
Hari
SQL Server MVP
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||According to Books Online
(mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL% 20Server\80\Tools\Books\architec.chm::/8_ar_ts_8dbn.htm)
the Standard Edition of SQL Server will not use more than 2GB of RAM.
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Take a look at the following URL
http://support.microsoft.com/default...b;en-us;274750
There is a \3GB switch
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Hi,
Try /3gb switch in boot.ini
"Rafa?" wrote:
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Well, it's the Enterprise Edition...
What does /3gb in boot.ini?
"Wayne Snyder" wrote:
> Take a look at the following URL
> http://support.microsoft.com/default...b;en-us;274750
> There is a \3GB switch
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Dual-Xeon
> huge
> memory?
> than
>
>
|||Since you are running on Enterprise Edition you could try using /3GB and or
/PAE within boot.ini.
You will then probably want to specify the memory usage within SQL Server
Using AWE Memory on Windows 2000
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
Managing AWE Memory
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Keith,
Why would you use the /PAE and AWE switches if his server only has 4 GB RAM.
Those settings are for servers with more than 4GB.
"Keith Kratochvil" wrote:
> Since you are running on Enterprise Edition you could try using /3GB and or
> /PAE within boot.ini.
> You will then probably want to specify the memory usage within SQL Server
> Using AWE Memory on Windows 2000
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
> Managing AWE Memory
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
> --
> Keith
>
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
>
>
Memory Utilization
Guys,
I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
can use the whole memory for the SQL Server service...
Just as a 2GB server that I had before, monitoring with Task Manager I see
that the memory utilization don't grow up more than 1,84gb... Even with huge
processing and disk reading... So my question is, is there any kind of
special configuration that you must set to let server use the whole memory?
I know about AWE, but I thought AWE is just for servers who break the 4GB
boundary... Would like to know why the memory utilization don't go upper tha
n
1,84gb, even setting this as a fixed value in Server configuration...
Thx,
RafaHi,
What edition of SQL Server you are using? Only Enterprise or Developer
editions of SQL server supports more than 2 GB memory.
Sheck the version of SQL Server using
Select @.@.version
Thanks
Hari
SQL Server MVP
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||According to Books Online
(mk:@.MSITStore:C:\Program%20Files\Micros
oft%20SQL%20Server\80\Tools\Books\ar
chitec.chm::/8_ar_ts_8dbn.htm)
the Standard Edition of SQL Server will not use more than 2GB of RAM.
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Take a look at the following URL
http://support.microsoft.com/defaul...kb;en-us;274750
There is a \3GB switch
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Hi,
Try /3gb switch in boot.ini
"Rafa?" wrote:
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a Dual-Xeo
n
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with hu
ge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole memory
?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper t
han
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Well, it's the Enterprise Edition...
What does /3gb in boot.ini?
"Wayne Snyder" wrote:
> Take a look at the following URL
> http://support.microsoft.com/defaul...kb;en-us;274750
> There is a \3GB switch
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Dual-Xeon
> huge
> memory?
> than
>
>|||Since you are running on Enterprise Edition you could try using /3GB and or
/PAE within boot.ini.
You will then probably want to specify the memory usage within SQL Server
Using AWE Memory on Windows 2000
mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\arc
hitec.chm::/8_ar_sa_6b3k.htm
Managing AWE Memory
mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\adm
insql.chm::/ad_1_server_1fnd.htm
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Keith,
Why would you use the /PAE and AWE switches if his server only has 4 GB RAM.
Those settings are for servers with more than 4GB.
"Keith Kratochvil" wrote:
> Since you are running on Enterprise Edition you could try using /3GB and
or
> /PAE within boot.ini.
> You will then probably want to specify the memory usage within SQL Server
> Using AWE Memory on Windows 2000
> mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\a
rchitec.chm::/8_ar_sa_6b3k.htm
> Managing AWE Memory
> mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\a
dminsql.chm::/ad_1_server_1fnd.htm
> --
> Keith
>
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
>
>
I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
can use the whole memory for the SQL Server service...
Just as a 2GB server that I had before, monitoring with Task Manager I see
that the memory utilization don't grow up more than 1,84gb... Even with huge
processing and disk reading... So my question is, is there any kind of
special configuration that you must set to let server use the whole memory?
I know about AWE, but I thought AWE is just for servers who break the 4GB
boundary... Would like to know why the memory utilization don't go upper tha
n
1,84gb, even setting this as a fixed value in Server configuration...
Thx,
RafaHi,
What edition of SQL Server you are using? Only Enterprise or Developer
editions of SQL server supports more than 2 GB memory.
Sheck the version of SQL Server using
Select @.@.version
Thanks
Hari
SQL Server MVP
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||According to Books Online
(mk:@.MSITStore:C:\Program%20Files\Micros
oft%20SQL%20Server\80\Tools\Books\ar
chitec.chm::/8_ar_ts_8dbn.htm)
the Standard Edition of SQL Server will not use more than 2GB of RAM.
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Take a look at the following URL
http://support.microsoft.com/defaul...kb;en-us;274750
There is a \3GB switch
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Hi,
Try /3gb switch in boot.ini
"Rafa?" wrote:
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a Dual-Xeo
n
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with hu
ge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole memory
?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper t
han
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Well, it's the Enterprise Edition...
What does /3gb in boot.ini?
"Wayne Snyder" wrote:
> Take a look at the following URL
> http://support.microsoft.com/defaul...kb;en-us;274750
> There is a \3GB switch
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Dual-Xeon
> huge
> memory?
> than
>
>|||Since you are running on Enterprise Edition you could try using /3GB and or
/PAE within boot.ini.
You will then probably want to specify the memory usage within SQL Server
Using AWE Memory on Windows 2000
mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\arc
hitec.chm::/8_ar_sa_6b3k.htm
Managing AWE Memory
mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\adm
insql.chm::/ad_1_server_1fnd.htm
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Keith,
Why would you use the /PAE and AWE switches if his server only has 4 GB RAM.
Those settings are for servers with more than 4GB.
"Keith Kratochvil" wrote:
> Since you are running on Enterprise Edition you could try using /3GB and
or
> /PAE within boot.ini.
> You will then probably want to specify the memory usage within SQL Server
> Using AWE Memory on Windows 2000
> mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\a
rchitec.chm::/8_ar_sa_6b3k.htm
> Managing AWE Memory
> mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\a
dminsql.chm::/ad_1_server_1fnd.htm
> --
> Keith
>
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
>
>
Memory Utilization
Guys,
I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
can use the whole memory for the SQL Server service...
Just as a 2GB server that I had before, monitoring with Task Manager I see
that the memory utilization don't grow up more than 1,84gb... Even with huge
processing and disk reading... So my question is, is there any kind of
special configuration that you must set to let server use the whole memory?
I know about AWE, but I thought AWE is just for servers who break the 4GB
boundary... Would like to know why the memory utilization don't go upper than
1,84gb, even setting this as a fixed value in Server configuration...
Thx,
RafaHi,
What edition of SQL Server you are using? Only Enterprise or Developer
editions of SQL server supports more than 2 GB memory.
Sheck the version of SQL Server using
Select @.@.version
Thanks
Hari
SQL Server MVP
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Take a look at the following URL
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
There is a \3GB switch
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||According to Books Online
(mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_ts_8dbn.htm)
the Standard Edition of SQL Server will not use more than 2GB of RAM.
--
Keith
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Hi,
Try /3gb switch in boot.ini
"Rafa®" wrote:
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Well, it's the Enterprise Edition...
What does /3gb in boot.ini?
"Wayne Snyder" wrote:
> Take a look at the following URL
> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
> There is a \3GB switch
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> > Guys,
> > I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> > 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> > can use the whole memory for the SQL Server service...
> >
> > Just as a 2GB server that I had before, monitoring with Task Manager I see
> > that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> > processing and disk reading... So my question is, is there any kind of
> > special configuration that you must set to let server use the whole
> memory?
> >
> > I know about AWE, but I thought AWE is just for servers who break the 4GB
> > boundary... Would like to know why the memory utilization don't go upper
> than
> > 1,84gb, even setting this as a fixed value in Server configuration...
> >
> > Thx,
> > Rafa
>
>|||Since you are running on Enterprise Edition you could try using /3GB and or
/PAE within boot.ini.
You will then probably want to specify the memory usage within SQL Server
Using AWE Memory on Windows 2000
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
Managing AWE Memory
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
--
Keith
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Keith,
Why would you use the /PAE and AWE switches if his server only has 4 GB RAM.
Those settings are for servers with more than 4GB.
"Keith Kratochvil" wrote:
> Since you are running on Enterprise Edition you could try using /3GB and or
> /PAE within boot.ini.
> You will then probably want to specify the memory usage within SQL Server
> Using AWE Memory on Windows 2000
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
> Managing AWE Memory
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
> --
> Keith
>
> "Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> > Guys,
> > I have a server running MS-SQL SP3. The server configuration is a
> > Dual-Xeon
> > 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> > can use the whole memory for the SQL Server service...
> >
> > Just as a 2GB server that I had before, monitoring with Task Manager I see
> > that the memory utilization don't grow up more than 1,84gb... Even with
> > huge
> > processing and disk reading... So my question is, is there any kind of
> > special configuration that you must set to let server use the whole
> > memory?
> >
> > I know about AWE, but I thought AWE is just for servers who break the 4GB
> > boundary... Would like to know why the memory utilization don't go upper
> > than
> > 1,84gb, even setting this as a fixed value in Server configuration...
> >
> > Thx,
> > Rafa
>
>
I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
can use the whole memory for the SQL Server service...
Just as a 2GB server that I had before, monitoring with Task Manager I see
that the memory utilization don't grow up more than 1,84gb... Even with huge
processing and disk reading... So my question is, is there any kind of
special configuration that you must set to let server use the whole memory?
I know about AWE, but I thought AWE is just for servers who break the 4GB
boundary... Would like to know why the memory utilization don't go upper than
1,84gb, even setting this as a fixed value in Server configuration...
Thx,
RafaHi,
What edition of SQL Server you are using? Only Enterprise or Developer
editions of SQL server supports more than 2 GB memory.
Sheck the version of SQL Server using
Select @.@.version
Thanks
Hari
SQL Server MVP
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Take a look at the following URL
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
There is a \3GB switch
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||According to Books Online
(mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_ts_8dbn.htm)
the Standard Edition of SQL Server will not use more than 2GB of RAM.
--
Keith
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Hi,
Try /3gb switch in boot.ini
"Rafa®" wrote:
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Well, it's the Enterprise Edition...
What does /3gb in boot.ini?
"Wayne Snyder" wrote:
> Take a look at the following URL
> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
> There is a \3GB switch
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> > Guys,
> > I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> > 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> > can use the whole memory for the SQL Server service...
> >
> > Just as a 2GB server that I had before, monitoring with Task Manager I see
> > that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> > processing and disk reading... So my question is, is there any kind of
> > special configuration that you must set to let server use the whole
> memory?
> >
> > I know about AWE, but I thought AWE is just for servers who break the 4GB
> > boundary... Would like to know why the memory utilization don't go upper
> than
> > 1,84gb, even setting this as a fixed value in Server configuration...
> >
> > Thx,
> > Rafa
>
>|||Since you are running on Enterprise Edition you could try using /3GB and or
/PAE within boot.ini.
You will then probably want to specify the memory usage within SQL Server
Using AWE Memory on Windows 2000
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
Managing AWE Memory
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
--
Keith
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Keith,
Why would you use the /PAE and AWE switches if his server only has 4 GB RAM.
Those settings are for servers with more than 4GB.
"Keith Kratochvil" wrote:
> Since you are running on Enterprise Edition you could try using /3GB and or
> /PAE within boot.ini.
> You will then probably want to specify the memory usage within SQL Server
> Using AWE Memory on Windows 2000
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
> Managing AWE Memory
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
> --
> Keith
>
> "Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> > Guys,
> > I have a server running MS-SQL SP3. The server configuration is a
> > Dual-Xeon
> > 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> > can use the whole memory for the SQL Server service...
> >
> > Just as a 2GB server that I had before, monitoring with Task Manager I see
> > that the memory utilization don't grow up more than 1,84gb... Even with
> > huge
> > processing and disk reading... So my question is, is there any kind of
> > special configuration that you must set to let server use the whole
> > memory?
> >
> > I know about AWE, but I thought AWE is just for servers who break the 4GB
> > boundary... Would like to know why the memory utilization don't go upper
> > than
> > 1,84gb, even setting this as a fixed value in Server configuration...
> >
> > Thx,
> > Rafa
>
>
Monday, March 19, 2012
Memory Usage from sql server.
Hi, I have a server that has sql server2000 sp3 on win2000 server sp4.
On this server every day runs a process that take about 3 minutes to
finish. But once a month it takes about 30 min. or one hour to finish.
At this moment the only thing that help us to fix the problem is to
restart the server, so we have to restart the server almost once a
month.
Today, we were thinking if maybe the memory of the server is not been
freeing so, it is not enought and it has being free when the server is
restarted.
Do somebody know if sql server has some command that can help us to free
the memory or to check if this is busy and avoid to restart the server.
I'll apreciate a lot your help.
Regards,
*** Sent via Developersdex http://www.codecomments.com ***
My guess would be that you have other apps running onthe server and don't
leave enough for them to operate properly. If so try setting your max
memory setting to a few hundred MB less than the max and see if that helps.
YOU should also check for blocking during that time.
Andrew J. Kelly SQL MVP
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uJ$rY9MMGHA.2916@.tk2msftngp13.phx.gbl...
> Hi, I have a server that has sql server2000 sp3 on win2000 server sp4.
> On this server every day runs a process that take about 3 minutes to
> finish. But once a month it takes about 30 min. or one hour to finish.
> At this moment the only thing that help us to fix the problem is to
> restart the server, so we have to restart the server almost once a
> month.
> Today, we were thinking if maybe the memory of the server is not been
> freeing so, it is not enought and it has being free when the server is
> restarted.
> Do somebody know if sql server has some command that can help us to free
> the memory or to check if this is busy and avoid to restart the server.
> I'll apreciate a lot your help.
> Regards,
>
> *** Sent via Developersdex http://www.codecomments.com ***
On this server every day runs a process that take about 3 minutes to
finish. But once a month it takes about 30 min. or one hour to finish.
At this moment the only thing that help us to fix the problem is to
restart the server, so we have to restart the server almost once a
month.
Today, we were thinking if maybe the memory of the server is not been
freeing so, it is not enought and it has being free when the server is
restarted.
Do somebody know if sql server has some command that can help us to free
the memory or to check if this is busy and avoid to restart the server.
I'll apreciate a lot your help.
Regards,
*** Sent via Developersdex http://www.codecomments.com ***
My guess would be that you have other apps running onthe server and don't
leave enough for them to operate properly. If so try setting your max
memory setting to a few hundred MB less than the max and see if that helps.
YOU should also check for blocking during that time.
Andrew J. Kelly SQL MVP
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uJ$rY9MMGHA.2916@.tk2msftngp13.phx.gbl...
> Hi, I have a server that has sql server2000 sp3 on win2000 server sp4.
> On this server every day runs a process that take about 3 minutes to
> finish. But once a month it takes about 30 min. or one hour to finish.
> At this moment the only thing that help us to fix the problem is to
> restart the server, so we have to restart the server almost once a
> month.
> Today, we were thinking if maybe the memory of the server is not been
> freeing so, it is not enought and it has being free when the server is
> restarted.
> Do somebody know if sql server has some command that can help us to free
> the memory or to check if this is busy and avoid to restart the server.
> I'll apreciate a lot your help.
> Regards,
>
> *** Sent via Developersdex http://www.codecomments.com ***
Memory Usage from sql server.
Hi, I have a server that has sql server2000 sp3 on win2000 server sp4.
On this server every day runs a process that take about 3 minutes to
finish. But once a month it takes about 30 min. or one hour to finish.
At this moment the only thing that help us to fix the problem is to
restart the server, so we have to restart the server almost once a
month.
Today, we were thinking if maybe the memory of the server is not been
freeing so, it is not enought and it has being free when the server is
restarted.
Do somebody know if sql server has some command that can help us to free
the memory or to check if this is busy and avoid to restart the server.
I'll apreciate a lot your help.
Regards,
*** Sent via Developersdex http://www.codecomments.com ***My guess would be that you have other apps running onthe server and don't
leave enough for them to operate properly. If so try setting your max
memory setting to a few hundred MB less than the max and see if that helps.
YOU should also check for blocking during that time.
Andrew J. Kelly SQL MVP
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uJ$rY9MMGHA.2916@.tk2msftngp13.phx.gbl...
> Hi, I have a server that has sql server2000 sp3 on win2000 server sp4.
> On this server every day runs a process that take about 3 minutes to
> finish. But once a month it takes about 30 min. or one hour to finish.
> At this moment the only thing that help us to fix the problem is to
> restart the server, so we have to restart the server almost once a
> month.
> Today, we were thinking if maybe the memory of the server is not been
> freeing so, it is not enought and it has being free when the server is
> restarted.
> Do somebody know if sql server has some command that can help us to free
> the memory or to check if this is busy and avoid to restart the server.
> I'll apreciate a lot your help.
> Regards,
>
> *** Sent via Developersdex http://www.codecomments.com ***
On this server every day runs a process that take about 3 minutes to
finish. But once a month it takes about 30 min. or one hour to finish.
At this moment the only thing that help us to fix the problem is to
restart the server, so we have to restart the server almost once a
month.
Today, we were thinking if maybe the memory of the server is not been
freeing so, it is not enought and it has being free when the server is
restarted.
Do somebody know if sql server has some command that can help us to free
the memory or to check if this is busy and avoid to restart the server.
I'll apreciate a lot your help.
Regards,
*** Sent via Developersdex http://www.codecomments.com ***My guess would be that you have other apps running onthe server and don't
leave enough for them to operate properly. If so try setting your max
memory setting to a few hundred MB less than the max and see if that helps.
YOU should also check for blocking during that time.
Andrew J. Kelly SQL MVP
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uJ$rY9MMGHA.2916@.tk2msftngp13.phx.gbl...
> Hi, I have a server that has sql server2000 sp3 on win2000 server sp4.
> On this server every day runs a process that take about 3 minutes to
> finish. But once a month it takes about 30 min. or one hour to finish.
> At this moment the only thing that help us to fix the problem is to
> restart the server, so we have to restart the server almost once a
> month.
> Today, we were thinking if maybe the memory of the server is not been
> freeing so, it is not enought and it has being free when the server is
> restarted.
> Do somebody know if sql server has some command that can help us to free
> the memory or to check if this is busy and avoid to restart the server.
> I'll apreciate a lot your help.
> Regards,
>
> *** Sent via Developersdex http://www.codecomments.com ***
Memory Usage from sql server.
Hi, I have a server that has sql server2000 sp3 on win2000 server sp4.
On this server every day runs a process that take about 3 minutes to
finish. But once a month it takes about 30 min. or one hour to finish.
At this moment the only thing that help us to fix the problem is to
restart the server, so we have to restart the server almost once a
month.
Today, we were thinking if maybe the memory of the server is not been
freeing so, it is not enought and it has being free when the server is
restarted.
Do somebody know if sql server has some command that can help us to free
the memory or to check if this is busy and avoid to restart the server.
I'll apreciate a lot your help.
Regards,
*** Sent via Developersdex http://www.developersdex.com ***My guess would be that you have other apps running onthe server and don't
leave enough for them to operate properly. If so try setting your max
memory setting to a few hundred MB less than the max and see if that helps.
YOU should also check for blocking during that time.
--
Andrew J. Kelly SQL MVP
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uJ$rY9MMGHA.2916@.tk2msftngp13.phx.gbl...
> Hi, I have a server that has sql server2000 sp3 on win2000 server sp4.
> On this server every day runs a process that take about 3 minutes to
> finish. But once a month it takes about 30 min. or one hour to finish.
> At this moment the only thing that help us to fix the problem is to
> restart the server, so we have to restart the server almost once a
> month.
> Today, we were thinking if maybe the memory of the server is not been
> freeing so, it is not enought and it has being free when the server is
> restarted.
> Do somebody know if sql server has some command that can help us to free
> the memory or to check if this is busy and avoid to restart the server.
> I'll apreciate a lot your help.
> Regards,
>
> *** Sent via Developersdex http://www.developersdex.com ***
On this server every day runs a process that take about 3 minutes to
finish. But once a month it takes about 30 min. or one hour to finish.
At this moment the only thing that help us to fix the problem is to
restart the server, so we have to restart the server almost once a
month.
Today, we were thinking if maybe the memory of the server is not been
freeing so, it is not enought and it has being free when the server is
restarted.
Do somebody know if sql server has some command that can help us to free
the memory or to check if this is busy and avoid to restart the server.
I'll apreciate a lot your help.
Regards,
*** Sent via Developersdex http://www.developersdex.com ***My guess would be that you have other apps running onthe server and don't
leave enough for them to operate properly. If so try setting your max
memory setting to a few hundred MB less than the max and see if that helps.
YOU should also check for blocking during that time.
--
Andrew J. Kelly SQL MVP
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uJ$rY9MMGHA.2916@.tk2msftngp13.phx.gbl...
> Hi, I have a server that has sql server2000 sp3 on win2000 server sp4.
> On this server every day runs a process that take about 3 minutes to
> finish. But once a month it takes about 30 min. or one hour to finish.
> At this moment the only thing that help us to fix the problem is to
> restart the server, so we have to restart the server almost once a
> month.
> Today, we were thinking if maybe the memory of the server is not been
> freeing so, it is not enought and it has being free when the server is
> restarted.
> Do somebody know if sql server has some command that can help us to free
> the memory or to check if this is busy and avoid to restart the server.
> I'll apreciate a lot your help.
> Regards,
>
> *** Sent via Developersdex http://www.developersdex.com ***
Monday, March 12, 2012
Memory usage
Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, 3.7
GB RAM. Cluster Service is running but currently there is no failover
server. Currently the Perfmon counters Target Server Memeory and Total
Server Memory are about 1682534 KB with only slight flucuations. AWE is not
enabled nor is the /3GB switch. The server's memory setting is 'Dynamically
configure SQL Server memory'. Since this is a fairly active db I expect the
memory usage to be closer to 2 GB.
Why is it not maxing out memory up to 2 GB?
I eventually want to enable memory greater than 2 GB. I believe all I need
to do is enable AWE using sp_configure and restart the instance. Do I need
the /3GB switch also? Should I set the max memory setting or leave it
dynamic? If I set the max memory setting what should I set it to?
Buffer Cache Hit Ratio - 98%+
Average Page Life 20 - 1000 secs.
CPU - 20% - 50 %
It has been a while since I have worked on a server that has had memory =
config set to 2GB, but if I remember correctly the servers that I worked =
on that were limited to 2GB of usage showed less (somewhere between 1.6 =
and 1.8GB). I think what you are seeing is normal.
You will want to add /3GB to the boot.ini. Yes, you would need to use =
sp_configure to enable AWE. You will also want to set min and max =
server memory (MB). Try setting min/max server memory to 3GB. =20
To be honest, I don't know that you will see a large performance =
increase in going from 2GB to 3GB of RAM on a server with an 80GB =
database. Then again, it depends on how the database is used.
--=20
Keith
"Dean" <deann@.dtn.com> wrote in message =
news:eDKK2CGNEHA.640@.TK2MSFTNGP12.phx.gbl...
> Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, =
3.7
> GB RAM. Cluster Service is running but currently there is no failover
> server. Currently the Perfmon counters Target Server Memeory and Total
> Server Memory are about 1682534 KB with only slight flucuations. AWE =
is not
> enabled nor is the /3GB switch. The server's memory setting is =
'Dynamically
> configure SQL Server memory'. Since this is a fairly active db I =
expect the
> memory usage to be closer to 2 GB.
>=20
> Why is it not maxing out memory up to 2 GB?
>=20
> I eventually want to enable memory greater than 2 GB. I believe all I =
need
> to do is enable AWE using sp_configure and restart the instance. Do I =
need
> the /3GB switch also? Should I set the max memory setting or leave it
> dynamic? If I set the max memory setting what should I set it to?
>=20
> Buffer Cache Hit Ratio - 98%+
> Average Page Life 20 - 1000 secs.
> CPU - 20% - 50 %
>=20
>
GB RAM. Cluster Service is running but currently there is no failover
server. Currently the Perfmon counters Target Server Memeory and Total
Server Memory are about 1682534 KB with only slight flucuations. AWE is not
enabled nor is the /3GB switch. The server's memory setting is 'Dynamically
configure SQL Server memory'. Since this is a fairly active db I expect the
memory usage to be closer to 2 GB.
Why is it not maxing out memory up to 2 GB?
I eventually want to enable memory greater than 2 GB. I believe all I need
to do is enable AWE using sp_configure and restart the instance. Do I need
the /3GB switch also? Should I set the max memory setting or leave it
dynamic? If I set the max memory setting what should I set it to?
Buffer Cache Hit Ratio - 98%+
Average Page Life 20 - 1000 secs.
CPU - 20% - 50 %
It has been a while since I have worked on a server that has had memory =
config set to 2GB, but if I remember correctly the servers that I worked =
on that were limited to 2GB of usage showed less (somewhere between 1.6 =
and 1.8GB). I think what you are seeing is normal.
You will want to add /3GB to the boot.ini. Yes, you would need to use =
sp_configure to enable AWE. You will also want to set min and max =
server memory (MB). Try setting min/max server memory to 3GB. =20
To be honest, I don't know that you will see a large performance =
increase in going from 2GB to 3GB of RAM on a server with an 80GB =
database. Then again, it depends on how the database is used.
--=20
Keith
"Dean" <deann@.dtn.com> wrote in message =
news:eDKK2CGNEHA.640@.TK2MSFTNGP12.phx.gbl...
> Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, =
3.7
> GB RAM. Cluster Service is running but currently there is no failover
> server. Currently the Perfmon counters Target Server Memeory and Total
> Server Memory are about 1682534 KB with only slight flucuations. AWE =
is not
> enabled nor is the /3GB switch. The server's memory setting is =
'Dynamically
> configure SQL Server memory'. Since this is a fairly active db I =
expect the
> memory usage to be closer to 2 GB.
>=20
> Why is it not maxing out memory up to 2 GB?
>=20
> I eventually want to enable memory greater than 2 GB. I believe all I =
need
> to do is enable AWE using sp_configure and restart the instance. Do I =
need
> the /3GB switch also? Should I set the max memory setting or leave it
> dynamic? If I set the max memory setting what should I set it to?
>=20
> Buffer Cache Hit Ratio - 98%+
> Average Page Life 20 - 1000 secs.
> CPU - 20% - 50 %
>=20
>
Memory usage
Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, 3.7
GB RAM. Cluster Service is running but currently there is no failover
server. Currently the Perfmon counters Target Server Memeory and Total
Server Memory are about 1682534 KB with only slight flucuations. AWE is not
enabled nor is the /3GB switch. The server's memory setting is 'Dynamically
configure SQL Server memory'. Since this is a fairly active db I expect the
memory usage to be closer to 2 GB.
Why is it not maxing out memory up to 2 GB?
I eventually want to enable memory greater than 2 GB. I believe all I need
to do is enable AWE using sp_configure and restart the instance. Do I need
the /3GB switch also? Should I set the max memory setting or leave it
dynamic? If I set the max memory setting what should I set it to?
Buffer Cache Hit Ratio - 98%+
Average Page Life 20 - 1000 secs.
CPU - 20% - 50 %It has been a while since I have worked on a server that has had memory =
config set to 2GB, but if I remember correctly the servers that I worked =
on that were limited to 2GB of usage showed less (somewhere between 1.6 =
and 1.8GB). I think what you are seeing is normal.
You will want to add /3GB to the boot.ini. Yes, you would need to use =
sp_configure to enable AWE. You will also want to set min and max =
server memory (MB). Try setting min/max server memory to 3GB. =20
To be honest, I don't know that you will see a large performance =
increase in going from 2GB to 3GB of RAM on a server with an 80GB =
database. Then again, it depends on how the database is used.
--=20
Keith
"Dean" <deann@.dtn.com> wrote in message =
news:eDKK2CGNEHA.640@.TK2MSFTNGP12.phx.gbl...
> Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, =
3.7
> GB RAM. Cluster Service is running but currently there is no failover
> server. Currently the Perfmon counters Target Server Memeory and Total
> Server Memory are about 1682534 KB with only slight flucuations. AWE =
is not
> enabled nor is the /3GB switch. The server's memory setting is =
'Dynamically
> configure SQL Server memory'. Since this is a fairly active db I =
expect the
> memory usage to be closer to 2 GB.
>=20
> Why is it not maxing out memory up to 2 GB?
>=20
> I eventually want to enable memory greater than 2 GB. I believe all I =
need
> to do is enable AWE using sp_configure and restart the instance. Do I =
need
> the /3GB switch also? Should I set the max memory setting or leave it
> dynamic? If I set the max memory setting what should I set it to?
>=20
> Buffer Cache Hit Ratio - 98%+
> Average Page Life 20 - 1000 secs.
> CPU - 20% - 50 %
>=20
>
GB RAM. Cluster Service is running but currently there is no failover
server. Currently the Perfmon counters Target Server Memeory and Total
Server Memory are about 1682534 KB with only slight flucuations. AWE is not
enabled nor is the /3GB switch. The server's memory setting is 'Dynamically
configure SQL Server memory'. Since this is a fairly active db I expect the
memory usage to be closer to 2 GB.
Why is it not maxing out memory up to 2 GB?
I eventually want to enable memory greater than 2 GB. I believe all I need
to do is enable AWE using sp_configure and restart the instance. Do I need
the /3GB switch also? Should I set the max memory setting or leave it
dynamic? If I set the max memory setting what should I set it to?
Buffer Cache Hit Ratio - 98%+
Average Page Life 20 - 1000 secs.
CPU - 20% - 50 %It has been a while since I have worked on a server that has had memory =
config set to 2GB, but if I remember correctly the servers that I worked =
on that were limited to 2GB of usage showed less (somewhere between 1.6 =
and 1.8GB). I think what you are seeing is normal.
You will want to add /3GB to the boot.ini. Yes, you would need to use =
sp_configure to enable AWE. You will also want to set min and max =
server memory (MB). Try setting min/max server memory to 3GB. =20
To be honest, I don't know that you will see a large performance =
increase in going from 2GB to 3GB of RAM on a server with an 80GB =
database. Then again, it depends on how the database is used.
--=20
Keith
"Dean" <deann@.dtn.com> wrote in message =
news:eDKK2CGNEHA.640@.TK2MSFTNGP12.phx.gbl...
> Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, =
3.7
> GB RAM. Cluster Service is running but currently there is no failover
> server. Currently the Perfmon counters Target Server Memeory and Total
> Server Memory are about 1682534 KB with only slight flucuations. AWE =
is not
> enabled nor is the /3GB switch. The server's memory setting is =
'Dynamically
> configure SQL Server memory'. Since this is a fairly active db I =
expect the
> memory usage to be closer to 2 GB.
>=20
> Why is it not maxing out memory up to 2 GB?
>=20
> I eventually want to enable memory greater than 2 GB. I believe all I =
need
> to do is enable AWE using sp_configure and restart the instance. Do I =
need
> the /3GB switch also? Should I set the max memory setting or leave it
> dynamic? If I set the max memory setting what should I set it to?
>=20
> Buffer Cache Hit Ratio - 98%+
> Average Page Life 20 - 1000 secs.
> CPU - 20% - 50 %
>=20
>
Friday, March 9, 2012
Memory usage
Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, 3.7
GB RAM. Cluster Service is running but currently there is no failover
server. Currently the Perfmon counters Target Server Memeory and Total
Server Memory are about 1682534 KB with only slight flucuations. AWE is not
enabled nor is the /3GB switch. The server's memory setting is 'Dynamically
configure SQL Server memory'. Since this is a fairly active db I expect the
memory usage to be closer to 2 GB.
Why is it not maxing out memory up to 2 GB?
I eventually want to enable memory greater than 2 GB. I believe all I need
to do is enable AWE using sp_configure and restart the instance. Do I need
the /3GB switch also? Should I set the max memory setting or leave it
dynamic? If I set the max memory setting what should I set it to?
Buffer Cache Hit Ratio - 98%+
Average Page Life 20 - 1000 secs.
CPU - 20% - 50 %It has been a while since I have worked on a server that has had memory =config set to 2GB, but if I remember correctly the servers that I worked =on that were limited to 2GB of usage showed less (somewhere between 1.6 =and 1.8GB). I think what you are seeing is normal.
You will want to add /3GB to the boot.ini. Yes, you would need to use =sp_configure to enable AWE. You will also want to set min and max =server memory (MB). Try setting min/max server memory to 3GB.
To be honest, I don't know that you will see a large performance =increase in going from 2GB to 3GB of RAM on a server with an 80GB =database. Then again, it depends on how the database is used.
-- Keith
"Dean" <deann@.dtn.com> wrote in message =news:eDKK2CGNEHA.640@.TK2MSFTNGP12.phx.gbl...
> Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, =3.7
> GB RAM. Cluster Service is running but currently there is no failover
> server. Currently the Perfmon counters Target Server Memeory and Total
> Server Memory are about 1682534 KB with only slight flucuations. AWE =is not
> enabled nor is the /3GB switch. The server's memory setting is ='Dynamically
> configure SQL Server memory'. Since this is a fairly active db I =expect the
> memory usage to be closer to 2 GB.
> > Why is it not maxing out memory up to 2 GB?
> > I eventually want to enable memory greater than 2 GB. I believe all I =need
> to do is enable AWE using sp_configure and restart the instance. Do I =need
> the /3GB switch also? Should I set the max memory setting or leave it
> dynamic? If I set the max memory setting what should I set it to?
> > Buffer Cache Hit Ratio - 98%+
> Average Page Life 20 - 1000 secs.
> CPU - 20% - 50 %
> >
GB RAM. Cluster Service is running but currently there is no failover
server. Currently the Perfmon counters Target Server Memeory and Total
Server Memory are about 1682534 KB with only slight flucuations. AWE is not
enabled nor is the /3GB switch. The server's memory setting is 'Dynamically
configure SQL Server memory'. Since this is a fairly active db I expect the
memory usage to be closer to 2 GB.
Why is it not maxing out memory up to 2 GB?
I eventually want to enable memory greater than 2 GB. I believe all I need
to do is enable AWE using sp_configure and restart the instance. Do I need
the /3GB switch also? Should I set the max memory setting or leave it
dynamic? If I set the max memory setting what should I set it to?
Buffer Cache Hit Ratio - 98%+
Average Page Life 20 - 1000 secs.
CPU - 20% - 50 %It has been a while since I have worked on a server that has had memory =config set to 2GB, but if I remember correctly the servers that I worked =on that were limited to 2GB of usage showed less (somewhere between 1.6 =and 1.8GB). I think what you are seeing is normal.
You will want to add /3GB to the boot.ini. Yes, you would need to use =sp_configure to enable AWE. You will also want to set min and max =server memory (MB). Try setting min/max server memory to 3GB.
To be honest, I don't know that you will see a large performance =increase in going from 2GB to 3GB of RAM on a server with an 80GB =database. Then again, it depends on how the database is used.
-- Keith
"Dean" <deann@.dtn.com> wrote in message =news:eDKK2CGNEHA.640@.TK2MSFTNGP12.phx.gbl...
> Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, =3.7
> GB RAM. Cluster Service is running but currently there is no failover
> server. Currently the Perfmon counters Target Server Memeory and Total
> Server Memory are about 1682534 KB with only slight flucuations. AWE =is not
> enabled nor is the /3GB switch. The server's memory setting is ='Dynamically
> configure SQL Server memory'. Since this is a fairly active db I =expect the
> memory usage to be closer to 2 GB.
> > Why is it not maxing out memory up to 2 GB?
> > I eventually want to enable memory greater than 2 GB. I believe all I =need
> to do is enable AWE using sp_configure and restart the instance. Do I =need
> the /3GB switch also? Should I set the max memory setting or leave it
> dynamic? If I set the max memory setting what should I set it to?
> > Buffer Cache Hit Ratio - 98%+
> Average Page Life 20 - 1000 secs.
> CPU - 20% - 50 %
> >
Memory settings for Virtual SQL Server
Hi all,
I am planning to put one instance of SQL Server 2000 sp3 on a two node
Windows 2003 EE MSCS. Each node has two channels, with each channel running
RAID 1. The page file is in one channel, and the OS in the other. Each node
has 4GB of RAM, and PAE enabled. The pagefiles are locked at 8GB on each
server. MDB's and LOG's will run on separate LUN's in the shared storage
array, with MDB's configured as RAID 1/0 and LOGs as RAID 1. Both nodes will
be dedicated to SQL Server.
1. Should I enable AWE in this situation?
2. Should I use the /3GB switch?
3. Would you put the SQL bits in the OS RAID group or the pagefile RAID
group?
4. What settings for sp_configure 'min server memory'?
5. For sp_configure 'max server memory'?
6. Settings for Sp_configure 'max worker thread'?
7. Use WindowsNT fibers?
8. Settings for set working set size? 0?
Thanks for any advice.
John
1. No. And you can remove the /PAE switch from boot.ini. Unless you have
MORE than 4GB of RAM , you don't need it.
2. No. You will need to have flexible memory incase the two instances land
on the same host during a failover event.
3. Forget the pagefile RAID group. Put the pagefile on the OS partition.
A properly tuned SQL server should not page. Put SQL Data and Logs on
different RAID groups. If you only have two RAID groups, put Data on its
own group and Logs on with the OS bits.
4. No change.
5. No change. With 4GB of RAM , it is best to allow SQL to determine its
own memory usage. If you end up with two instances on the same node, they
will come to a balance. You can lock those numbers into the settings, but
be aware that changes in load man affect memory demand between the two
instances.
6. Unless PSS tells you, don't change it.
7. No. Very No.
8. Again, go with the default.
Geoff N. Hiten
Microsoft SQL Server MVP
"JT" <Jthayer@.online.nospam> wrote in message
news:371EAB65-6324-4ABC-A798-E0A114B528B2@.microsoft.com...
> Hi all,
> I am planning to put one instance of SQL Server 2000 sp3 on a two node
> Windows 2003 EE MSCS. Each node has two channels, with each channel
> running
> RAID 1. The page file is in one channel, and the OS in the other. Each
> node
> has 4GB of RAM, and PAE enabled. The pagefiles are locked at 8GB on each
> server. MDB's and LOG's will run on separate LUN's in the shared storage
> array, with MDB's configured as RAID 1/0 and LOGs as RAID 1. Both nodes
> will
> be dedicated to SQL Server.
> 1. Should I enable AWE in this situation?
> 2. Should I use the /3GB switch?
> 3. Would you put the SQL bits in the OS RAID group or the pagefile RAID
> group?
> 4. What settings for sp_configure 'min server memory'?
> 5. For sp_configure 'max server memory'?
> 6. Settings for Sp_configure 'max worker thread'?
> 7. Use WindowsNT fibers?
> 8. Settings for set working set size? 0?
> Thanks for any advice.
> --
> John
|||Thank you Geoff.
John
"Geoff N. Hiten" wrote:
> 1. No. And you can remove the /PAE switch from boot.ini. Unless you have
> MORE than 4GB of RAM , you don't need it.
> 2. No. You will need to have flexible memory incase the two instances land
> on the same host during a failover event.
> 3. Forget the pagefile RAID group. Put the pagefile on the OS partition.
> A properly tuned SQL server should not page. Put SQL Data and Logs on
> different RAID groups. If you only have two RAID groups, put Data on its
> own group and Logs on with the OS bits.
> 4. No change.
> 5. No change. With 4GB of RAM , it is best to allow SQL to determine its
> own memory usage. If you end up with two instances on the same node, they
> will come to a balance. You can lock those numbers into the settings, but
> be aware that changes in load man affect memory demand between the two
> instances.
> 6. Unless PSS tells you, don't change it.
> 7. No. Very No.
> 8. Again, go with the default.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "JT" <Jthayer@.online.nospam> wrote in message
> news:371EAB65-6324-4ABC-A798-E0A114B528B2@.microsoft.com...
>
>
|||Hi again Geoff. As I think about your answer, I think you may have
misunderstood my situation. I am not putting on two instances of SQL Server.
I am putting on one instance onto a virtual server running in active/passive
mode. In this situation, I would expect to not need spare ram to absorb the
second instance, as there will not be one. Would your answers change,
especially the /3GB, AWE and server memory options?
Thanks for your additional consideration of this question.
John
"Geoff N. Hiten" wrote:
> 1. No. And you can remove the /PAE switch from boot.ini. Unless you have
> MORE than 4GB of RAM , you don't need it.
> 2. No. You will need to have flexible memory incase the two instances land
> on the same host during a failover event.
> 3. Forget the pagefile RAID group. Put the pagefile on the OS partition.
> A properly tuned SQL server should not page. Put SQL Data and Logs on
> different RAID groups. If you only have two RAID groups, put Data on its
> own group and Logs on with the OS bits.
> 4. No change.
> 5. No change. With 4GB of RAM , it is best to allow SQL to determine its
> own memory usage. If you end up with two instances on the same node, they
> will come to a balance. You can lock those numbers into the settings, but
> be aware that changes in load man affect memory demand between the two
> instances.
> 6. Unless PSS tells you, don't change it.
> 7. No. Very No.
> 8. Again, go with the default.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "JT" <Jthayer@.online.nospam> wrote in message
> news:371EAB65-6324-4ABC-A798-E0A114B528B2@.microsoft.com...
>
>
|||Active/Passive is not the current nor the correct nomenclature. What you
are talking about is a Single-Instance cluster. With 4GB of RAM in each
host node, I would use the /3GB switch but not AWE or PAE. This KB article
may help (or it may confuse you beyond hope).
How to configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/default...b;en-us;274750
Geoff N. Hiten
Microsoft SQL Server MVP
"JT" <Jthayer@.online.nospam> wrote in message
news:4757AAF6-2A34-4961-8BD0-83580457F6EB@.microsoft.com...[vbcol=seagreen]
> Hi again Geoff. As I think about your answer, I think you may have
> misunderstood my situation. I am not putting on two instances of SQL
> Server.
> I am putting on one instance onto a virtual server running in
> active/passive
> mode. In this situation, I would expect to not need spare ram to absorb
> the
> second instance, as there will not be one. Would your answers change,
> especially the /3GB, AWE and server memory options?
> Thanks for your additional consideration of this question.
> --
> John
>
> "Geoff N. Hiten" wrote:
I am planning to put one instance of SQL Server 2000 sp3 on a two node
Windows 2003 EE MSCS. Each node has two channels, with each channel running
RAID 1. The page file is in one channel, and the OS in the other. Each node
has 4GB of RAM, and PAE enabled. The pagefiles are locked at 8GB on each
server. MDB's and LOG's will run on separate LUN's in the shared storage
array, with MDB's configured as RAID 1/0 and LOGs as RAID 1. Both nodes will
be dedicated to SQL Server.
1. Should I enable AWE in this situation?
2. Should I use the /3GB switch?
3. Would you put the SQL bits in the OS RAID group or the pagefile RAID
group?
4. What settings for sp_configure 'min server memory'?
5. For sp_configure 'max server memory'?
6. Settings for Sp_configure 'max worker thread'?
7. Use WindowsNT fibers?
8. Settings for set working set size? 0?
Thanks for any advice.
John
1. No. And you can remove the /PAE switch from boot.ini. Unless you have
MORE than 4GB of RAM , you don't need it.
2. No. You will need to have flexible memory incase the two instances land
on the same host during a failover event.
3. Forget the pagefile RAID group. Put the pagefile on the OS partition.
A properly tuned SQL server should not page. Put SQL Data and Logs on
different RAID groups. If you only have two RAID groups, put Data on its
own group and Logs on with the OS bits.
4. No change.
5. No change. With 4GB of RAM , it is best to allow SQL to determine its
own memory usage. If you end up with two instances on the same node, they
will come to a balance. You can lock those numbers into the settings, but
be aware that changes in load man affect memory demand between the two
instances.
6. Unless PSS tells you, don't change it.
7. No. Very No.
8. Again, go with the default.
Geoff N. Hiten
Microsoft SQL Server MVP
"JT" <Jthayer@.online.nospam> wrote in message
news:371EAB65-6324-4ABC-A798-E0A114B528B2@.microsoft.com...
> Hi all,
> I am planning to put one instance of SQL Server 2000 sp3 on a two node
> Windows 2003 EE MSCS. Each node has two channels, with each channel
> running
> RAID 1. The page file is in one channel, and the OS in the other. Each
> node
> has 4GB of RAM, and PAE enabled. The pagefiles are locked at 8GB on each
> server. MDB's and LOG's will run on separate LUN's in the shared storage
> array, with MDB's configured as RAID 1/0 and LOGs as RAID 1. Both nodes
> will
> be dedicated to SQL Server.
> 1. Should I enable AWE in this situation?
> 2. Should I use the /3GB switch?
> 3. Would you put the SQL bits in the OS RAID group or the pagefile RAID
> group?
> 4. What settings for sp_configure 'min server memory'?
> 5. For sp_configure 'max server memory'?
> 6. Settings for Sp_configure 'max worker thread'?
> 7. Use WindowsNT fibers?
> 8. Settings for set working set size? 0?
> Thanks for any advice.
> --
> John
|||Thank you Geoff.
John
"Geoff N. Hiten" wrote:
> 1. No. And you can remove the /PAE switch from boot.ini. Unless you have
> MORE than 4GB of RAM , you don't need it.
> 2. No. You will need to have flexible memory incase the two instances land
> on the same host during a failover event.
> 3. Forget the pagefile RAID group. Put the pagefile on the OS partition.
> A properly tuned SQL server should not page. Put SQL Data and Logs on
> different RAID groups. If you only have two RAID groups, put Data on its
> own group and Logs on with the OS bits.
> 4. No change.
> 5. No change. With 4GB of RAM , it is best to allow SQL to determine its
> own memory usage. If you end up with two instances on the same node, they
> will come to a balance. You can lock those numbers into the settings, but
> be aware that changes in load man affect memory demand between the two
> instances.
> 6. Unless PSS tells you, don't change it.
> 7. No. Very No.
> 8. Again, go with the default.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "JT" <Jthayer@.online.nospam> wrote in message
> news:371EAB65-6324-4ABC-A798-E0A114B528B2@.microsoft.com...
>
>
|||Hi again Geoff. As I think about your answer, I think you may have
misunderstood my situation. I am not putting on two instances of SQL Server.
I am putting on one instance onto a virtual server running in active/passive
mode. In this situation, I would expect to not need spare ram to absorb the
second instance, as there will not be one. Would your answers change,
especially the /3GB, AWE and server memory options?
Thanks for your additional consideration of this question.
John
"Geoff N. Hiten" wrote:
> 1. No. And you can remove the /PAE switch from boot.ini. Unless you have
> MORE than 4GB of RAM , you don't need it.
> 2. No. You will need to have flexible memory incase the two instances land
> on the same host during a failover event.
> 3. Forget the pagefile RAID group. Put the pagefile on the OS partition.
> A properly tuned SQL server should not page. Put SQL Data and Logs on
> different RAID groups. If you only have two RAID groups, put Data on its
> own group and Logs on with the OS bits.
> 4. No change.
> 5. No change. With 4GB of RAM , it is best to allow SQL to determine its
> own memory usage. If you end up with two instances on the same node, they
> will come to a balance. You can lock those numbers into the settings, but
> be aware that changes in load man affect memory demand between the two
> instances.
> 6. Unless PSS tells you, don't change it.
> 7. No. Very No.
> 8. Again, go with the default.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "JT" <Jthayer@.online.nospam> wrote in message
> news:371EAB65-6324-4ABC-A798-E0A114B528B2@.microsoft.com...
>
>
|||Active/Passive is not the current nor the correct nomenclature. What you
are talking about is a Single-Instance cluster. With 4GB of RAM in each
host node, I would use the /3GB switch but not AWE or PAE. This KB article
may help (or it may confuse you beyond hope).
How to configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/default...b;en-us;274750
Geoff N. Hiten
Microsoft SQL Server MVP
"JT" <Jthayer@.online.nospam> wrote in message
news:4757AAF6-2A34-4961-8BD0-83580457F6EB@.microsoft.com...[vbcol=seagreen]
> Hi again Geoff. As I think about your answer, I think you may have
> misunderstood my situation. I am not putting on two instances of SQL
> Server.
> I am putting on one instance onto a virtual server running in
> active/passive
> mode. In this situation, I would expect to not need spare ram to absorb
> the
> second instance, as there will not be one. Would your answers change,
> especially the /3GB, AWE and server memory options?
> Thanks for your additional consideration of this question.
> --
> John
>
> "Geoff N. Hiten" wrote:
Memory Settings
Hi
I Have a sql server standard edition running on win2k server sp3.
1g Ram on the server.
The sever records plant data in an idustrial appilcation every minute.
After a week of use i have noticed that in the task manager view the memory consuption has increased yet when looking at the performance monitor total server memory is equal to target server memory. Is this correct as the memory settings are set to limit the sql server to 511meg as the sql process is greater than this.
Surely when sql reaches its limit is should release memory back to the system. Is this a memeory leak? or normal .
After another couple of days the sql server crashes and the only way out is a reboot
Can anyone help please very frustrating as the
--
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.>
> Hi
> I Have a sql server standard edition running on win2k server sp3.
> 1g Ram on the server.
> The sever records plant data in an idustrial appilcation every minute.
> After a week of use i have noticed that in the task manager view the
> memory consuption has increased yet when looking at the performance
> monitor total server memory is equal to target server memory. Is
> this correct as the memory settings are set to limit the sql server
> to 511meg as the sql process is greater than this.
> Surely when sql reaches its limit is should release memory back to
> the system. Is this a memeory leak? or normal .
> After another couple of days the sql server crashes and the only way out
is a reboot
>
--
If SQL Server were crashing, you should raise a case with Microsoft Product
Support so the crash can be diagnosed and remedied.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
I Have a sql server standard edition running on win2k server sp3.
1g Ram on the server.
The sever records plant data in an idustrial appilcation every minute.
After a week of use i have noticed that in the task manager view the memory consuption has increased yet when looking at the performance monitor total server memory is equal to target server memory. Is this correct as the memory settings are set to limit the sql server to 511meg as the sql process is greater than this.
Surely when sql reaches its limit is should release memory back to the system. Is this a memeory leak? or normal .
After another couple of days the sql server crashes and the only way out is a reboot
Can anyone help please very frustrating as the
--
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.>
> Hi
> I Have a sql server standard edition running on win2k server sp3.
> 1g Ram on the server.
> The sever records plant data in an idustrial appilcation every minute.
> After a week of use i have noticed that in the task manager view the
> memory consuption has increased yet when looking at the performance
> monitor total server memory is equal to target server memory. Is
> this correct as the memory settings are set to limit the sql server
> to 511meg as the sql process is greater than this.
> Surely when sql reaches its limit is should release memory back to
> the system. Is this a memeory leak? or normal .
> After another couple of days the sql server crashes and the only way out
is a reboot
>
--
If SQL Server were crashing, you should raise a case with Microsoft Product
Support so the crash can be diagnosed and remedied.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Memory Settings
Hi
I Have a sql server standard edition running on win2k server sp3.
1g Ram on the server.
The sever records plant data in an idustrial appilcation every minute.
After a week of use i have noticed that in the task manager view the memory consuption has increased yet when looking at the performance monitor total server memory is equal to target server memory. Is this correct as the memory settings are set to limit
the sql server to 511meg as the sql process is greater than this.
Surely when sql reaches its limit is should release memory back to the system. Is this a memeory leak? or normal .
After another couple of days the sql server crashes and the only way out is a reboot
Can anyone help please very frustrating as the
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
>
> Hi
> I Have a sql server standard edition running on win2k server sp3.
> 1g Ram on the server.
> The sever records plant data in an idustrial appilcation every minute.
> After a week of use i have noticed that in the task manager view the
> memory consuption has increased yet when looking at the performance
> monitor total server memory is equal to target server memory. Is
> this correct as the memory settings are set to limit the sql server
> to 511meg as the sql process is greater than this.
> Surely when sql reaches its limit is should release memory back to
> the system. Is this a memeory leak? or normal .
> After another couple of days the sql server crashes and the only way out
is a reboot
>
If SQL Server were crashing, you should raise a case with Microsoft Product
Support so the crash can be diagnosed and remedied.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
I Have a sql server standard edition running on win2k server sp3.
1g Ram on the server.
The sever records plant data in an idustrial appilcation every minute.
After a week of use i have noticed that in the task manager view the memory consuption has increased yet when looking at the performance monitor total server memory is equal to target server memory. Is this correct as the memory settings are set to limit
the sql server to 511meg as the sql process is greater than this.
Surely when sql reaches its limit is should release memory back to the system. Is this a memeory leak? or normal .
After another couple of days the sql server crashes and the only way out is a reboot
Can anyone help please very frustrating as the
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
>
> Hi
> I Have a sql server standard edition running on win2k server sp3.
> 1g Ram on the server.
> The sever records plant data in an idustrial appilcation every minute.
> After a week of use i have noticed that in the task manager view the
> memory consuption has increased yet when looking at the performance
> monitor total server memory is equal to target server memory. Is
> this correct as the memory settings are set to limit the sql server
> to 511meg as the sql process is greater than this.
> Surely when sql reaches its limit is should release memory back to
> the system. Is this a memeory leak? or normal .
> After another couple of days the sql server crashes and the only way out
is a reboot
>
If SQL Server were crashing, you should raise a case with Microsoft Product
Support so the crash can be diagnosed and remedied.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Memory Settings
Hi
I Have a sql server standard edition running on win2k server sp3.
1g Ram on the server.
The sever records plant data in an idustrial appilcation every minute.
After a week of use i have noticed that in the task manager view the memory
consuption has increased yet when looking at the performance monitor total s
erver memory is equal to target server memory. Is this correct as the memory
settings are set to limit
the sql server to 511meg as the sql process is greater than this.
Surely when sql reaches its limit is should release memory back to the syste
m. Is this a memeory leak? or normal .
After another couple of days the sql server crashes and the only way out is
a reboot
Can anyone help please very frustrating as the
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine sup
ports Post Alerts, Ratings, and Searching.>
> Hi
> I Have a sql server standard edition running on win2k server sp3.
> 1g Ram on the server.
> The sever records plant data in an idustrial appilcation every minute.
> After a week of use i have noticed that in the task manager view the
> memory consuption has increased yet when looking at the performance
> monitor total server memory is equal to target server memory. Is
> this correct as the memory settings are set to limit the sql server
> to 511meg as the sql process is greater than this.
> Surely when sql reaches its limit is should release memory back to
> the system. Is this a memeory leak? or normal .
> After another couple of days the sql server crashes and the only way out
is a reboot
>
--
If SQL Server were crashing, you should raise a case with Microsoft Product
Support so the crash can be diagnosed and remedied.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
I Have a sql server standard edition running on win2k server sp3.
1g Ram on the server.
The sever records plant data in an idustrial appilcation every minute.
After a week of use i have noticed that in the task manager view the memory
consuption has increased yet when looking at the performance monitor total s
erver memory is equal to target server memory. Is this correct as the memory
settings are set to limit
the sql server to 511meg as the sql process is greater than this.
Surely when sql reaches its limit is should release memory back to the syste
m. Is this a memeory leak? or normal .
After another couple of days the sql server crashes and the only way out is
a reboot
Can anyone help please very frustrating as the
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine sup
ports Post Alerts, Ratings, and Searching.>
> Hi
> I Have a sql server standard edition running on win2k server sp3.
> 1g Ram on the server.
> The sever records plant data in an idustrial appilcation every minute.
> After a week of use i have noticed that in the task manager view the
> memory consuption has increased yet when looking at the performance
> monitor total server memory is equal to target server memory. Is
> this correct as the memory settings are set to limit the sql server
> to 511meg as the sql process is greater than this.
> Surely when sql reaches its limit is should release memory back to
> the system. Is this a memeory leak? or normal .
> After another couple of days the sql server crashes and the only way out
is a reboot
>
--
If SQL Server were crashing, you should raise a case with Microsoft Product
Support so the crash can be diagnosed and remedied.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Wednesday, March 7, 2012
Memory Problem
Hello,
I look after several SQL server DB's, all are SQL 2000 standard edition,
some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
fine and dandy, except for one application that's causing me a headache. The
SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
and sits on a dual processor box with 2GB of RAM.
Through profiler and performance monitor I can see the app logs into SQL,
runs a sql statement, and logs out again - it does this circa 250 times every
30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
release it, seemingly it's due to this login process (on perfmon I can see
when the logins occur every 30 seconds or so, and using taskmanager I can see
inline with this login process the memory sqlservr.exe uses increases). The
memory increases at a rate of around 116mb per hour, and when it hits the
physical limit, SQL crashes. The actual error in the log relates to
CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
over.
Anyone any ideas why this is happening?
Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for the
related error messages? If you still didn't find anything, you should open a case with MS.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> Hello,
> I look after several SQL server DB's, all are SQL 2000 standard edition,
> some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> fine and dandy, except for one application that's causing me a headache. The
> SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> and sits on a dual processor box with 2GB of RAM.
> Through profiler and performance monitor I can see the app logs into SQL,
> runs a sql statement, and logs out again - it does this circa 250 times every
> 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> release it, seemingly it's due to this login process (on perfmon I can see
> when the logins occur every 30 seconds or so, and using taskmanager I can see
> inline with this login process the memory sqlservr.exe uses increases). The
> memory increases at a rate of around 116mb per hour, and when it hits the
> physical limit, SQL crashes. The actual error in the log relates to
> CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> over.
> Anyone any ideas why this is happening?
|||Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
KB articles that cover the issue, can't find anything on web at all really (a
part from a couple with slight relavance)
"Tibor Karaszi" wrote:
> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for the
> related error messages? If you still didn't find anything, you should open a case with MS.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
>
>
|||I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
that your code hit a memory leak in that code section of SQL Server, and that you would need
assistance from MS to either work around it or have them prepare a hotfix for you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...[vbcol=seagreen]
> Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> KB articles that cover the issue, can't find anything on web at all really (a
> part from a couple with slight relavance)
> "Tibor Karaszi" wrote:
|||Thanks for your help Tibor :-)
"Tibor Karaszi" wrote:
> I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
> that your code hit a memory leak in that code section of SQL Server, and that you would need
> assistance from MS to either work around it or have them prepare a hotfix for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
>
>
|||If you do get a fix would you mind posting it so we can see what
happened....thanks.
burt_king@.yahoo.com
"BenUK" wrote:
[vbcol=seagreen]
> Thanks for your help Tibor :-)
> "Tibor Karaszi" wrote:
|||no problem, will do
"burt_king" wrote:
[vbcol=seagreen]
> If you do get a fix would you mind posting it so we can see what
> happened....thanks.
> --
> burt_king@.yahoo.com
>
> "BenUK" wrote:
|||You can increase machine to 3GB, and let SQL Server use full 2gb and leave
1GB for OS.
I look after several SQL server DB's, all are SQL 2000 standard edition,
some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
fine and dandy, except for one application that's causing me a headache. The
SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
and sits on a dual processor box with 2GB of RAM.
Through profiler and performance monitor I can see the app logs into SQL,
runs a sql statement, and logs out again - it does this circa 250 times every
30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
release it, seemingly it's due to this login process (on perfmon I can see
when the logins occur every 30 seconds or so, and using taskmanager I can see
inline with this login process the memory sqlservr.exe uses increases). The
memory increases at a rate of around 116mb per hour, and when it hits the
physical limit, SQL crashes. The actual error in the log relates to
CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
over.
Anyone any ideas why this is happening?
Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for the
related error messages? If you still didn't find anything, you should open a case with MS.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> Hello,
> I look after several SQL server DB's, all are SQL 2000 standard edition,
> some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> fine and dandy, except for one application that's causing me a headache. The
> SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> and sits on a dual processor box with 2GB of RAM.
> Through profiler and performance monitor I can see the app logs into SQL,
> runs a sql statement, and logs out again - it does this circa 250 times every
> 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> release it, seemingly it's due to this login process (on perfmon I can see
> when the logins occur every 30 seconds or so, and using taskmanager I can see
> inline with this login process the memory sqlservr.exe uses increases). The
> memory increases at a rate of around 116mb per hour, and when it hits the
> physical limit, SQL crashes. The actual error in the log relates to
> CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> over.
> Anyone any ideas why this is happening?
|||Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
KB articles that cover the issue, can't find anything on web at all really (a
part from a couple with slight relavance)
"Tibor Karaszi" wrote:
> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for the
> related error messages? If you still didn't find anything, you should open a case with MS.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
>
>
|||I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
that your code hit a memory leak in that code section of SQL Server, and that you would need
assistance from MS to either work around it or have them prepare a hotfix for you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...[vbcol=seagreen]
> Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> KB articles that cover the issue, can't find anything on web at all really (a
> part from a couple with slight relavance)
> "Tibor Karaszi" wrote:
|||Thanks for your help Tibor :-)
"Tibor Karaszi" wrote:
> I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
> that your code hit a memory leak in that code section of SQL Server, and that you would need
> assistance from MS to either work around it or have them prepare a hotfix for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
>
>
|||If you do get a fix would you mind posting it so we can see what
happened....thanks.
burt_king@.yahoo.com
"BenUK" wrote:
[vbcol=seagreen]
> Thanks for your help Tibor :-)
> "Tibor Karaszi" wrote:
|||no problem, will do
"burt_king" wrote:
[vbcol=seagreen]
> If you do get a fix would you mind posting it so we can see what
> happened....thanks.
> --
> burt_king@.yahoo.com
>
> "BenUK" wrote:
|||You can increase machine to 3GB, and let SQL Server use full 2gb and leave
1GB for OS.
Memory Problem
Hello,
I look after several SQL server DB's, all are SQL 2000 standard edition,
some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
fine and dandy, except for one application that's causing me a headache. The
SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
and sits on a dual processor box with 2GB of RAM.
Through profiler and performance monitor I can see the app logs into SQL,
runs a sql statement, and logs out again - it does this circa 250 times every
30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
release it, seemingly it's due to this login process (on perfmon I can see
when the logins occur every 30 seconds or so, and using taskmanager I can see
inline with this login process the memory sqlservr.exe uses increases). The
memory increases at a rate of around 116mb per hour, and when it hits the
physical limit, SQL crashes. The actual error in the log relates to
CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
over.
Anyone any ideas why this is happening?Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for the
related error messages? If you still didn't find anything, you should open a case with MS.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> Hello,
> I look after several SQL server DB's, all are SQL 2000 standard edition,
> some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> fine and dandy, except for one application that's causing me a headache. The
> SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> and sits on a dual processor box with 2GB of RAM.
> Through profiler and performance monitor I can see the app logs into SQL,
> runs a sql statement, and logs out again - it does this circa 250 times every
> 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> release it, seemingly it's due to this login process (on perfmon I can see
> when the logins occur every 30 seconds or so, and using taskmanager I can see
> inline with this login process the memory sqlservr.exe uses increases). The
> memory increases at a rate of around 116mb per hour, and when it hits the
> physical limit, SQL crashes. The actual error in the log relates to
> CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> over.
> Anyone any ideas why this is happening?|||Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
KB articles that cover the issue, can't find anything on web at all really (a
part from a couple with slight relavance)
"Tibor Karaszi" wrote:
> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for the
> related error messages? If you still didn't find anything, you should open a case with MS.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> > Hello,
> >
> > I look after several SQL server DB's, all are SQL 2000 standard edition,
> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> > fine and dandy, except for one application that's causing me a headache. The
> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> > and sits on a dual processor box with 2GB of RAM.
> > Through profiler and performance monitor I can see the app logs into SQL,
> > runs a sql statement, and logs out again - it does this circa 250 times every
> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> > release it, seemingly it's due to this login process (on perfmon I can see
> > when the logins occur every 30 seconds or so, and using taskmanager I can see
> > inline with this login process the memory sqlservr.exe uses increases). The
> > memory increases at a rate of around 116mb per hour, and when it hits the
> > physical limit, SQL crashes. The actual error in the log relates to
> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> > over.
> >
> > Anyone any ideas why this is happening?
>
>|||I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
that your code hit a memory leak in that code section of SQL Server, and that you would need
assistance from MS to either work around it or have them prepare a hotfix for you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
> Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> KB articles that cover the issue, can't find anything on web at all really (a
> part from a couple with slight relavance)
> "Tibor Karaszi" wrote:
>> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for
>> the
>> related error messages? If you still didn't find anything, you should open a case with MS.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
>> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
>> > Hello,
>> >
>> > I look after several SQL server DB's, all are SQL 2000 standard edition,
>> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
>> > fine and dandy, except for one application that's causing me a headache. The
>> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
>> > and sits on a dual processor box with 2GB of RAM.
>> > Through profiler and performance monitor I can see the app logs into SQL,
>> > runs a sql statement, and logs out again - it does this circa 250 times every
>> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
>> > release it, seemingly it's due to this login process (on perfmon I can see
>> > when the logins occur every 30 seconds or so, and using taskmanager I can see
>> > inline with this login process the memory sqlservr.exe uses increases). The
>> > memory increases at a rate of around 116mb per hour, and when it hits the
>> > physical limit, SQL crashes. The actual error in the log relates to
>> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
>> > over.
>> >
>> > Anyone any ideas why this is happening?
>>|||Thanks for your help Tibor :-)
"Tibor Karaszi" wrote:
> I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
> that your code hit a memory leak in that code section of SQL Server, and that you would need
> assistance from MS to either work around it or have them prepare a hotfix for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
> > Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> > KB articles that cover the issue, can't find anything on web at all really (a
> > part from a couple with slight relavance)
> >
> > "Tibor Karaszi" wrote:
> >
> >> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for
> >> the
> >> related error messages? If you still didn't find anything, you should open a case with MS.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> >> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> >> > Hello,
> >> >
> >> > I look after several SQL server DB's, all are SQL 2000 standard edition,
> >> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> >> > fine and dandy, except for one application that's causing me a headache. The
> >> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> >> > and sits on a dual processor box with 2GB of RAM.
> >> > Through profiler and performance monitor I can see the app logs into SQL,
> >> > runs a sql statement, and logs out again - it does this circa 250 times every
> >> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> >> > release it, seemingly it's due to this login process (on perfmon I can see
> >> > when the logins occur every 30 seconds or so, and using taskmanager I can see
> >> > inline with this login process the memory sqlservr.exe uses increases). The
> >> > memory increases at a rate of around 116mb per hour, and when it hits the
> >> > physical limit, SQL crashes. The actual error in the log relates to
> >> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> >> > over.
> >> >
> >> > Anyone any ideas why this is happening?
> >>
> >>
> >>
>
>|||If you do get a fix would you mind posting it so we can see what
happened....thanks.
--
burt_king@.yahoo.com
"BenUK" wrote:
> Thanks for your help Tibor :-)
> "Tibor Karaszi" wrote:
> > I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
> > that your code hit a memory leak in that code section of SQL Server, and that you would need
> > assistance from MS to either work around it or have them prepare a hotfix for you.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> > news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
> > > Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> > > KB articles that cover the issue, can't find anything on web at all really (a
> > > part from a couple with slight relavance)
> > >
> > > "Tibor Karaszi" wrote:
> > >
> > >> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for
> > >> the
> > >> related error messages? If you still didn't find anything, you should open a case with MS.
> > >>
> > >> --
> > >> Tibor Karaszi, SQL Server MVP
> > >> http://www.karaszi.com/sqlserver/default.asp
> > >> http://www.solidqualitylearning.com/
> > >>
> > >>
> > >> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> > >> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> > >> > Hello,
> > >> >
> > >> > I look after several SQL server DB's, all are SQL 2000 standard edition,
> > >> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> > >> > fine and dandy, except for one application that's causing me a headache. The
> > >> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> > >> > and sits on a dual processor box with 2GB of RAM.
> > >> > Through profiler and performance monitor I can see the app logs into SQL,
> > >> > runs a sql statement, and logs out again - it does this circa 250 times every
> > >> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> > >> > release it, seemingly it's due to this login process (on perfmon I can see
> > >> > when the logins occur every 30 seconds or so, and using taskmanager I can see
> > >> > inline with this login process the memory sqlservr.exe uses increases). The
> > >> > memory increases at a rate of around 116mb per hour, and when it hits the
> > >> > physical limit, SQL crashes. The actual error in the log relates to
> > >> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> > >> > over.
> > >> >
> > >> > Anyone any ideas why this is happening?
> > >>
> > >>
> > >>
> >
> >
> >|||no problem, will do
"burt_king" wrote:
> If you do get a fix would you mind posting it so we can see what
> happened....thanks.
> --
> burt_king@.yahoo.com
>
> "BenUK" wrote:
> > Thanks for your help Tibor :-)
> >
> > "Tibor Karaszi" wrote:
> >
> > > I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
> > > that your code hit a memory leak in that code section of SQL Server, and that you would need
> > > assistance from MS to either work around it or have them prepare a hotfix for you.
> > >
> > > --
> > > Tibor Karaszi, SQL Server MVP
> > > http://www.karaszi.com/sqlserver/default.asp
> > > http://www.solidqualitylearning.com/
> > >
> > >
> > > "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> > > news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
> > > > Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> > > > KB articles that cover the issue, can't find anything on web at all really (a
> > > > part from a couple with slight relavance)
> > > >
> > > > "Tibor Karaszi" wrote:
> > > >
> > > >> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for
> > > >> the
> > > >> related error messages? If you still didn't find anything, you should open a case with MS.
> > > >>
> > > >> --
> > > >> Tibor Karaszi, SQL Server MVP
> > > >> http://www.karaszi.com/sqlserver/default.asp
> > > >> http://www.solidqualitylearning.com/
> > > >>
> > > >>
> > > >> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> > > >> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> > > >> > Hello,
> > > >> >
> > > >> > I look after several SQL server DB's, all are SQL 2000 standard edition,
> > > >> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> > > >> > fine and dandy, except for one application that's causing me a headache. The
> > > >> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> > > >> > and sits on a dual processor box with 2GB of RAM.
> > > >> > Through profiler and performance monitor I can see the app logs into SQL,
> > > >> > runs a sql statement, and logs out again - it does this circa 250 times every
> > > >> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> > > >> > release it, seemingly it's due to this login process (on perfmon I can see
> > > >> > when the logins occur every 30 seconds or so, and using taskmanager I can see
> > > >> > inline with this login process the memory sqlservr.exe uses increases). The
> > > >> > memory increases at a rate of around 116mb per hour, and when it hits the
> > > >> > physical limit, SQL crashes. The actual error in the log relates to
> > > >> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> > > >> > over.
> > > >> >
> > > >> > Anyone any ideas why this is happening?
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >|||You can increase machine to 3GB, and let SQL Server use full 2gb and leave
1GB for OS.
I look after several SQL server DB's, all are SQL 2000 standard edition,
some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
fine and dandy, except for one application that's causing me a headache. The
SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
and sits on a dual processor box with 2GB of RAM.
Through profiler and performance monitor I can see the app logs into SQL,
runs a sql statement, and logs out again - it does this circa 250 times every
30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
release it, seemingly it's due to this login process (on perfmon I can see
when the logins occur every 30 seconds or so, and using taskmanager I can see
inline with this login process the memory sqlservr.exe uses increases). The
memory increases at a rate of around 116mb per hour, and when it hits the
physical limit, SQL crashes. The actual error in the log relates to
CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
over.
Anyone any ideas why this is happening?Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for the
related error messages? If you still didn't find anything, you should open a case with MS.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> Hello,
> I look after several SQL server DB's, all are SQL 2000 standard edition,
> some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> fine and dandy, except for one application that's causing me a headache. The
> SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> and sits on a dual processor box with 2GB of RAM.
> Through profiler and performance monitor I can see the app logs into SQL,
> runs a sql statement, and logs out again - it does this circa 250 times every
> 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> release it, seemingly it's due to this login process (on perfmon I can see
> when the logins occur every 30 seconds or so, and using taskmanager I can see
> inline with this login process the memory sqlservr.exe uses increases). The
> memory increases at a rate of around 116mb per hour, and when it hits the
> physical limit, SQL crashes. The actual error in the log relates to
> CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> over.
> Anyone any ideas why this is happening?|||Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
KB articles that cover the issue, can't find anything on web at all really (a
part from a couple with slight relavance)
"Tibor Karaszi" wrote:
> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for the
> related error messages? If you still didn't find anything, you should open a case with MS.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> > Hello,
> >
> > I look after several SQL server DB's, all are SQL 2000 standard edition,
> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> > fine and dandy, except for one application that's causing me a headache. The
> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> > and sits on a dual processor box with 2GB of RAM.
> > Through profiler and performance monitor I can see the app logs into SQL,
> > runs a sql statement, and logs out again - it does this circa 250 times every
> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> > release it, seemingly it's due to this login process (on perfmon I can see
> > when the logins occur every 30 seconds or so, and using taskmanager I can see
> > inline with this login process the memory sqlservr.exe uses increases). The
> > memory increases at a rate of around 116mb per hour, and when it hits the
> > physical limit, SQL crashes. The actual error in the log relates to
> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> > over.
> >
> > Anyone any ideas why this is happening?
>
>|||I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
that your code hit a memory leak in that code section of SQL Server, and that you would need
assistance from MS to either work around it or have them prepare a hotfix for you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
> Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> KB articles that cover the issue, can't find anything on web at all really (a
> part from a couple with slight relavance)
> "Tibor Karaszi" wrote:
>> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for
>> the
>> related error messages? If you still didn't find anything, you should open a case with MS.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
>> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
>> > Hello,
>> >
>> > I look after several SQL server DB's, all are SQL 2000 standard edition,
>> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
>> > fine and dandy, except for one application that's causing me a headache. The
>> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
>> > and sits on a dual processor box with 2GB of RAM.
>> > Through profiler and performance monitor I can see the app logs into SQL,
>> > runs a sql statement, and logs out again - it does this circa 250 times every
>> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
>> > release it, seemingly it's due to this login process (on perfmon I can see
>> > when the logins occur every 30 seconds or so, and using taskmanager I can see
>> > inline with this login process the memory sqlservr.exe uses increases). The
>> > memory increases at a rate of around 116mb per hour, and when it hits the
>> > physical limit, SQL crashes. The actual error in the log relates to
>> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
>> > over.
>> >
>> > Anyone any ideas why this is happening?
>>|||Thanks for your help Tibor :-)
"Tibor Karaszi" wrote:
> I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
> that your code hit a memory leak in that code section of SQL Server, and that you would need
> assistance from MS to either work around it or have them prepare a hotfix for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
> > Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> > KB articles that cover the issue, can't find anything on web at all really (a
> > part from a couple with slight relavance)
> >
> > "Tibor Karaszi" wrote:
> >
> >> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for
> >> the
> >> related error messages? If you still didn't find anything, you should open a case with MS.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> >> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> >> > Hello,
> >> >
> >> > I look after several SQL server DB's, all are SQL 2000 standard edition,
> >> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> >> > fine and dandy, except for one application that's causing me a headache. The
> >> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> >> > and sits on a dual processor box with 2GB of RAM.
> >> > Through profiler and performance monitor I can see the app logs into SQL,
> >> > runs a sql statement, and logs out again - it does this circa 250 times every
> >> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> >> > release it, seemingly it's due to this login process (on perfmon I can see
> >> > when the logins occur every 30 seconds or so, and using taskmanager I can see
> >> > inline with this login process the memory sqlservr.exe uses increases). The
> >> > memory increases at a rate of around 116mb per hour, and when it hits the
> >> > physical limit, SQL crashes. The actual error in the log relates to
> >> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> >> > over.
> >> >
> >> > Anyone any ideas why this is happening?
> >>
> >>
> >>
>
>|||If you do get a fix would you mind posting it so we can see what
happened....thanks.
--
burt_king@.yahoo.com
"BenUK" wrote:
> Thanks for your help Tibor :-)
> "Tibor Karaszi" wrote:
> > I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
> > that your code hit a memory leak in that code section of SQL Server, and that you would need
> > assistance from MS to either work around it or have them prepare a hotfix for you.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> > news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
> > > Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> > > KB articles that cover the issue, can't find anything on web at all really (a
> > > part from a couple with slight relavance)
> > >
> > > "Tibor Karaszi" wrote:
> > >
> > >> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for
> > >> the
> > >> related error messages? If you still didn't find anything, you should open a case with MS.
> > >>
> > >> --
> > >> Tibor Karaszi, SQL Server MVP
> > >> http://www.karaszi.com/sqlserver/default.asp
> > >> http://www.solidqualitylearning.com/
> > >>
> > >>
> > >> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> > >> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> > >> > Hello,
> > >> >
> > >> > I look after several SQL server DB's, all are SQL 2000 standard edition,
> > >> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> > >> > fine and dandy, except for one application that's causing me a headache. The
> > >> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> > >> > and sits on a dual processor box with 2GB of RAM.
> > >> > Through profiler and performance monitor I can see the app logs into SQL,
> > >> > runs a sql statement, and logs out again - it does this circa 250 times every
> > >> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> > >> > release it, seemingly it's due to this login process (on perfmon I can see
> > >> > when the logins occur every 30 seconds or so, and using taskmanager I can see
> > >> > inline with this login process the memory sqlservr.exe uses increases). The
> > >> > memory increases at a rate of around 116mb per hour, and when it hits the
> > >> > physical limit, SQL crashes. The actual error in the log relates to
> > >> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> > >> > over.
> > >> >
> > >> > Anyone any ideas why this is happening?
> > >>
> > >>
> > >>
> >
> >
> >|||no problem, will do
"burt_king" wrote:
> If you do get a fix would you mind posting it so we can see what
> happened....thanks.
> --
> burt_king@.yahoo.com
>
> "BenUK" wrote:
> > Thanks for your help Tibor :-)
> >
> > "Tibor Karaszi" wrote:
> >
> > > I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
> > > that your code hit a memory leak in that code section of SQL Server, and that you would need
> > > assistance from MS to either work around it or have them prepare a hotfix for you.
> > >
> > > --
> > > Tibor Karaszi, SQL Server MVP
> > > http://www.karaszi.com/sqlserver/default.asp
> > > http://www.solidqualitylearning.com/
> > >
> > >
> > > "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> > > news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
> > > > Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> > > > KB articles that cover the issue, can't find anything on web at all really (a
> > > > part from a couple with slight relavance)
> > > >
> > > > "Tibor Karaszi" wrote:
> > > >
> > > >> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for
> > > >> the
> > > >> related error messages? If you still didn't find anything, you should open a case with MS.
> > > >>
> > > >> --
> > > >> Tibor Karaszi, SQL Server MVP
> > > >> http://www.karaszi.com/sqlserver/default.asp
> > > >> http://www.solidqualitylearning.com/
> > > >>
> > > >>
> > > >> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> > > >> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> > > >> > Hello,
> > > >> >
> > > >> > I look after several SQL server DB's, all are SQL 2000 standard edition,
> > > >> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> > > >> > fine and dandy, except for one application that's causing me a headache. The
> > > >> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> > > >> > and sits on a dual processor box with 2GB of RAM.
> > > >> > Through profiler and performance monitor I can see the app logs into SQL,
> > > >> > runs a sql statement, and logs out again - it does this circa 250 times every
> > > >> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> > > >> > release it, seemingly it's due to this login process (on perfmon I can see
> > > >> > when the logins occur every 30 seconds or so, and using taskmanager I can see
> > > >> > inline with this login process the memory sqlservr.exe uses increases). The
> > > >> > memory increases at a rate of around 116mb per hour, and when it hits the
> > > >> > physical limit, SQL crashes. The actual error in the log relates to
> > > >> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> > > >> > over.
> > > >> >
> > > >> > Anyone any ideas why this is happening?
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >|||You can increase machine to 3GB, and let SQL Server use full 2gb and leave
1GB for OS.
Memory Problem
Hello,
I look after several SQL server DB's, all are SQL 2000 standard edition,
some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
fine and dandy, except for one application that's causing me a headache. Th
e
SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1
,
and sits on a dual processor box with 2GB of RAM.
Through profiler and performance monitor I can see the app logs into SQL,
runs a sql statement, and logs out again - it does this circa 250 times ever
y
30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
release it, seemingly it's due to this login process (on perfmon I can see
when the logins occur every 30 seconds or so, and using taskmanager I can se
e
inline with this login process the memory sqlservr.exe uses increases). The
memory increases at a rate of around 116mb per hour, and when it hits the
physical limit, SQL crashes. The actual error in the log relates to
CImageHelper:: and dbghelp.dll and gets posted several times before SQL fall
s
over.
Anyone any ideas why this is happening?Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Di
d you search KB for the
related error messages? If you still didn't find anything, you should open a
case with MS.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> Hello,
> I look after several SQL server DB's, all are SQL 2000 standard edition,
> some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> fine and dandy, except for one application that's causing me a headache.
The
> SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 S
P1,
> and sits on a dual processor box with 2GB of RAM.
> Through profiler and performance monitor I can see the app logs into SQL,
> runs a sql statement, and logs out again - it does this circa 250 times ev
ery
> 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn'
t
> release it, seemingly it's due to this login process (on perfmon I can see
> when the logins occur every 30 seconds or so, and using taskmanager I can
see
> inline with this login process the memory sqlservr.exe uses increases). T
he
> memory increases at a rate of around 116mb per hour, and when it hits the
> physical limit, SQL crashes. The actual error in the log relates to
> CImageHelper:: and dbghelp.dll and gets posted several times before SQL fa
lls
> over.
> Anyone any ideas why this is happening?|||Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
KB articles that cover the issue, can't find anything on web at all really (
a
part from a couple with slight relavance)
"Tibor Karaszi" wrote:
> Sounds like you hit a bug in SQL Server. Are you current on Service Pack?
Did you search KB for the
> related error messages? If you still didn't find anything, you should open
a case with MS.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
>
>|||I did a quick Google search and I guess we found similar cases. Not exactly
your case. My guess is
that your code hit a memory leak in that code section of SQL Server, and tha
t you would need
assistance from MS to either work around it or have them prepare a hotfix fo
r you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...[vbcol=seagreen]
> Thanks for the reply Tibor, We're on SP4 (which is current), Can't find an
y
> KB articles that cover the issue, can't find anything on web at all really
(a
> part from a couple with slight relavance)
> "Tibor Karaszi" wrote:
>|||Thanks for your help Tibor :-)
"Tibor Karaszi" wrote:
> I did a quick Google search and I guess we found similar cases. Not exactl
y your case. My guess is
> that your code hit a memory leak in that code section of SQL Server, and t
hat you would need
> assistance from MS to either work around it or have them prepare a hotfix
for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
>
>|||If you do get a fix would you mind posting it so we can see what
happened....thanks.
--
burt_king@.yahoo.com
"BenUK" wrote:
[vbcol=seagreen]
> Thanks for your help Tibor :-)
> "Tibor Karaszi" wrote:
>|||no problem, will do
"burt_king" wrote:
[vbcol=seagreen]
> If you do get a fix would you mind posting it so we can see what
> happened....thanks.
> --
> burt_king@.yahoo.com
>
> "BenUK" wrote:
>|||You can increase machine to 3GB, and let SQL Server use full 2gb and leave
1GB for OS.
I look after several SQL server DB's, all are SQL 2000 standard edition,
some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
fine and dandy, except for one application that's causing me a headache. Th
e
SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1
,
and sits on a dual processor box with 2GB of RAM.
Through profiler and performance monitor I can see the app logs into SQL,
runs a sql statement, and logs out again - it does this circa 250 times ever
y
30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
release it, seemingly it's due to this login process (on perfmon I can see
when the logins occur every 30 seconds or so, and using taskmanager I can se
e
inline with this login process the memory sqlservr.exe uses increases). The
memory increases at a rate of around 116mb per hour, and when it hits the
physical limit, SQL crashes. The actual error in the log relates to
CImageHelper:: and dbghelp.dll and gets posted several times before SQL fall
s
over.
Anyone any ideas why this is happening?Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Di
d you search KB for the
related error messages? If you still didn't find anything, you should open a
case with MS.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> Hello,
> I look after several SQL server DB's, all are SQL 2000 standard edition,
> some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> fine and dandy, except for one application that's causing me a headache.
The
> SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 S
P1,
> and sits on a dual processor box with 2GB of RAM.
> Through profiler and performance monitor I can see the app logs into SQL,
> runs a sql statement, and logs out again - it does this circa 250 times ev
ery
> 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn'
t
> release it, seemingly it's due to this login process (on perfmon I can see
> when the logins occur every 30 seconds or so, and using taskmanager I can
see
> inline with this login process the memory sqlservr.exe uses increases). T
he
> memory increases at a rate of around 116mb per hour, and when it hits the
> physical limit, SQL crashes. The actual error in the log relates to
> CImageHelper:: and dbghelp.dll and gets posted several times before SQL fa
lls
> over.
> Anyone any ideas why this is happening?|||Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
KB articles that cover the issue, can't find anything on web at all really (
a
part from a couple with slight relavance)
"Tibor Karaszi" wrote:
> Sounds like you hit a bug in SQL Server. Are you current on Service Pack?
Did you search KB for the
> related error messages? If you still didn't find anything, you should open
a case with MS.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
>
>|||I did a quick Google search and I guess we found similar cases. Not exactly
your case. My guess is
that your code hit a memory leak in that code section of SQL Server, and tha
t you would need
assistance from MS to either work around it or have them prepare a hotfix fo
r you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...[vbcol=seagreen]
> Thanks for the reply Tibor, We're on SP4 (which is current), Can't find an
y
> KB articles that cover the issue, can't find anything on web at all really
(a
> part from a couple with slight relavance)
> "Tibor Karaszi" wrote:
>|||Thanks for your help Tibor :-)
"Tibor Karaszi" wrote:
> I did a quick Google search and I guess we found similar cases. Not exactl
y your case. My guess is
> that your code hit a memory leak in that code section of SQL Server, and t
hat you would need
> assistance from MS to either work around it or have them prepare a hotfix
for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
>
>|||If you do get a fix would you mind posting it so we can see what
happened....thanks.
--
burt_king@.yahoo.com
"BenUK" wrote:
[vbcol=seagreen]
> Thanks for your help Tibor :-)
> "Tibor Karaszi" wrote:
>|||no problem, will do
"burt_king" wrote:
[vbcol=seagreen]
> If you do get a fix would you mind posting it so we can see what
> happened....thanks.
> --
> burt_king@.yahoo.com
>
> "BenUK" wrote:
>|||You can increase machine to 3GB, and let SQL Server use full 2gb and leave
1GB for OS.
Friday, February 24, 2012
memory performance
The server is a SQL2k standard edition SP3, on Win2k server.
I have 4GB physical memory and 5GB page file.
I know that SQL2k standard edition can only utilize 2GB memory.
Running perfmon caught Process\SQLserver\pagefaults/sec and working set.
The working set maximum is 1779MB and pagefults/sec maximum is 34.
Do I have memory problem?
Thanks in advance.
Looks fine to me.
Andrew J. Kelly SQL MVP
"mike" <mike@.discussions.microsoft.com> wrote in message
news:BC14859F-F926-484A-9DFD-569C301A43E6@.microsoft.com...
> The server is a SQL2k standard edition SP3, on Win2k server.
> I have 4GB physical memory and 5GB page file.
> I know that SQL2k standard edition can only utilize 2GB memory.
> Running perfmon caught Process\SQLserver\pagefaults/sec and working set.
> The working set maximum is 1779MB and pagefults/sec maximum is 34.
> Do I have memory problem?
> Thanks in advance.
I have 4GB physical memory and 5GB page file.
I know that SQL2k standard edition can only utilize 2GB memory.
Running perfmon caught Process\SQLserver\pagefaults/sec and working set.
The working set maximum is 1779MB and pagefults/sec maximum is 34.
Do I have memory problem?
Thanks in advance.
Looks fine to me.
Andrew J. Kelly SQL MVP
"mike" <mike@.discussions.microsoft.com> wrote in message
news:BC14859F-F926-484A-9DFD-569C301A43E6@.microsoft.com...
> The server is a SQL2k standard edition SP3, on Win2k server.
> I have 4GB physical memory and 5GB page file.
> I know that SQL2k standard edition can only utilize 2GB memory.
> Running perfmon caught Process\SQLserver\pagefaults/sec and working set.
> The working set maximum is 1779MB and pagefults/sec maximum is 34.
> Do I have memory problem?
> Thanks in advance.
memory performance
The server is a SQL2k standard edition SP3, on Win2k server.
I have 4GB physical memory and 5GB page file.
I know that SQL2k standard edition can only utilize 2GB memory.
Running perfmon caught Process\SQLserver\pagefaults/sec and working set.
The working set maximum is 1779MB and pagefults/sec maximum is 34.
Do I have memory problem?
Thanks in advance.Looks fine to me.
Andrew J. Kelly SQL MVP
"mike" <mike@.discussions.microsoft.com> wrote in message
news:BC14859F-F926-484A-9DFD-569C301A43E6@.microsoft.com...
> The server is a SQL2k standard edition SP3, on Win2k server.
> I have 4GB physical memory and 5GB page file.
> I know that SQL2k standard edition can only utilize 2GB memory.
> Running perfmon caught Process\SQLserver\pagefaults/sec and working set.
> The working set maximum is 1779MB and pagefults/sec maximum is 34.
> Do I have memory problem?
> Thanks in advance.
I have 4GB physical memory and 5GB page file.
I know that SQL2k standard edition can only utilize 2GB memory.
Running perfmon caught Process\SQLserver\pagefaults/sec and working set.
The working set maximum is 1779MB and pagefults/sec maximum is 34.
Do I have memory problem?
Thanks in advance.Looks fine to me.
Andrew J. Kelly SQL MVP
"mike" <mike@.discussions.microsoft.com> wrote in message
news:BC14859F-F926-484A-9DFD-569C301A43E6@.microsoft.com...
> The server is a SQL2k standard edition SP3, on Win2k server.
> I have 4GB physical memory and 5GB page file.
> I know that SQL2k standard edition can only utilize 2GB memory.
> Running perfmon caught Process\SQLserver\pagefaults/sec and working set.
> The working set maximum is 1779MB and pagefults/sec maximum is 34.
> Do I have memory problem?
> Thanks in advance.
Subscribe to:
Comments (Atom)