Recommendations from technical support:

• Remember to maintain your SQL database installation:

1. Backup: To restore an EMS installation on a new server or computer in case of an emergency, nearly everything you need is stored within your Microsoft SQL Server database. This database contains all your data and the configuration settings for your EMS system. Therefore, it is crucial to regularly back up your databases at intervals that align with your recovery expectations in the event of a server disaster.
Should you need to restore your system on another machine, you would benefit from also having specific files outside the database available. This include reports normally located in "C:\EMS Reports", image files normally located in "C:\ProgramData\EMS\uploadImg".
2. Index maintenance: Index maintenance is vital for SQL databases as it optimizes query performance, reduces response times, and prevents database slowdowns. Regular maintenance ensures efficient data retrieval and overall system stability. Therefor, it is important to regular maintain your database indexes.
Microsoft have a good article descriping this issue: https://learn.microsoft.com/en-us/sql/relational-databases/indexes/reorganize-and-rebuild-indexes?view=sql-server-ver16
3. Statistics maintenance: Statistics maintenance is crucial for SQL databases as it ensures the query optimizer has up-to-date data distribution information, leading to more efficient query execution and improved overall performance.
Microsoft says: Updates query optimization statistics on a table. By default, the query optimizer already updates statistics as necessary to improve the query plan; in some cases you can improve query performance by using the stored procedure sp_updatestats to update statistics more frequently than the default updates.

• Remember to document your installation:

1. Licenses: If you have purchased licenses, to open up additional functions in EMS, it is important that you document the License IDs. This is important as licenses are only stored as hash values and if you should need to re-apply your license it is not possible without the License ID.
Licenses may need to be re-applied because the license hash is generated based on the hardware detected when the license was first applied. In virtual environments, if the virtual machine is moved to a different host with different underlying hardware, the license may be deemed invalid and require re-application.