Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««45678»»

How to centralize your SQL Server Event Logs. Expand / Collapse
Author
Message
Posted Wednesday, May 30, 2012 4:38 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 6, 2014 2:02 AM
Points: 4, Visits: 103
Geoff A (5/30/2012)
Hi Phil,

Only MSSQL logs will be forwarded to the central server. That is a SQL Server Agent function.
SQL Server Agent will not forward non SQL Application log entries.

The modification to the script will work, but only on the server where the error occurs.

Thanks


Thanks for the quick reply Geoff.

I'm having a little trouble trying to grasp the concept. Maybe I'm misunderstanding SQL Server Agent's role in this.

I only want to monitor one SQL Server, and write the errors into a database on that server. In this case, all errors are occurring on that one server, the server that is monitoring for errors. But the script isn't picking up non-SQL specific errors. If the script is reading directly from wherever the Event Viewer Application log is, it shouldn't matter that the errors are not SQL specific?

Thanks

Phil
Post #1308235
Posted Wednesday, May 30, 2012 4:46 AM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Tuesday, June 24, 2014 12:24 PM
Points: 514, Visits: 1,717
try this script instead;

query = "Select * from __InstanceCreationEvent" _
& " " & "where TargetInstance isa 'Win32_NTLogEvent'" _
& " " & "and (TargetInstance.Logfile = 'Application' or TargetInstance.Logfile = 'System')" _
& " " & "and (TargetInstance.EventType = 1 or TargetInstance.EventType = 2)"
Post #1308239
Posted Thursday, May 31, 2012 3:02 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 6, 2014 2:02 AM
Points: 4, Visits: 103
Geoff A (5/30/2012)
try this script instead;

query = "Select * from __InstanceCreationEvent" _
& " " & "where TargetInstance isa 'Win32_NTLogEvent'" _
& " " & "and (TargetInstance.Logfile = 'Application' or TargetInstance.Logfile = 'System')" _
& " " & "and (TargetInstance.EventType = 1 or TargetInstance.EventType = 2)"


Thanks for that, I've given it a try but I'm having the same results.

I thought the package might have cached the script or something so I recreated it with the correct script from the beginning, and it's still ignoring non-SQL errors.

Really confusing one.
Post #1308817
Posted Monday, June 4, 2012 4:38 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, September 26, 2013 9:18 PM
Points: 42, Visits: 104
Hi,

I am testing the script on one server and it works.
However it inserts four records for the same event.
Any thoughts?

Adam
Post #1310863
Posted Thursday, September 12, 2013 8:52 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, June 11, 2014 9:03 PM
Points: 3, Visits: 62
c:\>cscript EventLog2DB.vbs
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Step 0:
Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'f:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup\11'. Operating system error 3(The system cannot find the path specified.).
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.

Error in Step 0 triggers the following error. Please help
c:\EventLog2DB.vbs(30, 2) Microsoft OLE DB Provider for SQL Server: Conversion failed when converting the varchar value 'kF' to data type tinyint.
Post #1494426
Posted Thursday, May 1, 2014 11:52 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, May 1, 2014 11:46 PM
Points: 1, Visits: 4
This article was the subjectline feature article 2nd May 2014 SQLServerCentral e-mail newsletter.

Come on guys, a circa 2010 solution featuring a VBscript!? Where's the powershell updated equivalent? VBscript should be relegated to Office macros by now....

Regards, Leigh.
Post #1566924
Posted Friday, May 2, 2014 5:51 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Yesterday @ 8:21 AM
Points: 55, Visits: 292
Any thoughts to using PowerShell instead of VBScript?
Post #1566997
Posted Friday, May 2, 2014 7:51 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, June 10, 2014 4:50 PM
Points: 324, Visits: 217
Any thoughts on using Powershell instead of VB?

Edit:

Apparently DanGuzman and I both had the same thought while not reading the entire thread.



Post #1567036
Posted Friday, May 2, 2014 8:24 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 7:56 PM
Points: 36,775, Visits: 31,230
lsatchell (5/1/2014)
This article was the subjectline feature article 2nd May 2014 SQLServerCentral e-mail newsletter.

Come on guys, a circa 2010 solution featuring a VBscript!? Where's the powershell updated equivalent? VBscript should be relegated to Office macros by now....

Regards, Leigh.


Dan Guzman-481633 (5/2/2014)
Any thoughts to using PowerShell instead of VBScript?


buddy__a (5/2/2014)
Any thoughts on using Powershell instead of VB?

Edit:

Apparently DanGuzman and I both had the same thought while not reading the entire thread.


Why? It still works even after more than 3 years. Would PoSH make it better in some way? If so, I'm all for it. If not, I wouldn't change it.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1567054
Posted Friday, May 2, 2014 9:16 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, June 10, 2014 4:50 PM
Points: 324, Visits: 217
Jeff Moden (5/2/2014)
lsatchell (5/1/2014)
This article was the subjectline feature article 2nd May 2014 SQLServerCentral e-mail newsletter.

Come on guys, a circa 2010 solution featuring a VBscript!? Where's the powershell updated equivalent? VBscript should be relegated to Office macros by now....

Regards, Leigh.


Dan Guzman-481633 (5/2/2014)
Any thoughts to using PowerShell instead of VBScript?


buddy__a (5/2/2014)
Any thoughts on using Powershell instead of VB?

Edit:

Apparently DanGuzman and I both had the same thought while not reading the entire thread.


Why? It still works even after more than 3 years. Would PoSH make it better in some way? If so, I'm all for it. If not, I wouldn't change it.



Great point, I'm going to tell the company I'm working for to stop upgrading all those working VB6 apps. I'm not sure why Geoff bothered to use VBScript in the first place when he could have done this all in an assembly language app.

Or you could replace stuff like this:

Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
' get the events we want
query = "Select * from __InstanceCreationEvent" _
& " " & "where TargetInstance isa 'Win32_NTLogEvent'" _
& " " & "and TargetInstance.Logfile = 'Application'" _
& " " & "and (TargetInstance.EventType = 1 or TargetInstance.EventType = 2)" _
& " " & "and (TargetInstance.SourceName like 'MSSQL%')"
' get ready to insert into our DBA table
Set colMonitoredEvents = objWMIService.ExecNotificationQuery(query)

with this:

Get-EventLog -LogName Application -Source "MSSQL*" -EntryType Warning,Error

I don't get technology workers that say stuff like this. Working with the bottom code is much easier (and that's the whole purpose of technology) than all the string concatenated stuff above. Also, everyone new to the administration game (be it server admin or database admin) is learning Powershell, not VBScript. VBScript is dead, the new king is Powershell and it is so much better than VBScript. Geoff did a great job but there is nothing wrong with upgrading to new technology.



Post #1567079
« Prev Topic | Next Topic »

Add to briefcase «««45678»»

Permissions Expand / Collapse