Showing posts with label supporting. Show all posts
Showing posts with label supporting. Show all posts

Monday, March 19, 2012

Monitoring SQL Server Error logs

Hi,
We have a large number of SQL servers that we are supporting. Monitoring the
error logs for new errors is really a big task as we have to manually check
these error logs. I was hoping that some of you might have automated this
process and filtered out the unwanted messages from the error log and mail
only the genuine ones. If anyone can share it with the group, it will be
terrific as you will be giving us extra minutes of sleep each night.
Thanking you in anticipation,
Yoga
You'll need to define for yourself what a wanted message is.
One option is to use finstr to search for whatever it is you
are looking for - you can find examples in these articles:
http://support.microsoft.com/?id=115519
http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=40
You can automate those in a job.
Another consideration is how you set up and use your alerts
and monitoring on the servers. For most things you can be
notified if monitoring is set up correctly.
Of course there are a lot of third party solutions but I
take it your looking for scripts and built in solutions.
-Sue
On Mon, 26 Mar 2007 11:53:38 -0700, "Yoganarasimha Prasad"
<yogakiran@.gmail.com> wrote:

>Hi,
>We have a large number of SQL servers that we are supporting. Monitoring the
>error logs for new errors is really a big task as we have to manually check
>these error logs. I was hoping that some of you might have automated this
>process and filtered out the unwanted messages from the error log and mail
>only the genuine ones. If anyone can share it with the group, it will be
>terrific as you will be giving us extra minutes of sleep each night.
>Thanking you in anticipation,
>Yoga
>

Monitoring SQL Server Error logs

Hi,
We have a large number of SQL servers that we are supporting. Monitoring the
error logs for new errors is really a big task as we have to manually check
these error logs. I was hoping that some of you might have automated this
process and filtered out the unwanted messages from the error log and mail
only the genuine ones. If anyone can share it with the group, it will be
terrific as you will be giving us extra minutes of sleep each night.
Thanking you in anticipation,
YogaYou'll need to define for yourself what a wanted message is.
One option is to use finstr to search for whatever it is you
are looking for - you can find examples in these articles:
http://support.microsoft.com/?id=115519
http://www.sqlservercentral.com/scr...asp?scriptid=40
You can automate those in a job.
Another consideration is how you set up and use your alerts
and monitoring on the servers. For most things you can be
notified if monitoring is set up correctly.
Of course there are a lot of third party solutions but I
take it your looking for scripts and built in solutions.
-Sue
On Mon, 26 Mar 2007 11:53:38 -0700, "Yoganarasimha Prasad"
<yogakiran@.gmail.com> wrote:

>Hi,
>We have a large number of SQL servers that we are supporting. Monitoring th
e
>error logs for new errors is really a big task as we have to manually check
>these error logs. I was hoping that some of you might have automated this
>process and filtered out the unwanted messages from the error log and mail
>only the genuine ones. If anyone can share it with the group, it will be
>terrific as you will be giving us extra minutes of sleep each night.
>Thanking you in anticipation,
>Yoga
>|||I've got a DIY SQL error log checking , as you can see in the script there a
various terms filtered out , change it as required.
I've selected those terms , as error logs I'm not interested in. It takes a
parameter , being the server name . I've got it wrapped on another sp that
runs through the servers , hitting the the error log sp , and then if
relevant send an email
http://www.quicksqlserver.com/2007/...erver_log_.html
Jack Vamvas
___________________________________
Advertise your IT vacancies for free at - http://www.ITjobfeed.com
"Yoganarasimha Prasad" <yogakiran@.gmail.com> wrote in message
news:elZrRg9bHHA.1388@.TK2MSFTNGP05.phx.gbl...
> Hi,
> We have a large number of SQL servers that we are supporting. Monitoring
> the error logs for new errors is really a big task as we have to manually
> check these error logs. I was hoping that some of you might have automated
> this process and filtered out the unwanted messages from the error log and
> mail only the genuine ones. If anyone can share it with the group, it will
> be terrific as you will be giving us extra minutes of sleep each night.
> Thanking you in anticipation,
> Yoga
>

Monitoring SQL Server Error logs

Hi,
We have a large number of SQL servers that we are supporting. Monitoring the
error logs for new errors is really a big task as we have to manually check
these error logs. I was hoping that some of you might have automated this
process and filtered out the unwanted messages from the error log and mail
only the genuine ones. If anyone can share it with the group, it will be
terrific as you will be giving us extra minutes of sleep each night.
Thanking you in anticipation,
YogaYou'll need to define for yourself what a wanted message is.
One option is to use finstr to search for whatever it is you
are looking for - you can find examples in these articles:
http://support.microsoft.com/?id=115519
http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=40
You can automate those in a job.
Another consideration is how you set up and use your alerts
and monitoring on the servers. For most things you can be
notified if monitoring is set up correctly.
Of course there are a lot of third party solutions but I
take it your looking for scripts and built in solutions.
-Sue
On Mon, 26 Mar 2007 11:53:38 -0700, "Yoganarasimha Prasad"
<yogakiran@.gmail.com> wrote:
>Hi,
>We have a large number of SQL servers that we are supporting. Monitoring the
>error logs for new errors is really a big task as we have to manually check
>these error logs. I was hoping that some of you might have automated this
>process and filtered out the unwanted messages from the error log and mail
>only the genuine ones. If anyone can share it with the group, it will be
>terrific as you will be giving us extra minutes of sleep each night.
>Thanking you in anticipation,
>Yoga
>|||I've got a DIY SQL error log checking , as you can see in the script there a
various terms filtered out , change it as required.
I've selected those terms , as error logs I'm not interested in. It takes a
parameter , being the server name . I've got it wrapped on another sp that
runs through the servers , hitting the the error log sp , and then if
relevant send an email
http://www.quicksqlserver.com/2007/03/sql_server_log_.html
Jack Vamvas
___________________________________
Advertise your IT vacancies for free at - http://www.ITjobfeed.com
"Yoganarasimha Prasad" <yogakiran@.gmail.com> wrote in message
news:elZrRg9bHHA.1388@.TK2MSFTNGP05.phx.gbl...
> Hi,
> We have a large number of SQL servers that we are supporting. Monitoring
> the error logs for new errors is really a big task as we have to manually
> check these error logs. I was hoping that some of you might have automated
> this process and filtered out the unwanted messages from the error log and
> mail only the genuine ones. If anyone can share it with the group, it will
> be terrific as you will be giving us extra minutes of sleep each night.
> Thanking you in anticipation,
> Yoga
>

Monday, March 12, 2012

Monitoring log usage

Hi Everyone,
I'mn setting up a proposal for a new hard drive for one of our SQL servers.
In an effort to get supporting data, I've defined performance counter logs f
or both %Disk and %Idle. Currently, %Idle is a minimum of 74.161 and a maxi
mum of 100.081. After I get the new drive installed and move the logs over
to that drive, I expect the
se percentages to change.
Question: Are there any other counter(s) I should be using to get more exac
t data that exposes the benefits of having the log files on a different hard
drive?
Thanks in advance
LarryYou should always have the log on a separate physcial drive from the data
for 2 reasons ( irregardless of stats) if there is going to be anything more
than minimal use of the database.
1. separate random IO from Serial IO... Log is serial(mostly) and data files
are random (mostly).
2. If you need up to the minute recovery without loss of data, you'd better
have your log on a separate drive...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Larry" <Larry@.discussions.microsoft.com> wrote in message
news:8A16AAEB-D472-4037-90EE-1D9B9EB5A202@.microsoft.com...
> Hi Everyone,
> I'mn setting up a proposal for a new hard drive for one of our SQL
servers.
> In an effort to get supporting data, I've defined performance counter logs
for both %Disk and %Idle. Currently, %Idle is a minimum of 74.161 and a
maximum of 100.081. After I get the new drive installed and move the logs
over to that drive, I expect these percentages to change.
> Question: Are there any other counter(s) I should be using to get more
exact data that exposes the benefits of having the log files on a different
hard drive?
> Thanks in advance
> Larry

Monitoring log usage

Hi Everyone,
I'mn setting up a proposal for a new hard drive for one of our SQL servers.
In an effort to get supporting data, I've defined performance counter logs for both %Disk and %Idle. Currently, %Idle is a minimum of 74.161 and a maximum of 100.081. After I get the new drive installed and move the logs over to that drive, I expect the
se percentages to change.
Question: Are there any other counter(s) I should be using to get more exact data that exposes the benefits of having the log files on a different hard drive?
Thanks in advance
Larry
You should always have the log on a separate physcial drive from the data
for 2 reasons ( irregardless of stats) if there is going to be anything more
than minimal use of the database.
1. separate random IO from Serial IO... Log is serial(mostly) and data files
are random (mostly).
2. If you need up to the minute recovery without loss of data, you'd better
have your log on a separate drive...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Larry" <Larry@.discussions.microsoft.com> wrote in message
news:8A16AAEB-D472-4037-90EE-1D9B9EB5A202@.microsoft.com...
> Hi Everyone,
> I'mn setting up a proposal for a new hard drive for one of our SQL
servers.
> In an effort to get supporting data, I've defined performance counter logs
for both %Disk and %Idle. Currently, %Idle is a minimum of 74.161 and a
maximum of 100.081. After I get the new drive installed and move the logs
over to that drive, I expect these percentages to change.
> Question: Are there any other counter(s) I should be using to get more
exact data that exposes the benefits of having the log files on a different
hard drive?
> Thanks in advance
> Larry

Monitoring log usage

Hi Everyone,
I'mn setting up a proposal for a new hard drive for one of our SQL servers.
In an effort to get supporting data, I've defined performance counter logs for both %Disk and %Idle. Currently, %Idle is a minimum of 74.161 and a maximum of 100.081. After I get the new drive installed and move the logs over to that drive, I expect these percentages to change.
Question: Are there any other counter(s) I should be using to get more exact data that exposes the benefits of having the log files on a different hard drive?
Thanks in advance
LarryYou should always have the log on a separate physcial drive from the data
for 2 reasons ( irregardless of stats) if there is going to be anything more
than minimal use of the database.
1. separate random IO from Serial IO... Log is serial(mostly) and data files
are random (mostly).
2. If you need up to the minute recovery without loss of data, you'd better
have your log on a separate drive...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Larry" <Larry@.discussions.microsoft.com> wrote in message
news:8A16AAEB-D472-4037-90EE-1D9B9EB5A202@.microsoft.com...
> Hi Everyone,
> I'mn setting up a proposal for a new hard drive for one of our SQL
servers.
> In an effort to get supporting data, I've defined performance counter logs
for both %Disk and %Idle. Currently, %Idle is a minimum of 74.161 and a
maximum of 100.081. After I get the new drive installed and move the logs
over to that drive, I expect these percentages to change.
> Question: Are there any other counter(s) I should be using to get more
exact data that exposes the benefits of having the log files on a different
hard drive?
> Thanks in advance
> Larry