Method A: If you know the postgres user password you can use the pgAdmin utility: 1A. Open pgAdmin by going through the Start Menu EventSentry Database pgAdmin 2A. Double click on EventSentry under the Servers category. 3A. Enter the postgres user password this was set during installation and click OK. 4A...
The builtin EventSentry database ships with a basic configuration which is tuned for wide compatibility instead of speed. If you are collecting a lot of data it is likely that the default parameters are undersized for your system resulting in poor collector performance high outbound queue size or resulting in poor performance when searching...
If after purging data from your EventSentry database you still have enough disk space approximately 1.5x the database size is needed available on the drive you can open the PgADMIN software doubleclick EventSentry localhost:5432 to bring up the logon window and log on with the Postgres password and then follow these steps to shrink...
First we recommend you make a backup of the database in case you have any issues and need to reinstall: How do I back up the built in EventSentry database Once you39ve got a backup then you can proceed with moving the database by following these steps: Stop the EventSentry Database v14 Service Control Panel Administrative Too...
After successfully migrating to the newer PostgreSQL v14.2 database that is available in EventSentry v5.0 and later the legacy v9.6 builtin database can be removed if the data is no longer needed. NOTE: Recovering data from the PostgreSQL v9.6 database is not possible unless a database or host backup is available. Do not proceed unless ...
The default and recommended database upgrade path when upgrading to EventSentry v5 is to access existing data from the v9.6 database through a separate profile in the web reports and start storing future data in the newer v14.2 database. Migrating existing data from the older v9.6 to the newer v14.2 is possible with a migration script but is...
