Showing posts with label log. Show all posts
Showing posts with label log. Show all posts

Friday, March 23, 2012

Performance Counter Problems

Hi,
We are running SQL Server 2000 SP3a on Windows 2003 Server.
I use the Performance Log to capture some performance counters and saved
as text file. When I opened the captured file, I discovered that the
SQLServer Counters are not recording anything (\SQLServer:Memory
manager, \SQLServer:Buffer manager, etc ) But other counters like
\Physical Disk: %Disk Time, \Processor:%Processor Time are recording
values.
I will appreciate your help.
Thanks
Egbon
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!"Egbon V." <vnjowusi@.gosps.com> wrote in message
news:eXySJtO7DHA.2656@.TK2MSFTNGP11.phx.gbl...
> We are running SQL Server 2000 SP3a on Windows 2003 Server.
> I use the Performance Log to capture some performance counters and saved
> as text file. When I opened the captured file, I discovered that the
> SQLServer Counters are not recording anything (\SQLServer:Memory
> manager, \SQLServer:Buffer manager, etc ) But other counters like
> \Physical Disk: %Disk Time, \Processor:%Processor Time are recording
> values.
This article looks promising, it may be a WMI registration issue:
http://support.microsoft.com/defaul...0&Product=sql2k
Steve|||Steve,
Thanks a lot!
Egbon
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!sql

Performance Counter Problems

Hi,
We are running SQL Server 2000 SP3a on Windows 2003 Server.
I use the Performance Log to capture some performance counters and saved
as text file. When I opened the captured file, I discovered that the
SQLServer Counters are not recording anything (\SQLServer:Memory
manager, \SQLServer:Buffer manager, etc ) But other counters like
\Physical Disk: %Disk Time, \Processor:%Processor Time are recording
values.
I will appreciate your help.
Thanks
Egbon
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!"Egbon V." <vnjowusi@.gosps.com> wrote in message
news:eXySJtO7DHA.2656@.TK2MSFTNGP11.phx.gbl...
> We are running SQL Server 2000 SP3a on Windows 2003 Server.
> I use the Performance Log to capture some performance counters and saved
> as text file. When I opened the captured file, I discovered that the
> SQLServer Counters are not recording anything (\SQLServer:Memory
> manager, \SQLServer:Buffer manager, etc ) But other counters like
> \Physical Disk: %Disk Time, \Processor:%Processor Time are recording
> values.
This article looks promising, it may be a WMI registration issue:
http://support.microsoft.com/default.aspx?scid=kb;en-us;827260&Product=sql2k
Steve

Tuesday, March 20, 2012

PErformance and SQL Server Error Log

I am using SQL 2K.
Size of the SQL Server error log file will degrade the performance of SQL
Server.
I am talking about log file which I cleared using SP_CYCLE_ERRORLOG.
Thanks,
JJ
Recycle more often then. How did you determine that it "degraded"
performance?
bert
|||Sorry,
It was my quetion as whether it will degrade the performance or not?
Thanks,
JJ
"bert" <bertcord@.gmail.com> wrote in message
news:1107297013.482698.267950@.l41g2000cwc.googlegr oups.com...
> Recycle more often then. How did you determine that it "degraded"
> performance?
> bert
>
|||Hi
Not that I have ever found. Output to the log file is appended and is not
read by SQL Server itself.
The bigger issue is how do you view it. A 10Mb log file does take a while to
open in EM (or notepad).
We cycle our error logs on our 400 servers every night. This helps us to
keep the Error log entries by day.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Smith" <JJSmith45@.hotmail.com> wrote in message
news:#bkfy5KCFHA.3524@.TK2MSFTNGP15.phx.gbl...
> Sorry,
> It was my quetion as whether it will degrade the performance or not?
> Thanks,
> JJ
> "bert" <bertcord@.gmail.com> wrote in message
> news:1107297013.482698.267950@.l41g2000cwc.googlegr oups.com...
>
|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.
|||Another helpful hint: either by registry key or by using SQLEM, you can
modify the properties of the SQL Error logs to increase the number retained.
We set ours to 32 and recycle at 11:59 PM every night.
Another thing to consider, most of what is output to the SQL Server Error
logs also ends up in the server's Application Event log; so, you might want
to increase the size of that log too.
Finally, if you have your security settings to Audit all logins, both the
SQL Server Error logs and the system's Application Event logs can be
enourmous. We currently only set for failed login attempts.
Sincerely,
Anthony Thomas

"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:EthMd.26166$ZD1.5393@.twister.nyroc.rr.com...
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.

PErformance and SQL Server Error Log

I am using SQL 2K.
Size of the SQL Server error log file will degrade the performance of SQL
Server.
I am talking about log file which I cleared using SP_CYCLE_ERRORLOG.
Thanks,
JJRecycle more often then. How did you determine that it "degraded"
performance?
bert|||Sorry,
It was my quetion as whether it will degrade the performance or not?
Thanks,
JJ
"bert" <bertcord@.gmail.com> wrote in message
news:1107297013.482698.267950@.l41g2000cwc.googlegroups.com...
> Recycle more often then. How did you determine that it "degraded"
> performance?
> bert
>|||Hi
Not that I have ever found. Output to the log file is appended and is not
read by SQL Server itself.
The bigger issue is how do you view it. A 10Mb log file does take a while to
open in EM (or notepad).
We cycle our error logs on our 400 servers every night. This helps us to
keep the Error log entries by day.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Smith" <JJSmith45@.hotmail.com> wrote in message
news:#bkfy5KCFHA.3524@.TK2MSFTNGP15.phx.gbl...
> Sorry,
> It was my quetion as whether it will degrade the performance or not?
> Thanks,
> JJ
> "bert" <bertcord@.gmail.com> wrote in message
> news:1107297013.482698.267950@.l41g2000cwc.googlegroups.com...
> > Recycle more often then. How did you determine that it "degraded"
> > performance?
> >
> > bert
> >
>|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.|||Another helpful hint: either by registry key or by using SQLEM, you can
modify the properties of the SQL Error logs to increase the number retained.
We set ours to 32 and recycle at 11:59 PM every night.
Another thing to consider, most of what is output to the SQL Server Error
logs also ends up in the server's Application Event log; so, you might want
to increase the size of that log too.
Finally, if you have your security settings to Audit all logins, both the
SQL Server Error logs and the system's Application Event logs can be
enourmous. We currently only set for failed login attempts.
Sincerely,
Anthony Thomas
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:EthMd.26166$ZD1.5393@.twister.nyroc.rr.com...
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.

PErformance and SQL Server Error Log

I am using SQL 2K.
Size of the SQL Server error log file will degrade the performance of SQL
Server.
I am talking about log file which I cleared using SP_CYCLE_ERRORLOG.
Thanks,
JJRecycle more often then. How did you determine that it "degraded"
performance?
bert|||Sorry,
It was my quetion as whether it will degrade the performance or not?
Thanks,
JJ
"bert" <bertcord@.gmail.com> wrote in message
news:1107297013.482698.267950@.l41g2000cwc.googlegroups.com...
> Recycle more often then. How did you determine that it "degraded"
> performance?
> bert
>|||Hi
Not that I have ever found. Output to the log file is appended and is not
read by SQL Server itself.
The bigger issue is how do you view it. A 10Mb log file does take a while to
open in EM (or notepad).
We cycle our error logs on our 400 servers every night. This helps us to
keep the Error log entries by day.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Smith" <JJSmith45@.hotmail.com> wrote in message
news:#bkfy5KCFHA.3524@.TK2MSFTNGP15.phx.gbl...
> Sorry,
> It was my quetion as whether it will degrade the performance or not?
> Thanks,
> JJ
> "bert" <bertcord@.gmail.com> wrote in message
> news:1107297013.482698.267950@.l41g2000cwc.googlegroups.com...
>|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.|||Another helpful hint: either by registry key or by using SQLEM, you can
modify the properties of the SQL Error logs to increase the number retained.
We set ours to 32 and recycle at 11:59 PM every night.
Another thing to consider, most of what is output to the SQL Server Error
logs also ends up in the server's Application Event log; so, you might want
to increase the size of that log too.
Finally, if you have your security settings to Audit all logins, both the
SQL Server Error logs and the system's Application Event logs can be
enourmous. We currently only set for failed login attempts.
Sincerely,
Anthony Thomas
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:EthMd.26166$ZD1.5393@.twister.nyroc.rr.com...
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.

Friday, March 9, 2012

performance

I am running sp_who2
I discover some task are occpied the CPU
one is Log Writer CPUTIme 36906
One is checkpoint sleep CPUTIme 26422
how can i stop it?
Those are SQL Server system processes - you don't want to
stop them from doing what they need to do. CPU time is
cumulative for the processes.
-Sue
On Wed, 30 Mar 2005 16:11:31 +0800, "Test" <TEst@.test.com>
wrote:

>I am running sp_who2
>I discover some task are occpied the CPU
>one is Log Writer CPUTIme 36906
>One is checkpoint sleep CPUTIme 26422
>how can i stop it?
>

performance

I am running sp_who2
I discover some task are occpied the CPU
one is Log Writer CPUTIme 36906
One is checkpoint sleep CPUTIme 26422
how can i stop it?Those are SQL Server system processes - you don't want to
stop them from doing what they need to do. CPU time is
cumulative for the processes.
-Sue
On Wed, 30 Mar 2005 16:11:31 +0800, "Test" <TEst@.test.com>
wrote:

>I am running sp_who2
>I discover some task are occpied the CPU
>one is Log Writer CPUTIme 36906
>One is checkpoint sleep CPUTIme 26422
>how can i stop it?
>

Wednesday, March 7, 2012

performance

I am running sp_who2
I discover some task are occpied the CPU
one is Log Writer CPUTIme 36906
One is checkpoint sleep CPUTIme 26422
how can i stop it?Those are SQL Server system processes - you don't want to
stop them from doing what they need to do. CPU time is
cumulative for the processes.
-Sue
On Wed, 30 Mar 2005 16:11:31 +0800, "Test" <TEst@.test.com>
wrote:
>I am running sp_who2
>I discover some task are occpied the CPU
>one is Log Writer CPUTIme 36906
>One is checkpoint sleep CPUTIme 26422
>how can i stop it?
>

Saturday, February 25, 2012

Perfmon SQL Server counters not appearing in list for saveds counter log.

Hi,
I set up a counter log to record SQL data in perfmon. This included a
few O/S counters and
SQL Server:Buffer Manager/Buffer Cache Hit Ratio
SQL Server:General Statistics/User Connections
I am now trying to look at the data through Perf Mon on the same
machine. However I can only add O/S counters to the view. The SQL
Server counters don't appear in the list.
Any ideas?
Cheers,
JamesHi James
"JimLad" wrote:
> Hi,
> I set up a counter log to record SQL data in perfmon. This included a
> few O/S counters and
> SQL Server:Buffer Manager/Buffer Cache Hit Ratio
> SQL Server:General Statistics/User Connections
> I am now trying to look at the data through Perf Mon on the same
> machine. However I can only add O/S counters to the view. The SQL
> Server counters don't appear in the list.
> Any ideas?
> Cheers,
> James
I assume this is opening the log file? In which case I suspect the counters
weren't collected. Are the counters available if you try to add them to the
system monitor?
If you are on a 64 bit server are you running the correct version of perfmon?
John|||On Jul 9, 1:28 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi James
>
>
> "JimLad" wrote:
> > Hi,
> > I set up a counter log to record SQL data in perfmon. This included a
> > few O/S counters and
> > SQL Server:Buffer Manager/Buffer Cache Hit Ratio
> > SQL Server:General Statistics/User Connections
> > I am now trying to look at the data through Perf Mon on the same
> > machine. However I can only add O/S counters to the view. The SQL
> > Server counters don't appear in the list.
> > Any ideas?
> > Cheers,
> > James
> I assume this is opening the log file? In which case I suspect the counters
> weren't collected. Are the counters available if you try to add them to the
> system monitor?
> If you are on a 64 bit server are you running the correct version of perfmon?
> John- Hide quoted text -
> - Show quoted text -
Hi John,
Yes, I am opening the log file. And yes they are available in Sys Mon.
It's a virtualised 32bit server I believe (Intel Xeon 3.2GHz).
As for perfmon version I'm just using the one in Administrative Tools.
So, I definitely put the counters in the log. Why haven't they been
recorded? I notice there is something about objects as well. I only
put the individual counters in. Do I need to put the whole SQL Server
object in?
Cheers,
James|||Hi James
"JimLad" wrote:
> On Jul 9, 1:28 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > Hi James
> >
> >
> >
> >
> >
> > "JimLad" wrote:
> > > Hi,
> >
> > > I set up a counter log to record SQL data in perfmon. This included a
> > > few O/S counters and
> >
> > > SQL Server:Buffer Manager/Buffer Cache Hit Ratio
> > > SQL Server:General Statistics/User Connections
> >
> > > I am now trying to look at the data through Perf Mon on the same
> > > machine. However I can only add O/S counters to the view. The SQL
> > > Server counters don't appear in the list.
> >
> > > Any ideas?
> >
> > > Cheers,
> >
> > > James
> >
> > I assume this is opening the log file? In which case I suspect the counters
> > weren't collected. Are the counters available if you try to add them to the
> > system monitor?
> > If you are on a 64 bit server are you running the correct version of perfmon?
> >
> > John- Hide quoted text -
> >
> > - Show quoted text -
> Hi John,
> Yes, I am opening the log file. And yes they are available in Sys Mon.
> It's a virtualised 32bit server I believe (Intel Xeon 3.2GHz).
> As for perfmon version I'm just using the one in Administrative Tools.
> So, I definitely put the counters in the log. Why haven't they been
> recorded? I notice there is something about objects as well. I only
> put the individual counters in. Do I need to put the whole SQL Server
> object in?
> Cheers,
> James
If they are in the file it should be ok or the file is somehow corrupt. You
should not need to include anything other than the specific counters. Try
doing a new one with just one of the counters and see what happens.
You could try importing the file into SQL 2005 profiler it you have a
corresponding profile.
John|||On Jul 9, 12:52 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi James
>
>
> "JimLad" wrote:
> > On Jul 9, 1:28 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > > Hi James
> > > "JimLad" wrote:
> > > > Hi,
> > > > I set up a counter log to record SQL data in perfmon. This included a
> > > > few O/S counters and
> > > > SQL Server:Buffer Manager/Buffer Cache Hit Ratio
> > > > SQL Server:General Statistics/User Connections
> > > > I am now trying to look at the data through Perf Mon on the same
> > > > machine. However I can only add O/S counters to the view. The SQL
> > > > Server counters don't appear in the list.
> > > > Any ideas?
> > > > Cheers,
> > > > James
> > > I assume this is opening the log file? In which case I suspect the counters
> > > weren't collected. Are the counters available if you try to add them to the
> > > system monitor?
> > > If you are on a 64 bit server are you running the correct version of perfmon?
> > > John- Hide quoted text -
> > > - Show quoted text -
> > Hi John,
> > Yes, I am opening the log file. And yes they are available in Sys Mon.
> > It's a virtualised 32bit server I believe (Intel Xeon 3.2GHz).
> > As for perfmon version I'm just using the one in Administrative Tools.
> > So, I definitely put the counters in the log. Why haven't they been
> > recorded? I notice there is something about objects as well. I only
> > put the individual counters in. Do I need to put the whole SQL Server
> > object in?
> > Cheers,
> > James
> If they are in the file it should be ok or the file is somehow corrupt. You
> should not need to include anything other than the specific counters. Try
> doing a new one with just one of the counters and see what happens.
> You could try importing the file into SQL 2005 profiler it you have a
> corresponding profile.
> John- Hide quoted text -
> - Show quoted text -
James,
This just happened to me last week. In my case, I could see the all
counters except for SQL Server counters (Availible memory, buffer
etc). It was a permissions issue. You can "run as" and when I changed
to administrator of the box who has sa access, they appeared.
Hope this helps.
Kristina

Perfmon SQL Server counters not appearing in list for saveds coun

Hi James
"JimLad" wrote:

> Hi,
> I set up a counter log to record SQL data in perfmon. This included a
> few O/S counters and
> SQL Server:Buffer Manager/Buffer Cache Hit Ratio
> SQL Server:General Statistics/User Connections
> I am now trying to look at the data through Perf Mon on the same
> machine. However I can only add O/S counters to the view. The SQL
> Server counters don't appear in the list.
> Any ideas?
> Cheers,
> James
I assume this is opening the log file? In which case I suspect the counters
weren't collected. Are the counters available if you try to add them to the
system monitor?
If you are on a 64 bit server are you running the correct version of perfmon?
John
Hi James
"JimLad" wrote:

> On Jul 9, 1:28 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi John,
> Yes, I am opening the log file. And yes they are available in Sys Mon.
> It's a virtualised 32bit server I believe (Intel Xeon 3.2GHz).
> As for perfmon version I'm just using the one in Administrative Tools.
> So, I definitely put the counters in the log. Why haven't they been
> recorded? I notice there is something about objects as well. I only
> put the individual counters in. Do I need to put the whole SQL Server
> object in?
> Cheers,
> James
If they are in the file it should be ok or the file is somehow corrupt. You
should not need to include anything other than the specific counters. Try
doing a new one with just one of the counters and see what happens.
You could try importing the file into SQL 2005 profiler it you have a
corresponding profile.
John
|||On Jul 9, 12:52 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi James
>
>
> "JimLad" wrote:
>
>
>
>
>
>
>
>
> If they are in the file it should be ok or the file is somehow corrupt. You
> should not need to include anything other than the specific counters. Try
> doing a new one with just one of the counters and see what happens.
> You could try importing the file into SQL 2005 profiler it you have a
> corresponding profile.
> John- Hide quoted text -
> - Show quoted text -
James,
This just happened to me last week. In my case, I could see the all
counters except for SQL Server counters (Availible memory, buffer
etc). It was a permissions issue. You can "run as" and when I changed
to administrator of the box who has sa access, they appeared.
Hope this helps.
Kristina