More on Runaway Log Files

I had to stop the RS service on our server. It's creating 30 megabyte log
files, once every minute. I can still serve up reports evidently with the
ReportServer service stopped in Control Panel, but I doubt I can publish
reports.
If I start the service, the log files immediately start to pile up.
Any ideas? Any way to just stop logging?
JeffYou should contact PSS for a fix for this issue. Restarting the service
should make the problem go away but it could come back at anytime.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:e$H8GRsjEHA.156@.TK2MSFTNGP10.phx.gbl...
> I had to stop the RS service on our server. It's creating 30 megabyte log
> files, once every minute. I can still serve up reports evidently with the
> ReportServer service stopped in Control Panel, but I doubt I can publish
> reports.
> If I start the service, the log files immediately start to pile up.
> Any ideas? Any way to just stop logging?
> Jeff
>|||Hi!
Nice to hear, as we have the same problem.
Would you be so kind to tell me what PSS is and how to contact them?
Armin Mueller
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:erEFxDtjEHA.596@.TK2MSFTNGP11.phx.gbl...
> You should contact PSS for a fix for this issue. Restarting the service
> should make the problem go away but it could come back at anytime.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> news:e$H8GRsjEHA.156@.TK2MSFTNGP10.phx.gbl...
> > I had to stop the RS service on our server. It's creating 30 megabyte
log
> > files, once every minute. I can still serve up reports evidently with
the
> > ReportServer service stopped in Control Panel, but I doubt I can publish
> > reports.
> >
> > If I start the service, the log files immediately start to pile up.
> >
> > Any ideas? Any way to just stop logging?
> >
> > Jeff
> >
> >
>|||Microsoft Product Support Services. See
http://support.microsoft.com/default.aspx?pr=cntactms&style=home. We are
working on the fix and should have a KB article number by the end of this
week.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Armin Mueller" <armin.mueller@.cosmicos.de> wrote in message
news:%23zEQTD$kEHA.3432@.TK2MSFTNGP14.phx.gbl...
> Hi!
> Nice to hear, as we have the same problem.
> Would you be so kind to tell me what PSS is and how to contact them?
> Armin Mueller
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:erEFxDtjEHA.596@.TK2MSFTNGP11.phx.gbl...
>> You should contact PSS for a fix for this issue. Restarting the service
>> should make the problem go away but it could come back at anytime.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>> "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
>> news:e$H8GRsjEHA.156@.TK2MSFTNGP10.phx.gbl...
>> > I had to stop the RS service on our server. It's creating 30 megabyte
> log
>> > files, once every minute. I can still serve up reports evidently with
> the
>> > ReportServer service stopped in Control Panel, but I doubt I can
>> > publish
>> > reports.
>> >
>> > If I start the service, the log files immediately start to pile up.
>> >
>> > Any ideas? Any way to just stop logging?
>> >
>> > Jeff
>> >
>> >
>>
>|||Can you tell me if there's been any progress on the hotfix and/or the KB
article related to this issue?
Thanks,
Shawn
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
news:ONXc$UFlEHA.536@.TK2MSFTNGP11.phx.gbl...
> Microsoft Product Support Services. See
> http://support.microsoft.com/default.aspx?pr=cntactms&style=home. We are
> working on the fix and should have a KB article number by the end of this
> week.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Armin Mueller" <armin.mueller@.cosmicos.de> wrote in message
> news:%23zEQTD$kEHA.3432@.TK2MSFTNGP14.phx.gbl...
> > Hi!
> >
> > Nice to hear, as we have the same problem.
> >
> > Would you be so kind to tell me what PSS is and how to contact them?
> >
> > Armin Mueller
> >
> > "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> > news:erEFxDtjEHA.596@.TK2MSFTNGP11.phx.gbl...
> >> You should contact PSS for a fix for this issue. Restarting the
service
> >> should make the problem go away but it could come back at anytime.
> >>
> >> --
> >> -Daniel
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >>
> >>
> >> "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> >> news:e$H8GRsjEHA.156@.TK2MSFTNGP10.phx.gbl...
> >> > I had to stop the RS service on our server. It's creating 30 megabyte
> > log
> >> > files, once every minute. I can still serve up reports evidently with
> > the
> >> > ReportServer service stopped in Control Panel, but I doubt I can
> >> > publish
> >> > reports.
> >> >
> >> > If I start the service, the log files immediately start to pile up.
> >> >
> >> > Any ideas? Any way to just stop logging?
> >> >
> >> > Jeff
> >> >
> >> >
> >>
> >>
> >
> >
>|||Yes, the hotfix is now available although the KB article is not finished.
Ask product support for the fix associated with KB 885286.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Shawn Hansen" <shansen@.lrs.com> wrote in message
news:%23oPKgdomEHA.1712@.TK2MSFTNGP09.phx.gbl...
> Can you tell me if there's been any progress on the hotfix and/or the KB
> article related to this issue?
> Thanks,
> Shawn
> "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
> news:ONXc$UFlEHA.536@.TK2MSFTNGP11.phx.gbl...
>> Microsoft Product Support Services. See
>> http://support.microsoft.com/default.aspx?pr=cntactms&style=home. We are
>> working on the fix and should have a KB article number by the end of this
>> week.
>> --
>> Brian Welcker
>> Group Program Manager
>> SQL Server Reporting Services
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> "Armin Mueller" <armin.mueller@.cosmicos.de> wrote in message
>> news:%23zEQTD$kEHA.3432@.TK2MSFTNGP14.phx.gbl...
>> > Hi!
>> >
>> > Nice to hear, as we have the same problem.
>> >
>> > Would you be so kind to tell me what PSS is and how to contact them?
>> >
>> > Armin Mueller
>> >
>> > "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
>> > news:erEFxDtjEHA.596@.TK2MSFTNGP11.phx.gbl...
>> >> You should contact PSS for a fix for this issue. Restarting the
> service
>> >> should make the problem go away but it could come back at anytime.
>> >>
>> >> --
>> >> -Daniel
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >>
>> >>
>> >> "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
>> >> news:e$H8GRsjEHA.156@.TK2MSFTNGP10.phx.gbl...
>> >> > I had to stop the RS service on our server. It's creating 30
>> >> > megabyte
>> > log
>> >> > files, once every minute. I can still serve up reports evidently
>> >> > with
>> > the
>> >> > ReportServer service stopped in Control Panel, but I doubt I can
>> >> > publish
>> >> > reports.
>> >> >
>> >> > If I start the service, the log files immediately start to pile up.
>> >> >
>> >> > Any ideas? Any way to just stop logging?
>> >> >
>> >> > Jeff
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>

More info

In the the Log File Viewer, I select Maintenace Plan and there I see to rows
marked with a green icon and a + sign to the left... I clicked on the + to
reveal what's under the row.. then it revealed a row with an red stop icon
to the left...
On one of the rows with red stop icon, I read this error message:
Could not generate mail report.An exception occurred while executing a
Transact-SQL statement or batch.No global profile is configured. Specify a
profile name in the @.profile_name parameter.
any suggestions?Hi Jeff
It looks like it is having problems sending the email notification. Try
changing the maintenance plan to remove these. There is probably a notify
operator task that needs to be re-configured. Also check that you can send
test emails for database mail and SQL Agent mail configuration (in the
properties)
John
"Jeff" wrote:

> In the the Log File Viewer, I select Maintenace Plan and there I see to ro
ws
> marked with a green icon and a + sign to the left... I clicked on the + to
> reveal what's under the row.. then it revealed a row with an red stop icon
> to the left...
> On one of the rows with red stop icon, I read this error message:
> Could not generate mail report.An exception occurred while executing a
> Transact-SQL statement or batch.No global profile is configured. Specify a
> profile name in the @.profile_name parameter.
> any suggestions?
>
>|||I modifyed the Maintenance Plan -> selected the Maintenance plan I selected
"Modify". then I opened the "Reporting and Logging" window and unchecked
"Send report to an email recipient". Maybe the error was here... the agent
operator set as recipient was an domain account which not exist anymore
It's a long time since this domain account was removed - strange if caused
problem for sqlserver now
I saved my modifications to the maintenance plan...
How do I manually test if this actually solved the problem'
Best Regards
Jeff|||Hi Jeff
It may be that the account had been disabled but the mailbox remained until
more recently!!
At least everything works now!
John
"Jeff" wrote:

> I modifyed the Maintenance Plan -> selected the Maintenance plan I selecte
d
> "Modify". then I opened the "Reporting and Logging" window and unchecked
> "Send report to an email recipient". Maybe the error was here... the agent
> operator set as recipient was an domain account which not exist anymore
> It's a long time since this domain account was removed - strange if caused
> problem for sqlserver now
> I saved my modifications to the maintenance plan...
> How do I manually test if this actually solved the problem'
> Best Regards
> Jeff
>
>|||Right click on the maintanence plan and select Execute from the popup menu
and View History for that plan (by right clicking on it again...)
Ekrem nsoy
"Jeff" <donot@.spam.me> wrote in message
news:eDsSQBLQIHA.4584@.TK2MSFTNGP03.phx.gbl...
>I modifyed the Maintenance Plan -> selected the Maintenance plan I selected
>"Modify". then I opened the "Reporting and Logging" window and unchecked
>"Send report to an email recipient". Maybe the error was here... the agent
>operator set as recipient was an domain account which not exist anymore
> It's a long time since this domain account was removed - strange if caused
> problem for sqlserver now
> I saved my modifications to the maintenance plan...
> How do I manually test if this actually solved the problem'
> Best Regards
> Jeff
>

Monsterlog file - short term solution?

Hi,
Ive inherited admin of a database of which I was a user, so I'm new to this.
The log file has grown to an enormous size. This has happened in the past
(only a couple of times in a year) and the db admin has fixed it. From
reading other posts I think I will set the recovery to SIMPLE (it is a data
warehouse). (However whatever scheme was in put in place by the admin
normally worked OK, even with recovery set to FULL, so I am not sure what has
changed.)
So, I still have the problem right now of the huge log file and a database
that will not respond. Can I fix the problem without backing up the log file
(to be honest the log file is of no use)? There is not enough space on disk
media to backup the log file. Is there a way of "fooling" SQL Server into
thinking it has been backed up?
Any help appreciated. And yes I will read up on BOL
Les R
Sounds like you have your recovery plan set to FULL. If you
truly do not need the contents of the log file then you can
truncate it
backup log <your db> with truncate_only
go
This will delete the inactive portion of the log
You can then issue a DBCC SHRINKFILE command
to reclaim disk space the log may have requested from
the operating system in the course of it's growth:
use <your db>
go
dbcc shrinkfile(<log name>, <size>)
go
Make sure you allocate enough initial space to the log
doesn't have to keep autogrowing (assuming it's set
to autogrow).
If you're using the FULL recovery model, also set it
to SIMPLE.
Before you do anything, make sure that you in fact
do not need the log info. And read up on the
backup log and dbcc shrinkfile before you run
them so you understand them.
"Les Russell" <LesRussell@.discussions.microsoft.com> wrote in message
news:453CEC6E-4E5F-4FDB-BE4E-20AE8CB91C16@.microsoft.com...
> Hi,
> Ive inherited admin of a database of which I was a user, so I'm new to
this.
> The log file has grown to an enormous size. This has happened in the past
> (only a couple of times in a year) and the db admin has fixed it. From
> reading other posts I think I will set the recovery to SIMPLE (it is a
data
> warehouse). (However whatever scheme was in put in place by the admin
> normally worked OK, even with recovery set to FULL, so I am not sure what
has
> changed.)
> So, I still have the problem right now of the huge log file and a database
> that will not respond. Can I fix the problem without backing up the log
file
> (to be honest the log file is of no use)? There is not enough space on
disk
> media to backup the log file. Is there a way of "fooling" SQL Server into
> thinking it has been backed up?
> Any help appreciated. And yes I will read up on BOL
> Les R

Monsterlog file - short term solution?

Hi,
Ive inherited admin of a database of which I was a user, so I'm new to this.
The log file has grown to an enormous size. This has happened in the past
(only a couple of times in a year) and the db admin has fixed it. From
reading other posts I think I will set the recovery to SIMPLE (it is a data
warehouse). (However whatever scheme was in put in place by the admin
normally worked OK, even with recovery set to FULL, so I am not sure what ha
s
changed.)
So, I still have the problem right now of the huge log file and a database
that will not respond. Can I fix the problem without backing up the log fil
e
(to be honest the log file is of no use)? There is not enough space on disk
media to backup the log file. Is there a way of "fooling" SQL Server into
thinking it has been backed up?
Any help appreciated. And yes I will read up on BOL
Les RSounds like you have your recovery plan set to FULL. If you
truly do not need the contents of the log file then you can
truncate it
backup log <your db> with truncate_only
go
This will delete the inactive portion of the log
You can then issue a DBCC SHRINKFILE command
to reclaim disk space the log may have requested from
the operating system in the course of it's growth:
use <your db>
go
dbcc shrinkfile(<log name>, <size> )
go
Make sure you allocate enough initial space to the log
doesn't have to keep autogrowing (assuming it's set
to autogrow).
If you're using the FULL recovery model, also set it
to SIMPLE.
Before you do anything, make sure that you in fact
do not need the log info. And read up on the
backup log and dbcc shrinkfile before you run
them so you understand them.
"Les Russell" <LesRussell@.discussions.microsoft.com> wrote in message
news:453CEC6E-4E5F-4FDB-BE4E-20AE8CB91C16@.microsoft.com...
> Hi,
> Ive inherited admin of a database of which I was a user, so I'm new to
this.
> The log file has grown to an enormous size. This has happened in the past
> (only a couple of times in a year) and the db admin has fixed it. From
> reading other posts I think I will set the recovery to SIMPLE (it is a
data
> warehouse). (However whatever scheme was in put in place by the admin
> normally worked OK, even with recovery set to FULL, so I am not sure what
has
> changed.)
> So, I still have the problem right now of the huge log file and a database
> that will not respond. Can I fix the problem without backing up the log
file
> (to be honest the log file is of no use)? There is not enough space on
disk
> media to backup the log file. Is there a way of "fooling" SQL Server into
> thinking it has been backed up?
> Any help appreciated. And yes I will read up on BOL
> Les Rsql

Monsterlog file - short term solution?

Hi,
Ive inherited admin of a database of which I was a user, so I'm new to this.
The log file has grown to an enormous size. This has happened in the past
(only a couple of times in a year) and the db admin has fixed it. From
reading other posts I think I will set the recovery to SIMPLE (it is a data
warehouse). (However whatever scheme was in put in place by the admin
normally worked OK, even with recovery set to FULL, so I am not sure what has
changed.)
So, I still have the problem right now of the huge log file and a database
that will not respond. Can I fix the problem without backing up the log file
(to be honest the log file is of no use)? There is not enough space on disk
media to backup the log file. Is there a way of "fooling" SQL Server into
thinking it has been backed up?
Any help appreciated. And yes I will read up on BOL :)
Les RSounds like you have your recovery plan set to FULL. If you
truly do not need the contents of the log file then you can
truncate it
backup log <your db> with truncate_only
go
This will delete the inactive portion of the log
You can then issue a DBCC SHRINKFILE command
to reclaim disk space the log may have requested from
the operating system in the course of it's growth:
use <your db>
go
dbcc shrinkfile(<log name>, <size>)
go
Make sure you allocate enough initial space to the log
doesn't have to keep autogrowing (assuming it's set
to autogrow).
If you're using the FULL recovery model, also set it
to SIMPLE.
Before you do anything, make sure that you in fact
do not need the log info. And read up on the
backup log and dbcc shrinkfile before you run
them so you understand them.
"Les Russell" <LesRussell@.discussions.microsoft.com> wrote in message
news:453CEC6E-4E5F-4FDB-BE4E-20AE8CB91C16@.microsoft.com...
> Hi,
> Ive inherited admin of a database of which I was a user, so I'm new to
this.
> The log file has grown to an enormous size. This has happened in the past
> (only a couple of times in a year) and the db admin has fixed it. From
> reading other posts I think I will set the recovery to SIMPLE (it is a
data
> warehouse). (However whatever scheme was in put in place by the admin
> normally worked OK, even with recovery set to FULL, so I am not sure what
has
> changed.)
> So, I still have the problem right now of the huge log file and a database
> that will not respond. Can I fix the problem without backing up the log
file
> (to be honest the log file is of no use)? There is not enough space on
disk
> media to backup the log file. Is there a way of "fooling" SQL Server into
> thinking it has been backed up?
> Any help appreciated. And yes I will read up on BOL :)
> Les R

Monitoring Trans Log

Does anyone know of a system stored procedure that I can use to record
how much space is left on my trans logs?
Thanks for any help.
*** Sent via Developersdex http://www.codecomments.com ***
Take a look at:
DBCC SQLPERF(LogSpace)
-Sue
On Mon, 23 Jan 2006 12:12:20 -0800, Gerald Hopkins
<geraldh@.sl-tech.net> wrote:

>Does anyone know of a system stored procedure that I can use to record
>how much space is left on my trans logs?
>Thanks for any help.
>*** Sent via Developersdex http://www.codecomments.com ***
|||Thanks, Sue. This looks like what I need!
*** Sent via Developersdex http://www.codecomments.com ***

Monitoring Trans Log

Does anyone know of a system stored procedure that I can use to record
how much space is left on my trans logs?
Thanks for any help.
*** Sent via Developersdex http://www.developersdex.com ***Take a look at:
DBCC SQLPERF(LogSpace)
-Sue
On Mon, 23 Jan 2006 12:12:20 -0800, Gerald Hopkins
<geraldh@.sl-tech.net> wrote:
>Does anyone know of a system stored procedure that I can use to record
>how much space is left on my trans logs?
>Thanks for any help.
>*** Sent via Developersdex http://www.developersdex.com ***

Monitoring Trans Log

Does anyone know of a system stored procedure that I can use to record
how much space is left on my trans logs?
Thanks for any help.
*** Sent via Developersdex http://www.codecomments.com ***Take a look at:
DBCC SQLPERF(LogSpace)
-Sue
On Mon, 23 Jan 2006 12:12:20 -0800, Gerald Hopkins
<geraldh@.sl-tech.net> wrote:

>Does anyone know of a system stored procedure that I can use to record
>how much space is left on my trans logs?
>Thanks for any help.
>*** Sent via Developersdex http://www.codecomments.com ***|||Thanks, Sue. This looks like what I need!
*** Sent via Developersdex http://www.codecomments.com ***

monitoring sql server log

can somebody help me with script to monitor the sql server
log for errors/messages? thanks.use xp_readerrorlog
>--Original Message--
>can somebody help me with script to monitor the sql
server
>log for errors/messages? thanks.
>.
>

Monitoring SQL Server Error Message - Severity Level Messages

Hello,
Do SQL server error messages (severilty level messages 11-16 & 17-25),
both 2000 & 2005, get written to the Windows Application Log, as well
as, the SQL server error log? I mainly monitor the server externally
(Windows Event Logs) and would like to NOT have to configure a MAPI
client on SQL to receive the SQL server severity errors.
Thanks,
Dan
The ones that are written to the errorlog are also written to the eventlog.
However, whether an error is to be written to eventlog/errorlog depends on whether it is configured
to do so. In 2000, sysmessages table, check the dlevel column. In 2005, check sys.messages. In 2000,
you can specify whether an error is to be logged (using sp_altermessage), but not in 2005.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"danfoxley@.anon.postalias" <danfoxley@.gmail.com> wrote in message
news:1187251441.579647.169310@.i38g2000prf.googlegr oups.com...
> Hello,
> Do SQL server error messages (severilty level messages 11-16 & 17-25),
> both 2000 & 2005, get written to the Windows Application Log, as well
> as, the SQL server error log? I mainly monitor the server externally
> (Windows Event Logs) and would like to NOT have to configure a MAPI
> client on SQL to receive the SQL server severity errors.
> Thanks,
> Dan
>

Monitoring SQL Server Error Message - Severity Level Messages

Hello,
Do SQL server error messages (severilty level messages 11-16 & 17-25),
both 2000 & 2005, get written to the Windows Application Log, as well
as, the SQL server error log? I mainly monitor the server externally
(Windows Event Logs) and would like to NOT have to configure a MAPI
client on SQL to receive the SQL server severity errors.
Thanks,
DanThe ones that are written to the errorlog are also written to the eventlog.
However, whether an error is to be written to eventlog/errorlog depends on whether it is configured
to do so. In 2000, sysmessages table, check the dlevel column. In 2005, check sys.messages. In 2000,
you can specify whether an error is to be logged (using sp_altermessage), but not in 2005.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"danfoxley@.anon.postalias" <danfoxley@.gmail.com> wrote in message
news:1187251441.579647.169310@.i38g2000prf.googlegroups.com...
> Hello,
> Do SQL server error messages (severilty level messages 11-16 & 17-25),
> both 2000 & 2005, get written to the Windows Application Log, as well
> as, the SQL server error log? I mainly monitor the server externally
> (Windows Event Logs) and would like to NOT have to configure a MAPI
> client on SQL to receive the SQL server severity errors.
> Thanks,
> Dan
>

Monitoring SQL Server Error Message - Severity Level Messages

Hello,
Do SQL server error messages (severilty level messages 11-16 & 17-25),
both 2000 & 2005, get written to the Windows Application Log, as well
as, the SQL server error log? I mainly monitor the server externally
(Windows Event Logs) and would like to NOT have to configure a MAPI
client on SQL to receive the SQL server severity errors.
Thanks,
DanThe ones that are written to the errorlog are also written to the eventlog.
However, whether an error is to be written to eventlog/errorlog depends on w
hether it is configured
to do so. In 2000, sysmessages table, check the dlevel column. In 2005, chec
k sys.messages. In 2000,
you can specify whether an error is to be logged (using sp_altermessage), bu
t not in 2005.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"danfoxley@.anon.postalias" <danfoxley@.gmail.com> wrote in message
news:1187251441.579647.169310@.i38g2000prf.googlegroups.com...
> Hello,
> Do SQL server error messages (severilty level messages 11-16 & 17-25),
> both 2000 & 2005, get written to the Windows Application Log, as well
> as, the SQL server error log? I mainly monitor the server externally
> (Windows Event Logs) and would like to NOT have to configure a MAPI
> client on SQL to receive the SQL server severity errors.
> Thanks,
> Dan
>

monitoring sql error log for keywords

Hello,
We have Patrol monitoring running on our SQL Server 2000/2005 instances.
One of the alerts for Patrol is ErrorLogUpdates.
This sends out an alert when a particular keyword is found in the error log.
There are two parameters I can specify, INCLUDE keywords and EXCLUDE keywords.
I have been taking a look at quiet a few of our error logs and not making
any headway so far.
Does anyone have any suggestions as to what I can put in INCLUDE list and
EXCLUDE list of keywords to look for in SQL error log.
Thanks in advance.
Cheers.
Kunal.
Hi
Products like MOM come with preconfigured scripts, therefore I would expect
the software vendor to supply this.
John
"kunalap" wrote:

> Hello,
> We have Patrol monitoring running on our SQL Server 2000/2005 instances.
> One of the alerts for Patrol is ErrorLogUpdates.
> This sends out an alert when a particular keyword is found in the error log.
> There are two parameters I can specify, INCLUDE keywords and EXCLUDE keywords.
> I have been taking a look at quiet a few of our error logs and not making
> any headway so far.
> Does anyone have any suggestions as to what I can put in INCLUDE list and
> EXCLUDE list of keywords to look for in SQL error log.
> Thanks in advance.
> Cheers.
> Kunal.
|||First, you really have to determine what you want to be alerted on. For
instance, we monitor all the SQL errors with severity 17 or higher, backup
failure, port binding failure, restarts, and so on. Each of rthese error
types has a certain patterns that you can use. Unfortunately, MS has not been
very good at keeping the error messages consistent on many dimensions, making
life somewhat difficult.
Anyway, for port binding failure for instance, you can look for the
following text string; "SuperSocket Info: Bind failed on TCP port", and for
severe SQL errors, you may want to enumerate all the patterns like "Severity:
17", replacing 17 with 18, 19, 20, and so on. Patrol has a perl like language
and should be very easy to specific a regular expression pattern here.
Linchi
"kunalap" wrote:

> Hello,
> We have Patrol monitoring running on our SQL Server 2000/2005 instances.
> One of the alerts for Patrol is ErrorLogUpdates.
> This sends out an alert when a particular keyword is found in the error log.
> There are two parameters I can specify, INCLUDE keywords and EXCLUDE keywords.
> I have been taking a look at quiet a few of our error logs and not making
> any headway so far.
> Does anyone have any suggestions as to what I can put in INCLUDE list and
> EXCLUDE list of keywords to look for in SQL error log.
> Thanks in advance.
> Cheers.
> Kunal.

monitoring sql error log for keywords

Hello,
We have Patrol monitoring running on our SQL Server 2000/2005 instances.
One of the alerts for Patrol is ErrorLogUpdates.
This sends out an alert when a particular keyword is found in the error log.
There are two parameters I can specify, INCLUDE keywords and EXCLUDE keywords.
I have been taking a look at quiet a few of our error logs and not making
any headway so far.
Does anyone have any suggestions as to what I can put in INCLUDE list and
EXCLUDE list of keywords to look for in SQL error log.
Thanks in advance.
Cheers.
Kunal.Hi
Products like MOM come with preconfigured scripts, therefore I would expect
the software vendor to supply this.
John
"kunalap" wrote:
> Hello,
> We have Patrol monitoring running on our SQL Server 2000/2005 instances.
> One of the alerts for Patrol is ErrorLogUpdates.
> This sends out an alert when a particular keyword is found in the error log.
> There are two parameters I can specify, INCLUDE keywords and EXCLUDE keywords.
> I have been taking a look at quiet a few of our error logs and not making
> any headway so far.
> Does anyone have any suggestions as to what I can put in INCLUDE list and
> EXCLUDE list of keywords to look for in SQL error log.
> Thanks in advance.
> Cheers.
> Kunal.|||First, you really have to determine what you want to be alerted on. For
instance, we monitor all the SQL errors with severity 17 or higher, backup
failure, port binding failure, restarts, and so on. Each of rthese error
types has a certain patterns that you can use. Unfortunately, MS has not been
very good at keeping the error messages consistent on many dimensions, making
life somewhat difficult.
Anyway, for port binding failure for instance, you can look for the
following text string; "SuperSocket Info: Bind failed on TCP port", and for
severe SQL errors, you may want to enumerate all the patterns like "Severity:
17", replacing 17 with 18, 19, 20, and so on. Patrol has a perl like language
and should be very easy to specific a regular expression pattern here.
Linchi
"kunalap" wrote:
> Hello,
> We have Patrol monitoring running on our SQL Server 2000/2005 instances.
> One of the alerts for Patrol is ErrorLogUpdates.
> This sends out an alert when a particular keyword is found in the error log.
> There are two parameters I can specify, INCLUDE keywords and EXCLUDE keywords.
> I have been taking a look at quiet a few of our error logs and not making
> any headway so far.
> Does anyone have any suggestions as to what I can put in INCLUDE list and
> EXCLUDE list of keywords to look for in SQL error log.
> Thanks in advance.
> Cheers.
> Kunal.

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

Monitoring Log Files Size

Dear All,
Is there any method to monitor the size of log files in SQL Server 2000?
If yes how?
Thanks
Robert Lie
Robert Lie wrote:
> Dear All,
> Is there any method to monitor the size of log files in SQL Server
> 2000? If yes how?
> Thanks
> Robert Lie
You can use sp_helpfile to get a listing of all files (data and log) in
the current database.
David Gugick
Imceda Software
www.imceda.com
|||Is there any way to send it the information to my email automatically?
David Gugick wrote:
> Robert Lie wrote:
>
> You can use sp_helpfile to get a listing of all files (data and log) in
> the current database.
>
|||hi,
Yes. You can send the information to your e-mail address automatically.
For that you need to register your e-mail address in the SQL Server.
Create a scheduled job that executes sp_helpfile and sedn the result to
desired e-mail address
I believe this answers your question
thanks and regards
Chandra
"Robert Lie" wrote:

> Is there any way to send it the information to my email automatically?
>
> David Gugick wrote:
>
|||Use SQL Agent Alerts to watch the Performance Monitor counters that track
file size, and when the log crosses a threshold that you define, SQL Server
Agent can take predetermined actions such as running a script to increase the
log size, sending you email, or shrinking the file.
"Robert Lie" wrote:

> Dear All,
> Is there any method to monitor the size of log files in SQL Server 2000?
> If yes how?
> Thanks
> Robert Lie
>
|||Use SQL Agent Alerts to watch the Performance Monitor counters that track
file size, and when the log crosses a threshold that you define, SQL Server
Agent can take predetermined actions such as running a script to increase the
log size, sending you email, or shrinking the file.
Sorry I posted this answer on the other question you asked about log files.
"Robert Lie" wrote:

> Dear All,
> Is there any method to monitor the size of log files in SQL Server 2000?
> If yes how?
> Thanks
> Robert Lie
>

Monitoring Log Files Size

Dear All,
Is there any method to monitor the size of log files in SQL Server 2000?
If yes how?
Thanks
Robert LieRobert Lie wrote:
> Dear All,
> Is there any method to monitor the size of log files in SQL Server
> 2000? If yes how?
> Thanks
> Robert Lie
You can use sp_helpfile to get a listing of all files (data and log) in
the current database.
--
David Gugick
Imceda Software
www.imceda.com|||Is there any way to send it the information to my email automatically?
David Gugick wrote:
> Robert Lie wrote:
>> Dear All,
>> Is there any method to monitor the size of log files in SQL Server
>> 2000? If yes how?
>> Thanks
>> Robert Lie
>
> You can use sp_helpfile to get a listing of all files (data and log) in
> the current database.
>|||hi,
Yes. You can send the information to your e-mail address automatically.
For that you need to register your e-mail address in the SQL Server.
Create a scheduled job that executes sp_helpfile and sedn the result to
desired e-mail address
I believe this answers your question
thanks and regards
Chandra
"Robert Lie" wrote:
> Is there any way to send it the information to my email automatically?
>
> David Gugick wrote:
> > Robert Lie wrote:
> >
> >> Dear All,
> >>
> >> Is there any method to monitor the size of log files in SQL Server
> >> 2000? If yes how?
> >>
> >> Thanks
> >>
> >> Robert Lie
> >
> >
> > You can use sp_helpfile to get a listing of all files (data and log) in
> > the current database.
> >
>|||Use SQL Agent Alerts to watch the Performance Monitor counters that track
file size, and when the log crosses a threshold that you define, SQL Server
Agent can take predetermined actions such as running a script to increase the
log size, sending you email, or shrinking the file.
"Robert Lie" wrote:
> Dear All,
> Is there any method to monitor the size of log files in SQL Server 2000?
> If yes how?
> Thanks
> Robert Lie
>|||Use SQL Agent Alerts to watch the Performance Monitor counters that track
file size, and when the log crosses a threshold that you define, SQL Server
Agent can take predetermined actions such as running a script to increase the
log size, sending you email, or shrinking the file.
Sorry I posted this answer on the other question you asked about log files.
"Robert Lie" wrote:
> Dear All,
> Is there any method to monitor the size of log files in SQL Server 2000?
> If yes how?
> Thanks
> Robert Lie
>

Monitoring Log Files Size

Dear All,
Is there any method to monitor the size of log files in SQL Server 2000?
If yes how?
Thanks
Robert LieRobert Lie wrote:
> Dear All,
> Is there any method to monitor the size of log files in SQL Server
> 2000? If yes how?
> Thanks
> Robert Lie
You can use sp_helpfile to get a listing of all files (data and log) in
the current database.
David Gugick
Imceda Software
www.imceda.com|||Is there any way to send it the information to my email automatically?
David Gugick wrote:
> Robert Lie wrote:
>
>
> You can use sp_helpfile to get a listing of all files (data and log) in
> the current database.
>|||hi,
Yes. You can send the information to your e-mail address automatically.
For that you need to register your e-mail address in the SQL Server.
Create a scheduled job that executes sp_helpfile and sedn the result to
desired e-mail address
I believe this answers your question
thanks and regards
Chandra
"Robert Lie" wrote:

> Is there any way to send it the information to my email automatically?
>
> David Gugick wrote:
>|||Use SQL Agent Alerts to watch the Performance Monitor counters that track
file size, and when the log crosses a threshold that you define, SQL Server
Agent can take predetermined actions such as running a script to increase th
e
log size, sending you email, or shrinking the file.
"Robert Lie" wrote:

> Dear All,
> Is there any method to monitor the size of log files in SQL Server 2000?
> If yes how?
> Thanks
> Robert Lie
>|||Use SQL Agent Alerts to watch the Performance Monitor counters that track
file size, and when the log crosses a threshold that you define, SQL Server
Agent can take predetermined actions such as running a script to increase th
e
log size, sending you email, or shrinking the file.
Sorry I posted this answer on the other question you asked about log files.
"Robert Lie" wrote:

> Dear All,
> Is there any method to monitor the size of log files in SQL Server 2000?
> If yes how?
> Thanks
> Robert Lie
>