MonitorWare Knowledge Base

I would like to know the exact function of the dbo.systemeventsproperties listed in the SQL configuration script. I had 3 primary tables configured for different windows and non windows machines. When I upgraded to the latest winsyslog it changed the database structure and produced many errors in my event log. I noticed it added 2 fields and required the systemeventsproperties table. I look in that table now and am confused by what it is for. This is an (edited) sample

1 104969 CustomerID 0
2 104969 SystemID 0
3 104969 rawsyslogmsg <133>EvntSLog: [AUS] Thu Apr 01 10:39:12 2004: WINDOWS_DC/Security (673) - "Service Ticket Granted: User Name: EXCHANGE_SRV$ User Domain: WINDOWS_DOMAIN Service Name: EXCHANGE_SRV$ Service ID: %{LONG_SID_NUMBER} Ticket Options:


A single record seems to span 3 rows and they all have the same SystemEventID. I am only concerned because currently the table is already occupying 3gigs of data, and I am wondering if it is of any use or required by the program. I searched the help file and the only page that came up involved the creation of the tables. Can you shed some light, thank your response.

Hello,

Read the following FAQ for details about SystemEventsProperties table:(This FAQ applies for WinSyslog as well)

http://www.monitorware.com/en/FAQ/MWAge ... ucture.asp

The advantage of this table is that the parameters in the SystemEventsProperties table can be used efficiently for Reporting purposes. These parameters are used by MonitorWare Console which is an analytical tool. These parameters actually help in generating more meaningful reports. As far as other fields are concerned, like CustomerID and SystemID, they are not currently used but we have plans of using them in the future. They will help in identifying that the records that have been logged in the database are coming from which customer site (in case you are using our products for your customers for monitoring their networks).

I hope this answer your questions.

Best Regards
Wajih-ur-Rehman
Adiscon