Hi All
Can anybody tell me why Memory is not utilized by MSSQL Service. The Environment as follows..
It is an Critical Web based Application with SQL 2000 Standard Edition + SP3 as backend
OS: Win 2000 Advanced Server + 3GB Memory + 2 CP
MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2 GB". This Server has Replication
Configuration also. During peak time or non-peak time, it always use 1 GB Memory only. Why MSSQL is not taking more than 1 GB, even though server has got 3 GB and database's max. memory configured as 2 GB
In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we will give /3GB in boot.ini. Similarly anything should be given for SQL 2000 Standard Edition. Right now, boot.ini doesn't contain this option
Appreciate your help on this
tks in advance
vasuAre you running other applications on the server besides SQL Server? SQL
Server will manage memory based on amount of free memory available.
Consequently, if other apps running on the same box (e.g. IIS) consume
significant amounts of memory, SQL Server won't acquire additional memory
because this would negatively impact performance.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"vasum" <anonymous@.discussions.microsoft.com> wrote in message
news:E2239F3D-53B5-4DA7-B7AC-280DC8B54ED7@.microsoft.com...
> Hi All,
> Can anybody tell me why Memory is not utilized by MSSQL Service. The
Environment as follows...
> It is an Critical Web based Application with SQL 2000 Standard Edition +
SP3 as backend .
> OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
> MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2
GB". This Server has Replication
> Configuration also. During peak time or non-peak time, it always use 1 GB
Memory only. Why MSSQL is not taking more than 1 GB, even though server has
got 3 GB and database's max. memory configured as 2 GB.
> In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we
will give /3GB in boot.ini. Similarly anything should be given for SQL 2000
Standard Edition. Right now, boot.ini doesn't contain this option.
> Appreciate your help on this.
> tks in advance,
> vasum
>|||Verify if your application is I/O bound or Memory Bound '
If your cpu utilization is fixed at 100%, then you should worry about
Memory.
Most of the performance problems in databases usually come from locks,
blocking, lot of IO read/writes, etc.
Check http://www.sql-server-performance.com/ for various ways to measure SQL
Server Performance.
Amol.
"vasum" <anonymous@.discussions.microsoft.com> wrote in message
news:E2239F3D-53B5-4DA7-B7AC-280DC8B54ED7@.microsoft.com...
> Hi All,
> Can anybody tell me why Memory is not utilized by MSSQL Service. The
Environment as follows...
> It is an Critical Web based Application with SQL 2000 Standard Edition +
SP3 as backend .
> OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
> MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2
GB". This Server has Replication
> Configuration also. During peak time or non-peak time, it always use 1 GB
Memory only. Why MSSQL is not taking more than 1 GB, even though server has
got 3 GB and database's max. memory configured as 2 GB.
> In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we
will give /3GB in boot.ini. Similarly anything should be given for SQL 2000
Standard Edition. Right now, boot.ini doesn't contain this option.
> Appreciate your help on this.
> tks in advance,
> vasum
>
Showing posts with label memory. Show all posts
Showing posts with label memory. Show all posts
Friday, March 30, 2012
MSSQL 2000 Standard Edition not utilizing Maximum Memory!
Hi All,
Can anybody tell me why Memory is not utilized by MSSQL Service. The Environment as follows...
It is an Critical Web based Application with SQL 2000 Standard Edition + SP3 as backend .
OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2 GB". This Server has Replication
Configuration also. During peak time or non-peak time, it always use 1 GB Memory only. Why MSSQL is not taking more than 1 GB, even though server has got 3 GB and database's max. memory configured as 2 GB.
In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we will give /3GB in boot.ini. Similarly anything should be given for SQL 2000 Standard Edition. Right now, boot.ini doesn't contain this option.
Appreciate your help on this.
tks in advance,
vasum
Are you running other applications on the server besides SQL Server? SQL
Server will manage memory based on amount of free memory available.
Consequently, if other apps running on the same box (e.g. IIS) consume
significant amounts of memory, SQL Server won't acquire additional memory
because this would negatively impact performance.
Hope this helps.
Dan Guzman
SQL Server MVP
"vasum" <anonymous@.discussions.microsoft.com> wrote in message
news:E2239F3D-53B5-4DA7-B7AC-280DC8B54ED7@.microsoft.com...
> Hi All,
> Can anybody tell me why Memory is not utilized by MSSQL Service. The
Environment as follows...
> It is an Critical Web based Application with SQL 2000 Standard Edition +
SP3 as backend .
> OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
> MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2
GB". This Server has Replication
> Configuration also. During peak time or non-peak time, it always use 1 GB
Memory only. Why MSSQL is not taking more than 1 GB, even though server has
got 3 GB and database's max. memory configured as 2 GB.
> In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we
will give /3GB in boot.ini. Similarly anything should be given for SQL 2000
Standard Edition. Right now, boot.ini doesn't contain this option.
> Appreciate your help on this.
> tks in advance,
> vasum
>
|||Verify if your application is I/O bound or Memory Bound ?
If your cpu utilization is fixed at 100%, then you should worry about
Memory.
Most of the performance problems in databases usually come from locks,
blocking, lot of IO read/writes, etc.
Check http://www.sql-server-performance.com/ for various ways to measure SQL
Server Performance.
Amol.
"vasum" <anonymous@.discussions.microsoft.com> wrote in message
news:E2239F3D-53B5-4DA7-B7AC-280DC8B54ED7@.microsoft.com...
> Hi All,
> Can anybody tell me why Memory is not utilized by MSSQL Service. The
Environment as follows...
> It is an Critical Web based Application with SQL 2000 Standard Edition +
SP3 as backend .
> OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
> MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2
GB". This Server has Replication
> Configuration also. During peak time or non-peak time, it always use 1 GB
Memory only. Why MSSQL is not taking more than 1 GB, even though server has
got 3 GB and database's max. memory configured as 2 GB.
> In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we
will give /3GB in boot.ini. Similarly anything should be given for SQL 2000
Standard Edition. Right now, boot.ini doesn't contain this option.
> Appreciate your help on this.
> tks in advance,
> vasum
>
Can anybody tell me why Memory is not utilized by MSSQL Service. The Environment as follows...
It is an Critical Web based Application with SQL 2000 Standard Edition + SP3 as backend .
OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2 GB". This Server has Replication
Configuration also. During peak time or non-peak time, it always use 1 GB Memory only. Why MSSQL is not taking more than 1 GB, even though server has got 3 GB and database's max. memory configured as 2 GB.
In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we will give /3GB in boot.ini. Similarly anything should be given for SQL 2000 Standard Edition. Right now, boot.ini doesn't contain this option.
Appreciate your help on this.
tks in advance,
vasum
Are you running other applications on the server besides SQL Server? SQL
Server will manage memory based on amount of free memory available.
Consequently, if other apps running on the same box (e.g. IIS) consume
significant amounts of memory, SQL Server won't acquire additional memory
because this would negatively impact performance.
Hope this helps.
Dan Guzman
SQL Server MVP
"vasum" <anonymous@.discussions.microsoft.com> wrote in message
news:E2239F3D-53B5-4DA7-B7AC-280DC8B54ED7@.microsoft.com...
> Hi All,
> Can anybody tell me why Memory is not utilized by MSSQL Service. The
Environment as follows...
> It is an Critical Web based Application with SQL 2000 Standard Edition +
SP3 as backend .
> OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
> MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2
GB". This Server has Replication
> Configuration also. During peak time or non-peak time, it always use 1 GB
Memory only. Why MSSQL is not taking more than 1 GB, even though server has
got 3 GB and database's max. memory configured as 2 GB.
> In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we
will give /3GB in boot.ini. Similarly anything should be given for SQL 2000
Standard Edition. Right now, boot.ini doesn't contain this option.
> Appreciate your help on this.
> tks in advance,
> vasum
>
|||Verify if your application is I/O bound or Memory Bound ?
If your cpu utilization is fixed at 100%, then you should worry about
Memory.
Most of the performance problems in databases usually come from locks,
blocking, lot of IO read/writes, etc.
Check http://www.sql-server-performance.com/ for various ways to measure SQL
Server Performance.
Amol.
"vasum" <anonymous@.discussions.microsoft.com> wrote in message
news:E2239F3D-53B5-4DA7-B7AC-280DC8B54ED7@.microsoft.com...
> Hi All,
> Can anybody tell me why Memory is not utilized by MSSQL Service. The
Environment as follows...
> It is an Critical Web based Application with SQL 2000 Standard Edition +
SP3 as backend .
> OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
> MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2
GB". This Server has Replication
> Configuration also. During peak time or non-peak time, it always use 1 GB
Memory only. Why MSSQL is not taking more than 1 GB, even though server has
got 3 GB and database's max. memory configured as 2 GB.
> In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we
will give /3GB in boot.ini. Similarly anything should be given for SQL 2000
Standard Edition. Right now, boot.ini doesn't contain this option.
> Appreciate your help on this.
> tks in advance,
> vasum
>
MSSQL 2000 Standard Edition not utilizing Maximum Memory!
Hi All,
Can anybody tell me why Memory is not utilized by MSSQL Service. The Environ
ment as follows...
It is an Critical Web based Application with SQL 2000 Standard Edition + SP3
as backend .
OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2 GB
". This Server has Replication
Configuration also. During peak time or non-peak time, it always use 1 GB Me
mory only. Why MSSQL is not taking more than 1 GB, even though server has go
t 3 GB and database's max. memory configured as 2 GB.
In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we w
ill give /3GB in boot.ini. Similarly anything should be given for SQL 2000 S
tandard Edition. Right now, boot.ini doesn't contain this option.
Appreciate your help on this.
tks in advance,
vasumAre you running other applications on the server besides SQL Server? SQL
Server will manage memory based on amount of free memory available.
Consequently, if other apps running on the same box (e.g. IIS) consume
significant amounts of memory, SQL Server won't acquire additional memory
because this would negatively impact performance.
Hope this helps.
Dan Guzman
SQL Server MVP
"vasum" <anonymous@.discussions.microsoft.com> wrote in message
news:E2239F3D-53B5-4DA7-B7AC-280DC8B54ED7@.microsoft.com...
> Hi All,
> Can anybody tell me why Memory is not utilized by MSSQL Service. The
Environment as follows...
> It is an Critical Web based Application with SQL 2000 Standard Edition +
SP3 as backend .
> OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
> MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2
GB". This Server has Replication
> Configuration also. During peak time or non-peak time, it always use 1 GB
Memory only. Why MSSQL is not taking more than 1 GB, even though server has
got 3 GB and database's max. memory configured as 2 GB.
> In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we
will give /3GB in boot.ini. Similarly anything should be given for SQL 2000
Standard Edition. Right now, boot.ini doesn't contain this option.
> Appreciate your help on this.
> tks in advance,
> vasum
>|||Verify if your application is I/O bound or Memory Bound '
If your cpu utilization is fixed at 100%, then you should worry about
Memory.
Most of the performance problems in databases usually come from locks,
blocking, lot of IO read/writes, etc.
Check http://www.sql-server-performance.com/ for various ways to measure SQL
Server Performance.
Amol.
"vasum" <anonymous@.discussions.microsoft.com> wrote in message
news:E2239F3D-53B5-4DA7-B7AC-280DC8B54ED7@.microsoft.com...
> Hi All,
> Can anybody tell me why Memory is not utilized by MSSQL Service. The
Environment as follows...
> It is an Critical Web based Application with SQL 2000 Standard Edition +
SP3 as backend .
> OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
> MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2
GB". This Server has Replication
> Configuration also. During peak time or non-peak time, it always use 1 GB
Memory only. Why MSSQL is not taking more than 1 GB, even though server has
got 3 GB and database's max. memory configured as 2 GB.
> In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we
will give /3GB in boot.ini. Similarly anything should be given for SQL 2000
Standard Edition. Right now, boot.ini doesn't contain this option.
> Appreciate your help on this.
> tks in advance,
> vasum
>
Can anybody tell me why Memory is not utilized by MSSQL Service. The Environ
ment as follows...
It is an Critical Web based Application with SQL 2000 Standard Edition + SP3
as backend .
OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2 GB
". This Server has Replication
Configuration also. During peak time or non-peak time, it always use 1 GB Me
mory only. Why MSSQL is not taking more than 1 GB, even though server has go
t 3 GB and database's max. memory configured as 2 GB.
In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we w
ill give /3GB in boot.ini. Similarly anything should be given for SQL 2000 S
tandard Edition. Right now, boot.ini doesn't contain this option.
Appreciate your help on this.
tks in advance,
vasumAre you running other applications on the server besides SQL Server? SQL
Server will manage memory based on amount of free memory available.
Consequently, if other apps running on the same box (e.g. IIS) consume
significant amounts of memory, SQL Server won't acquire additional memory
because this would negatively impact performance.
Hope this helps.
Dan Guzman
SQL Server MVP
"vasum" <anonymous@.discussions.microsoft.com> wrote in message
news:E2239F3D-53B5-4DA7-B7AC-280DC8B54ED7@.microsoft.com...
> Hi All,
> Can anybody tell me why Memory is not utilized by MSSQL Service. The
Environment as follows...
> It is an Critical Web based Application with SQL 2000 Standard Edition +
SP3 as backend .
> OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
> MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2
GB". This Server has Replication
> Configuration also. During peak time or non-peak time, it always use 1 GB
Memory only. Why MSSQL is not taking more than 1 GB, even though server has
got 3 GB and database's max. memory configured as 2 GB.
> In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we
will give /3GB in boot.ini. Similarly anything should be given for SQL 2000
Standard Edition. Right now, boot.ini doesn't contain this option.
> Appreciate your help on this.
> tks in advance,
> vasum
>|||Verify if your application is I/O bound or Memory Bound '
If your cpu utilization is fixed at 100%, then you should worry about
Memory.
Most of the performance problems in databases usually come from locks,
blocking, lot of IO read/writes, etc.
Check http://www.sql-server-performance.com/ for various ways to measure SQL
Server Performance.
Amol.
"vasum" <anonymous@.discussions.microsoft.com> wrote in message
news:E2239F3D-53B5-4DA7-B7AC-280DC8B54ED7@.microsoft.com...
> Hi All,
> Can anybody tell me why Memory is not utilized by MSSQL Service. The
Environment as follows...
> It is an Critical Web based Application with SQL 2000 Standard Edition +
SP3 as backend .
> OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
> MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2
GB". This Server has Replication
> Configuration also. During peak time or non-peak time, it always use 1 GB
Memory only. Why MSSQL is not taking more than 1 GB, even though server has
got 3 GB and database's max. memory configured as 2 GB.
> In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we
will give /3GB in boot.ini. Similarly anything should be given for SQL 2000
Standard Edition. Right now, boot.ini doesn't contain this option.
> Appreciate your help on this.
> tks in advance,
> vasum
>
MSSQL 2000 SP4 Memory Leak
Greetings all!
On one of our intranet SQL servers running under Windows 2000 SP 3,
MSsql 2000 SP4 seems to gradually "eat" away all available memory (with no obvious reason for it) until a certain limit is reached, forcing the server to slow down substantially since the OS has to SWAP continuously.
I would appreciate any suggestions at this point on how to tackle this problem :)
Thank you!
VincentJSThat is the nature of SQL Server. By default, it will continue to claim available memory that is not being used by applications. It's not a memory leak. Most of this memory is used for data cache, which greatly improves performance. You want SQL Server to have plenty of memory. But you can limit this amout if you view the server properties in enterprise manager.
Bill|||if you can afford it, you should have your web and database servers on different machines. I believe you can limit the amount memory sql server consums with the max server memory option in sp_configure but I have never used it
On one of our intranet SQL servers running under Windows 2000 SP 3,
MSsql 2000 SP4 seems to gradually "eat" away all available memory (with no obvious reason for it) until a certain limit is reached, forcing the server to slow down substantially since the OS has to SWAP continuously.
I would appreciate any suggestions at this point on how to tackle this problem :)
Thank you!
VincentJSThat is the nature of SQL Server. By default, it will continue to claim available memory that is not being used by applications. It's not a memory leak. Most of this memory is used for data cache, which greatly improves performance. You want SQL Server to have plenty of memory. But you can limit this amout if you view the server properties in enterprise manager.
Bill|||if you can afford it, you should have your web and database servers on different machines. I believe you can limit the amount memory sql server consums with the max server memory option in sp_configure but I have never used it
MSSQL 2000 memory not being used.
Hi,
I have a quad box with 12 gigs of memory. I can only seem to get up to
6 gigs of memory used. I am having page fault errors and was wondering
why it is page faulting with 6 gigs of memory available. I have tried
using /3GB /PAE and just the /3GB and just the /PAE switches. This is
a Windows 2003 enterprise SP1 server.
If I look at the System Information screen I see that we have total
memory of 12 gigs.
Total Physical Memory 11,519.20 MB
But only 1 gig available for use.
Available Physical Memory 1.07 GB
If I look at the task manager I see I am only using 6 gigs? I am not
the best at math, but things are not adding up here.
Does anybody know the secret sause to getting the server to see the
other 6 gigs?
Much thanks in advance,
John Burris
jburris@.centrisinfo.comjohncburris@.gmail.com wrote:
> Hi,
> I have a quad box with 12 gigs of memory. I can only seem to get up to
> 6 gigs of memory used. I am having page fault errors and was wondering
> why it is page faulting with 6 gigs of memory available. I have tried
> using /3GB /PAE and just the /3GB and just the /PAE switches. This is
> a Windows 2003 enterprise SP1 server.
> If I look at the System Information screen I see that we have total
> memory of 12 gigs.
> Total Physical Memory 11,519.20 MB
> But only 1 gig available for use.
> Available Physical Memory 1.07 GB
> If I look at the task manager I see I am only using 6 gigs? I am not
> the best at math, but things are not adding up here.
> Does anybody know the secret sause to getting the server to see the
> other 6 gigs?
> Much thanks in advance,
> John Burris
> jburris@.centrisinfo.com
>
What SQL service pack are you on? If SP4, have you installed the AWE
hotfix?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
I have a quad box with 12 gigs of memory. I can only seem to get up to
6 gigs of memory used. I am having page fault errors and was wondering
why it is page faulting with 6 gigs of memory available. I have tried
using /3GB /PAE and just the /3GB and just the /PAE switches. This is
a Windows 2003 enterprise SP1 server.
If I look at the System Information screen I see that we have total
memory of 12 gigs.
Total Physical Memory 11,519.20 MB
But only 1 gig available for use.
Available Physical Memory 1.07 GB
If I look at the task manager I see I am only using 6 gigs? I am not
the best at math, but things are not adding up here.
Does anybody know the secret sause to getting the server to see the
other 6 gigs?
Much thanks in advance,
John Burris
jburris@.centrisinfo.comjohncburris@.gmail.com wrote:
> Hi,
> I have a quad box with 12 gigs of memory. I can only seem to get up to
> 6 gigs of memory used. I am having page fault errors and was wondering
> why it is page faulting with 6 gigs of memory available. I have tried
> using /3GB /PAE and just the /3GB and just the /PAE switches. This is
> a Windows 2003 enterprise SP1 server.
> If I look at the System Information screen I see that we have total
> memory of 12 gigs.
> Total Physical Memory 11,519.20 MB
> But only 1 gig available for use.
> Available Physical Memory 1.07 GB
> If I look at the task manager I see I am only using 6 gigs? I am not
> the best at math, but things are not adding up here.
> Does anybody know the secret sause to getting the server to see the
> other 6 gigs?
> Much thanks in advance,
> John Burris
> jburris@.centrisinfo.com
>
What SQL service pack are you on? If SP4, have you installed the AWE
hotfix?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
MSSQL 2000 memory not being used.
Hi,
I have a quad box with 12 gigs of memory. I can only seem to get up to
6 gigs of memory used. I am having page fault errors and was wondering
why it is page faulting with 6 gigs of memory available. I have tried
using /3GB /PAE and just the /3GB and just the /PAE switches. This is
a Windows 2003 enterprise SP1 server.
If I look at the System Information screen I see that we have total
memory of 12 gigs.
Total Physical Memory11,519.20 MB
But only 1 gig available for use.
Available Physical Memory1.07 GB
If I look at the task manager I see I am only using 6 gigs? I am not
the best at math, but things are not adding up here.
Does anybody know the secret sause to getting the server to see the
other 6 gigs?
Much thanks in advance,
John Burris
jburris@.centrisinfo.com
johncburris@.gmail.com wrote:
> Hi,
> I have a quad box with 12 gigs of memory. I can only seem to get up to
> 6 gigs of memory used. I am having page fault errors and was wondering
> why it is page faulting with 6 gigs of memory available. I have tried
> using /3GB /PAE and just the /3GB and just the /PAE switches. This is
> a Windows 2003 enterprise SP1 server.
> If I look at the System Information screen I see that we have total
> memory of 12 gigs.
> Total Physical Memory11,519.20 MB
> But only 1 gig available for use.
> Available Physical Memory1.07 GB
> If I look at the task manager I see I am only using 6 gigs? I am not
> the best at math, but things are not adding up here.
> Does anybody know the secret sause to getting the server to see the
> other 6 gigs?
> Much thanks in advance,
> John Burris
> jburris@.centrisinfo.com
>
What SQL service pack are you on? If SP4, have you installed the AWE
hotfix?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
I have a quad box with 12 gigs of memory. I can only seem to get up to
6 gigs of memory used. I am having page fault errors and was wondering
why it is page faulting with 6 gigs of memory available. I have tried
using /3GB /PAE and just the /3GB and just the /PAE switches. This is
a Windows 2003 enterprise SP1 server.
If I look at the System Information screen I see that we have total
memory of 12 gigs.
Total Physical Memory11,519.20 MB
But only 1 gig available for use.
Available Physical Memory1.07 GB
If I look at the task manager I see I am only using 6 gigs? I am not
the best at math, but things are not adding up here.
Does anybody know the secret sause to getting the server to see the
other 6 gigs?
Much thanks in advance,
John Burris
jburris@.centrisinfo.com
johncburris@.gmail.com wrote:
> Hi,
> I have a quad box with 12 gigs of memory. I can only seem to get up to
> 6 gigs of memory used. I am having page fault errors and was wondering
> why it is page faulting with 6 gigs of memory available. I have tried
> using /3GB /PAE and just the /3GB and just the /PAE switches. This is
> a Windows 2003 enterprise SP1 server.
> If I look at the System Information screen I see that we have total
> memory of 12 gigs.
> Total Physical Memory11,519.20 MB
> But only 1 gig available for use.
> Available Physical Memory1.07 GB
> If I look at the task manager I see I am only using 6 gigs? I am not
> the best at math, but things are not adding up here.
> Does anybody know the secret sause to getting the server to see the
> other 6 gigs?
> Much thanks in advance,
> John Burris
> jburris@.centrisinfo.com
>
What SQL service pack are you on? If SP4, have you installed the AWE
hotfix?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
MSSQL 2000 memory not being used.
Hi,
I have a quad box with 12 gigs of memory. I can only seem to get up to
6 gigs of memory used. I am having page fault errors and was wondering
why it is page faulting with 6 gigs of memory available. I have tried
using /3GB /PAE and just the /3GB and just the /PAE switches. This is
a Windows 2003 enterprise SP1 server.
If I look at the System Information screen I see that we have total
memory of 12 gigs.
Total Physical Memory 11,519.20 MB
But only 1 gig available for use.
Available Physical Memory 1.07 GB
If I look at the task manager I see I am only using 6 gigs? I am not
the best at math, but things are not adding up here.
Does anybody know the secret sause to getting the server to see the
other 6 gigs?
Much thanks in advance,
John Burris
jburris@.centrisinfo.comjohncburris@.gmail.com wrote:
> Hi,
> I have a quad box with 12 gigs of memory. I can only seem to get up to
> 6 gigs of memory used. I am having page fault errors and was wondering
> why it is page faulting with 6 gigs of memory available. I have tried
> using /3GB /PAE and just the /3GB and just the /PAE switches. This is
> a Windows 2003 enterprise SP1 server.
> If I look at the System Information screen I see that we have total
> memory of 12 gigs.
> Total Physical Memory 11,519.20 MB
> But only 1 gig available for use.
> Available Physical Memory 1.07 GB
> If I look at the task manager I see I am only using 6 gigs? I am not
> the best at math, but things are not adding up here.
> Does anybody know the secret sause to getting the server to see the
> other 6 gigs?
> Much thanks in advance,
> John Burris
> jburris@.centrisinfo.com
>
What SQL service pack are you on? If SP4, have you installed the AWE
hotfix?
Tracy McKibben
MCDBA
http://www.realsqlguy.comsql
I have a quad box with 12 gigs of memory. I can only seem to get up to
6 gigs of memory used. I am having page fault errors and was wondering
why it is page faulting with 6 gigs of memory available. I have tried
using /3GB /PAE and just the /3GB and just the /PAE switches. This is
a Windows 2003 enterprise SP1 server.
If I look at the System Information screen I see that we have total
memory of 12 gigs.
Total Physical Memory 11,519.20 MB
But only 1 gig available for use.
Available Physical Memory 1.07 GB
If I look at the task manager I see I am only using 6 gigs? I am not
the best at math, but things are not adding up here.
Does anybody know the secret sause to getting the server to see the
other 6 gigs?
Much thanks in advance,
John Burris
jburris@.centrisinfo.comjohncburris@.gmail.com wrote:
> Hi,
> I have a quad box with 12 gigs of memory. I can only seem to get up to
> 6 gigs of memory used. I am having page fault errors and was wondering
> why it is page faulting with 6 gigs of memory available. I have tried
> using /3GB /PAE and just the /3GB and just the /PAE switches. This is
> a Windows 2003 enterprise SP1 server.
> If I look at the System Information screen I see that we have total
> memory of 12 gigs.
> Total Physical Memory 11,519.20 MB
> But only 1 gig available for use.
> Available Physical Memory 1.07 GB
> If I look at the task manager I see I am only using 6 gigs? I am not
> the best at math, but things are not adding up here.
> Does anybody know the secret sause to getting the server to see the
> other 6 gigs?
> Much thanks in advance,
> John Burris
> jburris@.centrisinfo.com
>
What SQL service pack are you on? If SP4, have you installed the AWE
hotfix?
Tracy McKibben
MCDBA
http://www.realsqlguy.comsql
MSSQL 2000 memory leaks
Hi,
I have one application in two different companies with MSSQL2000 running on Windows2000 Server and Windows2003 Server.
It seems that memory needed for MSSQL2000 as displayed in task manager is increased every day.
Does anybody knows anything regarding memory leaks in MSSQL2000?
How can I find what version of service pack have I installed in a MSSQL2000 server machine?
Regards,
ManolisSQL Server is designed to take up as much memory as it needs. See the article titled "Server Memory Options" in BOL.|||SQL 2000 is sensistive to "Memory Pressure" where other applications request memory from the host operating system. As other apps request more memory, SQL 2000 will free up some of the memory that it is using. In general though, SQL 2000 will tend to "camp" on memory until it percieves pressure from other applications, so it has a reputation as a "memory hog" that I don't feel is justified.
To find your present patch level, execute:SELECT ServerProperty('ProductLevel')-PatP|||Link http://www.sqljunkies.com/Article/7F8518F9-FDAA-4FF3-8FC5-25E8946C8D0C.scuk to investigate & resolve the performance issues.
I have one application in two different companies with MSSQL2000 running on Windows2000 Server and Windows2003 Server.
It seems that memory needed for MSSQL2000 as displayed in task manager is increased every day.
Does anybody knows anything regarding memory leaks in MSSQL2000?
How can I find what version of service pack have I installed in a MSSQL2000 server machine?
Regards,
ManolisSQL Server is designed to take up as much memory as it needs. See the article titled "Server Memory Options" in BOL.|||SQL 2000 is sensistive to "Memory Pressure" where other applications request memory from the host operating system. As other apps request more memory, SQL 2000 will free up some of the memory that it is using. In general though, SQL 2000 will tend to "camp" on memory until it percieves pressure from other applications, so it has a reputation as a "memory hog" that I don't feel is justified.
To find your present patch level, execute:SELECT ServerProperty('ProductLevel')-PatP|||Link http://www.sqljunkies.com/Article/7F8518F9-FDAA-4FF3-8FC5-25E8946C8D0C.scuk to investigate & resolve the performance issues.
Wednesday, March 28, 2012
mssearch.exe easting up memory
Hi ,
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdR
You should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdR
You should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>
mssearch.exe easting up memory
Hi ,
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdRYou should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdRYou should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>
mssearch.exe easting up memory
Hi ,
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdRYou should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>sql
Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it up
for three days, the mssearch.exe job just continues to eat up more memory
until the machine runs out of it needing for the mssearch.exe job to be
ended. Then the mssearch.exe runs again and the cycle continues.
I observered that everytime our .net app touches the sql server database,
that is when this mssearch.exe job stays and start to eat up memory. A
google search reveals that open cursors to the database or a web user
creates a link and does nothing causes this mssearch.exe to go up and grow
and grow.
Is there a fix for this or a workaround?
Thanks,
RdRYou should contact Microsoft Product Support and have them take a look at
MSSearch.
Adrian
"RdR" <rrosario@.datamirror.com> wrote in message
news:GWRde.4408$5u4.15748@.nnrp1.uunet.ca...
> Hi ,
> Running SQL 2000 on Windows Advanced Server 2003 Standard. If I leave it
> up for three days, the mssearch.exe job just continues to eat up more
> memory until the machine runs out of it needing for the mssearch.exe job
> to be ended. Then the mssearch.exe runs again and the cycle continues.
> I observered that everytime our .net app touches the sql server database,
> that is when this mssearch.exe job stays and start to eat up memory. A
> google search reveals that open cursors to the database or a web user
> creates a link and does nothing causes this mssearch.exe to go up and grow
> and grow.
> Is there a fix for this or a workaround?
> Thanks,
> RdR
>sql
Monday, March 26, 2012
mssdmn consuming cpu and memory
I have a sql 2000 SP4 server with two processors that has started to consume
cpu cycles (25% or more on each processor). The proces that is consuming
the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
team services, Lyris list manager, and Macromedia Breeze. Over the weekend
I shutdown all three of these major servers and the cpu continued to be
consumed. I have run Symantec AV and found no viruses. I have restarted
the SQL server several times and the problem continues. I find that if I
work in SQL Enterprise Manager on the sql server the cpu decreases, which I
guess points to a background process.
The server O/S is Windows 2003 server with the latest service packs and
updates applied.
Any suggestions on how to solve the problem would be grealy appreciated.
ThanksThis is SQL FTS - actually MSSearch. You might want to configure it to be
less invasive or perhaps more invasive. Use sp_fulltext_server
'resource_usage' to do this. Configure it for 1 to get less invasive, 5 to
get more invasive.
The question you should be asking yourself is why is it indexing all the
time. What sorts of docs are you storing, and are any of them in Far Eastern
languages or in German. These tend to be resource intensive.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jim Boyer" <boyerj@.wsu.edu> wrote in message
news:92bbe140b9d046ddb63a62ee9eef93a8@.ureader.com...
> I have a sql 2000 SP4 server with two processors that has started to
consume
> cpu cycles (25% or more on each processor). The proces that is consuming
> the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
> team services, Lyris list manager, and Macromedia Breeze. Over the
weekend
> I shutdown all three of these major servers and the cpu continued to be
> consumed. I have run Symantec AV and found no viruses. I have restarted
> the SQL server several times and the problem continues. I find that if I
> work in SQL Enterprise Manager on the sql server the cpu decreases, which
I
> guess points to a background process.
> The server O/S is Windows 2003 server with the latest service packs and
> updates applied.
> Any suggestions on how to solve the problem would be grealy appreciated.
> Thanks
cpu cycles (25% or more on each processor). The proces that is consuming
the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
team services, Lyris list manager, and Macromedia Breeze. Over the weekend
I shutdown all three of these major servers and the cpu continued to be
consumed. I have run Symantec AV and found no viruses. I have restarted
the SQL server several times and the problem continues. I find that if I
work in SQL Enterprise Manager on the sql server the cpu decreases, which I
guess points to a background process.
The server O/S is Windows 2003 server with the latest service packs and
updates applied.
Any suggestions on how to solve the problem would be grealy appreciated.
ThanksThis is SQL FTS - actually MSSearch. You might want to configure it to be
less invasive or perhaps more invasive. Use sp_fulltext_server
'resource_usage' to do this. Configure it for 1 to get less invasive, 5 to
get more invasive.
The question you should be asking yourself is why is it indexing all the
time. What sorts of docs are you storing, and are any of them in Far Eastern
languages or in German. These tend to be resource intensive.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jim Boyer" <boyerj@.wsu.edu> wrote in message
news:92bbe140b9d046ddb63a62ee9eef93a8@.ureader.com...
> I have a sql 2000 SP4 server with two processors that has started to
consume
> cpu cycles (25% or more on each processor). The proces that is consuming
> the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
> team services, Lyris list manager, and Macromedia Breeze. Over the
weekend
> I shutdown all three of these major servers and the cpu continued to be
> consumed. I have run Symantec AV and found no viruses. I have restarted
> the SQL server several times and the problem continues. I find that if I
> work in SQL Enterprise Manager on the sql server the cpu decreases, which
I
> guess points to a background process.
> The server O/S is Windows 2003 server with the latest service packs and
> updates applied.
> Any suggestions on how to solve the problem would be grealy appreciated.
> Thanks
mssdmn consuming cpu and memory
I have a sql 2000 SP4 server with two processors that has started to consume
cpu cycles (25% or more on each processor). The proces that is consuming
the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
team services, Lyris list manager, and Macromedia Breeze. Over the weekend
I shutdown all three of these major servers and the cpu continued to be
consumed. I have run Symantec AV and found no viruses. I have restarted
the SQL server several times and the problem continues. I find that if I
work in SQL Enterprise Manager on the sql server the cpu decreases, which I
guess points to a background process.
The server O/S is Windows 2003 server with the latest service packs and
updates applied.
Any suggestions on how to solve the problem would be grealy appreciated.
Thanks
This is SQL FTS - actually MSSearch. You might want to configure it to be
less invasive or perhaps more invasive. Use sp_fulltext_server
'resource_usage' to do this. Configure it for 1 to get less invasive, 5 to
get more invasive.
The question you should be asking yourself is why is it indexing all the
time. What sorts of docs are you storing, and are any of them in Far Eastern
languages or in German. These tend to be resource intensive.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jim Boyer" <boyerj@.wsu.edu> wrote in message
news:92bbe140b9d046ddb63a62ee9eef93a8@.ureader.com. ..
> I have a sql 2000 SP4 server with two processors that has started to
consume
> cpu cycles (25% or more on each processor). The proces that is consuming
> the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
> team services, Lyris list manager, and Macromedia Breeze. Over the
weekend
> I shutdown all three of these major servers and the cpu continued to be
> consumed. I have run Symantec AV and found no viruses. I have restarted
> the SQL server several times and the problem continues. I find that if I
> work in SQL Enterprise Manager on the sql server the cpu decreases, which
I
> guess points to a background process.
> The server O/S is Windows 2003 server with the latest service packs and
> updates applied.
> Any suggestions on how to solve the problem would be grealy appreciated.
> Thanks
sql
cpu cycles (25% or more on each processor). The proces that is consuming
the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
team services, Lyris list manager, and Macromedia Breeze. Over the weekend
I shutdown all three of these major servers and the cpu continued to be
consumed. I have run Symantec AV and found no viruses. I have restarted
the SQL server several times and the problem continues. I find that if I
work in SQL Enterprise Manager on the sql server the cpu decreases, which I
guess points to a background process.
The server O/S is Windows 2003 server with the latest service packs and
updates applied.
Any suggestions on how to solve the problem would be grealy appreciated.
Thanks
This is SQL FTS - actually MSSearch. You might want to configure it to be
less invasive or perhaps more invasive. Use sp_fulltext_server
'resource_usage' to do this. Configure it for 1 to get less invasive, 5 to
get more invasive.
The question you should be asking yourself is why is it indexing all the
time. What sorts of docs are you storing, and are any of them in Far Eastern
languages or in German. These tend to be resource intensive.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jim Boyer" <boyerj@.wsu.edu> wrote in message
news:92bbe140b9d046ddb63a62ee9eef93a8@.ureader.com. ..
> I have a sql 2000 SP4 server with two processors that has started to
consume
> cpu cycles (25% or more on each processor). The proces that is consuming
> the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
> team services, Lyris list manager, and Macromedia Breeze. Over the
weekend
> I shutdown all three of these major servers and the cpu continued to be
> consumed. I have run Symantec AV and found no viruses. I have restarted
> the SQL server several times and the problem continues. I find that if I
> work in SQL Enterprise Manager on the sql server the cpu decreases, which
I
> guess points to a background process.
> The server O/S is Windows 2003 server with the latest service packs and
> updates applied.
> Any suggestions on how to solve the problem would be grealy appreciated.
> Thanks
sql
mssdmn consuming cpu and memory
I have a sql 2000 SP4 server with two processors that has started to consume
cpu cycles (25% or more on each processor). The proces that is consuming
the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
team services, Lyris list manager, and Macromedia Breeze. Over the weekend
I shutdown all three of these major servers and the cpu continued to be
consumed. I have run Symantec AV and found no viruses. I have restarted
the SQL server several times and the problem continues. I find that if I
work in SQL Enterprise Manager on the sql server the cpu decreases, which I
guess points to a background process.
The server O/S is Windows 2003 server with the latest service packs and
updates applied.
Any suggestions on how to solve the problem would be grealy appreciated.
ThanksThis is SQL FTS - actually MSSearch. You might want to configure it to be
less invasive or perhaps more invasive. Use sp_fulltext_server
'resource_usage' to do this. Configure it for 1 to get less invasive, 5 to
get more invasive.
The question you should be asking yourself is why is it indexing all the
time. What sorts of docs are you storing, and are any of them in Far Eastern
languages or in German. These tend to be resource intensive.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jim Boyer" <boyerj@.wsu.edu> wrote in message
news:92bbe140b9d046ddb63a62ee9eef93a8@.ur
eader.com...
> I have a sql 2000 SP4 server with two processors that has started to
consume
> cpu cycles (25% or more on each processor). The proces that is consuming
> the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
> team services, Lyris list manager, and Macromedia Breeze. Over the
weekend
> I shutdown all three of these major servers and the cpu continued to be
> consumed. I have run Symantec AV and found no viruses. I have restarted
> the SQL server several times and the problem continues. I find that if I
> work in SQL Enterprise Manager on the sql server the cpu decreases, which
I
> guess points to a background process.
> The server O/S is Windows 2003 server with the latest service packs and
> updates applied.
> Any suggestions on how to solve the problem would be grealy appreciated.
> Thanks
cpu cycles (25% or more on each processor). The proces that is consuming
the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
team services, Lyris list manager, and Macromedia Breeze. Over the weekend
I shutdown all three of these major servers and the cpu continued to be
consumed. I have run Symantec AV and found no viruses. I have restarted
the SQL server several times and the problem continues. I find that if I
work in SQL Enterprise Manager on the sql server the cpu decreases, which I
guess points to a background process.
The server O/S is Windows 2003 server with the latest service packs and
updates applied.
Any suggestions on how to solve the problem would be grealy appreciated.
ThanksThis is SQL FTS - actually MSSearch. You might want to configure it to be
less invasive or perhaps more invasive. Use sp_fulltext_server
'resource_usage' to do this. Configure it for 1 to get less invasive, 5 to
get more invasive.
The question you should be asking yourself is why is it indexing all the
time. What sorts of docs are you storing, and are any of them in Far Eastern
languages or in German. These tend to be resource intensive.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jim Boyer" <boyerj@.wsu.edu> wrote in message
news:92bbe140b9d046ddb63a62ee9eef93a8@.ur
eader.com...
> I have a sql 2000 SP4 server with two processors that has started to
consume
> cpu cycles (25% or more on each processor). The proces that is consuming
> the cpu is mssdmn. The server hosts three major databases; MS Sharepoint
> team services, Lyris list manager, and Macromedia Breeze. Over the
weekend
> I shutdown all three of these major servers and the cpu continued to be
> consumed. I have run Symantec AV and found no viruses. I have restarted
> the SQL server several times and the problem continues. I find that if I
> work in SQL Enterprise Manager on the sql server the cpu decreases, which
I
> guess points to a background process.
> The server O/S is Windows 2003 server with the latest service packs and
> updates applied.
> Any suggestions on how to solve the problem would be grealy appreciated.
> Thanks
Wednesday, March 21, 2012
msmdsrv.exe taking substantial memory
Wondering if you have this problem or not, it seems SQL 2005 AS msmdsrv.exe taking lots of memory, I looked at 64 bit server, and 32 bit server, compare with other SQL server services, msmdsrv.exe runs about 500,000 - 600,000 K on 64 bit server, vs. 87,000 k for sqlserver.exe, and 67,000 k for reportserver.exe, and connect to AS through Management Studio also takes long time. I have default setting for all services.
I have one cube database which is about 240 MB in size and do full process, we have all SQL 2005 services in one 64 bit box with 8 way processor and at least 4 gz memory.
I am getting a little frustrated by this, any pointer?
Thanks
Not to become an emotional help, just to clarify the situation 
Analysis Server is completely different from SQL server. It is not relational but what is called OLAP and DM server. It works and implements completely different set of data structures. It is queried using different query language- MDX.
One example: Nature of relational databases is such that because of the frequent updates you often you cant caches of your data in memory. For Analysis Server the situation is completely different. The more things it can put in memory, the better- the faster it can answer user queries.
In many enterprise applicaiton it is recommended you place you Analysis Server on different machine from your relation database.
I understand that you have a small cube, but having all the servers running on your machine, fighting for resources can be cause you see for some of the slowdowns.
HTH
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Hi Edward,
Thank you so much for your comments. For right now, we have to put everything in one server becuase of licenses issue. So if I put all sql server services in one server, do you recommend set up memory limitation on Analysis Service can use instead of default setting?
I remember default setting is 75 or 80% of all avaliable memory, should I change that to lower percentage,so it will not affect other running servies?
Thanks
|||See whether this KBA http://support.microsoft.com/kb/922852 & http://support.microsoft.com/kb/900390 are any help here.|||If SSAS is only using 500-600 Mb on a 4Gb box, it does not sound like there is too much of an issue. I would be more worried about why the sqlserver is so low.
There are a couple of perfmon counters that you can check under SQL Server: Memory Manager object called "Target Server Memory" and "Total Server Memory". The Target amount is what the server "wants" and the Total is what it is currently using. Ideally these should be the same value, but if your system is under memory pressure your Total will be lower than your target.
|||Thanks all for your very helpfull advices. This is the test I did againist our test server, which of course not much usage. But I am a little concern about fighting resources among Database engine, RS, AS and SSIS. Have you all setup memory limit for your AS other than default setting?
Thanks
msmdsrv.exe taking substantial memory
Wondering if you have this problem or not, it seems SQL 2005 AS msmdsrv.exe taking lots of memory, I looked at 64 bit server, and 32 bit server, compare with other SQL server services, msmdsrv.exe runs about 500,000 - 600,000 K on 64 bit server, vs. 87,000 k for sqlserver.exe, and 67,000 k for reportserver.exe, and connect to AS through Management Studio also takes long time. I have default setting for all services.
I have one cube database which is about 240 MB in size and do full process, we have all SQL 2005 services in one 64 bit box with 8 way processor and at least 4 gz memory.
I am getting a little frustrated by this, any pointer?
Thanks
Not to become an emotional help, just to clarify the situation
Analysis Server is completely different from SQL server. It is not relational but what is called OLAP and DM server. It works and implements completely different set of data structures. It is queried using different query language- MDX.
One example: Nature of relational databases is such that because of the frequent updates you often you cant caches of your data in memory. For Analysis Server the situation is completely different. The more things it can put in memory, the better- the faster it can answer user queries.
In many enterprise applicaiton it is recommended you place you Analysis Server on different machine from your relation database.
I understand that you have a small cube, but having all the servers running on your machine, fighting for resources can be cause you see for some of the slowdowns.
HTH
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Hi Edward,
Thank you so much for your comments. For right now, we have to put everything in one server becuase of licenses issue. So if I put all sql server services in one server, do you recommend set up memory limitation on Analysis Service can use instead of default setting?
I remember default setting is 75 or 80% of all avaliable memory, should I change that to lower percentage,so it will not affect other running servies?
Thanks
|||See whether this KBA http://support.microsoft.com/kb/922852 & http://support.microsoft.com/kb/900390 are any help here.|||If SSAS is only using 500-600 Mb on a 4Gb box, it does not sound like there is too much of an issue. I would be more worried about why the sqlserver is so low.
There are a couple of perfmon counters that you can check under SQL Server: Memory Manager object called "Target Server Memory" and "Total Server Memory". The Target amount is what the server "wants" and the Total is what it is currently using. Ideally these should be the same value, but if your system is under memory pressure your Total will be lower than your target.
|||Thanks all for your very helpfull advices. This is the test I did againist our test server, which of course not much usage. But I am a little concern about fighting resources among Database engine, RS, AS and SSIS. Have you all setup memory limit for your AS other than default setting?
Thanks
Friday, March 9, 2012
msftesql memory usage
We have been testing SQL 2005 full-text search, and noticed that the
msftesql process isn't using much memory (only around 6 megs), when the
single table we're indexing has about 3.8 millions rows, with 4 varchar
columns indexed ranging between varchar(255) and varchar(750). Is this
normal, i.e., is the full text search service using sqlservr.exe's memory?
Our server is a 2-way 2.0 GHZ opteron with 4GB RAM using WIN2K server with
/3GB switch.
We've looked around for a way to increase the memory available to msfteql
without success.
Thanks,
John
John,
Yes, its normal, but you can control the "aggressiveness" of the SQL Server
2005 MSFTESQL service via several advance sp_configure settings. Run the
below SQL code and review the new fulltext search options:
use master
go
sp_configure 'show advanced options', 1
reconfigure with override
go
sp_configure
There should be several new option to allow you to control the memory
allocation of the MSFTESQL service. No, the MSFTESQL uses its own memory
separate from the SQL Server memory.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"John" <jglass67@.msn.com> wrote in message
news:uocvvK2lFHA.764@.TK2MSFTNGP14.phx.gbl...
> We have been testing SQL 2005 full-text search, and noticed that the
> msftesql process isn't using much memory (only around 6 megs), when the
> single table we're indexing has about 3.8 millions rows, with 4 varchar
> columns indexed ranging between varchar(255) and varchar(750). Is this
> normal, i.e., is the full text search service using sqlservr.exe's memory?
> Our server is a 2-way 2.0 GHZ opteron with 4GB RAM using WIN2K server with
> /3GB switch.
> We've looked around for a way to increase the memory available to msfteql
> without success.
> Thanks,
> John
>
msftesql process isn't using much memory (only around 6 megs), when the
single table we're indexing has about 3.8 millions rows, with 4 varchar
columns indexed ranging between varchar(255) and varchar(750). Is this
normal, i.e., is the full text search service using sqlservr.exe's memory?
Our server is a 2-way 2.0 GHZ opteron with 4GB RAM using WIN2K server with
/3GB switch.
We've looked around for a way to increase the memory available to msfteql
without success.
Thanks,
John
John,
Yes, its normal, but you can control the "aggressiveness" of the SQL Server
2005 MSFTESQL service via several advance sp_configure settings. Run the
below SQL code and review the new fulltext search options:
use master
go
sp_configure 'show advanced options', 1
reconfigure with override
go
sp_configure
There should be several new option to allow you to control the memory
allocation of the MSFTESQL service. No, the MSFTESQL uses its own memory
separate from the SQL Server memory.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"John" <jglass67@.msn.com> wrote in message
news:uocvvK2lFHA.764@.TK2MSFTNGP14.phx.gbl...
> We have been testing SQL 2005 full-text search, and noticed that the
> msftesql process isn't using much memory (only around 6 megs), when the
> single table we're indexing has about 3.8 millions rows, with 4 varchar
> columns indexed ranging between varchar(255) and varchar(750). Is this
> normal, i.e., is the full text search service using sqlservr.exe's memory?
> Our server is a 2-way 2.0 GHZ opteron with 4GB RAM using WIN2K server with
> /3GB switch.
> We've looked around for a way to increase the memory available to msfteql
> without success.
> Thanks,
> John
>
MsDtsSrvr.exe memory leak?
In our current environment, we are running about 10,000 packages per day on a given 64 bit SSIS server.
The MSDtsSrvr.exe (SSIS service) process' memory working set size continues to grow until it consumes the memory on the machine.
Some of the packages do use a custom component. Could this be responsible for leaking memory in the MSDtsSrvr.exe process? Has a memory leak been confirmed in this process for the "first-party" components anyway?
More information about the possible memory leak.
The packages are run in in a CLR process with calls Package.Execute(), rather than being executed via dtexec or dtexecui or the designer. The reason for this approach is the ability to write a custom event handler with access to the package pointer, which other log handlers cannot do. The process runs Package.Execute() and exits, so there are 10,000 short-lived processes, each of which call Package.Execute() once.
To be slightly more specific about what the packages are doing, each of the 10,000 packages generally correlates to 1 source file, loading in dummy (aka inferred) dimension records, and then populating a fact table via a surrogate key pipeline.
Subscribe to:
Posts (Atom)