What are the Microsoft SQL server database growth requirements for upgrading to 2.93 or newer?

The database upgrade can consume a large amount of disk space for Microsoft SQL databases. You would need to look up the size of the ESEventLogMain table (in SQL Management Studio you can right-click the table and choose Properties and then view the Storage tab) and then plan for the following disk space growth:

1) Temporary: EventSentry database transaction log size increase of 110% the size of your ESEventLogMain table. So if your table is 100GB you would temporarily need 121GB of disk space for the EventSentry transaction logs while the upgrade is in progress.

2) Temporary: TempDB size of 25% of your ESEventLogMain table. So if your table is 100GB you would temporarily need 25GB of disk space for your SQL server's TempDB.

3) Permanent: Size increase of ESEventLogMain table, increase of 4 bytes per row. The row count can be found in the same place as the table size.

4) Permanent : Size increase of the whole EventSentry database, it will be approximately 5% larger due to many new indexes being added in the database upgrade.

If you do not have adequate temporary or permanent disk space available to accommodate this change, you can create a new database to store your 2.93-and-newer data using these steps (please note these instructions are for the 3.0-and-newer interface, the button placement is slightly different in 2.93 and there is no EventSentry Web Reports service):
1) Stop all of your agents on all of your machines managed by EventSentry. In EventSentry, in the toolbar go to Groups > Other Actions > Stop > Go. You also need to temporarily stop other data from going to the database, so on the EventSentry server you need to go to the windows services management (start > run > services.msc) and stop the EventSentry, EventSentry Heartbeat Monitor, EventSentry Web Reports, and EventSentry Network Services. If you are missing any of these services, that's ok, it just means you are not using all of the EventSentry features.

2) In EventSentry, in the left tree under Actions, click your database action to view the database settings. On the settings page click the X button (next to the Create button) to remove the database settings. Click the Initialize or Update Database button to go through the database setup wizard. Once you're done with the wizard, you will have a new copy of your EventSentry database. Click the Test button to make sure you can write to the new database.

3) Push your new database settings to your managed machines, so in the EventSentry toolbar go to Groups > Push Configuration > Go. Then choose Groups > Other Actions > Start. You can turn on all of the EventSentry server functions again by going to the windows services management (start > run > services.msc) and starting the EventSentry, EventSentry Heartbeat Monitor, EventSentry Web Reports, and EventSentry Network Services.

4) To be able to look up both your old and new data in the web reports, you will need to go to the web reports and go to Settings (gear icon) and then choose Profiles. Click "Create New Profile" in the upper left corner, put the new database info in the Database Connection section, making sure the UTC box is checked, and then click the Test Connection button to make sure the connection works, and then click Submit to save the new database profile. Now you can click the little down-arrow next to the EventSentry logo in the upper left corner and select your old data profile or new data profile, so that you can look up all of your data.