Knowledge Base


Please see the instructions below to see how much space a feature is using: Microsoft SQL Server: Run the following command in SQL Query Analyzer to see how many rows and how much data is being used by the tables in the EventSentry database: EXEC spMSforeachtable command1=EXEC spspaceused 3939 A better way to see a sorted list of...

KB-ID 76
Category: Database
Applies to:

We have compared network traffic used between Microsoft SQL Server and MySQL in a scenario where one event log entry is logged to a database. In this scenario EventSentry connected to the database server transferred one event log entry with approximately 200 characters and disconnected from the database. In this test we measured the follo...

KB-ID 80
Category: Database
Applies to:

When the EventSentry database is located in a SQL Server instance then you can point to the instance by using the TCP port number instead of using the instance name. This will usually solve all connection problems. To determine the TCP port of the instance do the following: Open SQL Server Enterprise Manager Rightclick the instance ...

KB-ID 94
Category: Database
Applies to:

EventSentry definitely works with SQL Server 2005 Express however some special steps need to be taken to make EventSentry work with SQL Server 2005 Express. Most of the steps outlined in this article also apply to SQL Server 2005. 1. Configuring SQL Server 2005 Express 1. Make sure that SQL Server is installled in Mixed Mode. 2. Using the ...

KB-ID 95
Category: Database
Applies to:

The anticipated database size depends on many factors not just the number of hosts that are being monitored. In order to predict the future database size you will need the following information: How many servers will be monitored What event log data will be consolidated For example will you be collecting Audit Success events How ...

KB-ID 107
Category: Database
Applies to: All Versions

There are usually two causes for the above error: 1. The SQL Server does not have SQL Authentication turned on. A trusted SQL Server connection implies that the account the agent is running under LocalSystem by default has appropriate permissions in SQL Server. This is usually not the case. 2. The SQL Server does not have an eventsentry...

KB-ID 113
Category: Database
Applies to:

It is highly recommended that you use SQL Authentication when consolidating events and other information to a SQL Server database. Microsoft SQL Server 2000: Open Enterprise Manager and locate the server name / instance name under the SQL Server Group container. Rightclick the server/instance name and select Properties. Then click the Secur...

KB-ID 114
Category: Database
Applies to:

Microsoft SQL Server 2000 Open Enterprise Manager and locate the server name / instance name under the SQL Server Group container. Rightclick the server/instance name and select Properties. On the General tab click Network Configuration Under Enabled Protocols click TCP/IP and select Properties. The resulting dialog will show yo...

KB-ID 115
Category: Database
Applies to:

This error is usually logged when you are pointing a connection string to an instance of SQL Server that does not have the EventSentry database configured correctly. For example if you have two or more instances running on a given SQL Server 2000 or SQL Server 2005 Express then you will need to make sure that you are pointing the connecti...

KB-ID 117
Category: Database
Applies to: All Versions

You may encounter one of the following errors: OdbcExpandError: 28000MicrosoftSQL Native ClientSQL ServerLogin failed for user 39eventsentrysvc39. 18456 at SQLConnect OdbcExpandError: 42000MicrosoftSQL Native ClientSQL ServerCannot open database EventSentry requested by the login. The login failed 4060 at SQLConnect ...

KB-ID 149
Category: Database
Applies to: All Versions