SQL Express Maximum Database Size Limitation

Challenge

Once Veeam ONE database reaches the maximum allowed size, Veeam ONE will not be able to continue data collection thus affecting data accuracy and alarms generation.
 

Cause

If you choose to host the Veeam ONE database on Microsoft SQL Server Express, be informed there is a 10 GB database size limitation for this edition. For details, see Editions and Supported Features for SQL Server.

Solution

Database migration (permanent solution)

The best way to resolve the issue would be to move Veeam ONE database to a Standard or Enterprise edition of MS SQL Server. The procedure for configuring Veeam ONE to use a new SQL Server connection is described in the following KB article: http://www.veeam.com/kb1599

Purging old data (temporary workaround)

You can also address the issue by purging old performance data as described below.

You can delete past performance data via a custom SQL script that should be run against Veeam ONE database. Follow these steps to reduce the database size:

• make sure to properly backup Veeam ONE database;
• be aware that this change will touch all of Veeam ONE components: for example in Veeam ONE Reporter you will not be able to build reports that rely on the data that you delete with the script presented below;
• keep in mind that all graphs in Veeam ONE Monitor that rely on the deleted data that will be unavailable;
• unless specifically instructed by Veeam Support, do not modify the SQL statement and do not execute it against other database tables. If the aforementioned workaround does not help to reduce the database size, please contact Veeam Support for further assistance.

CHECKPOINT
DECLARE @dt DATETIME
SET @dt = CONVERT(DATETIME, '2018-01-25 00:00:00.001' ,120)
 
WHILE EXISTS (SELECT * FROM [monitor].[perfsamplelow] WITH(NOLOCK) WHERE [timestamp] < @dt)
BEGIN
    BEGIN TRAN
    DELETE TOP (50000) FROM [monitor].[perfsamplelow] WHERE [timestamp] < @dt
    COMMIT TRAN
    CHECKPOINT
END​
DBCC shrinkfile (N'VeeamOne', 1)​

   2017-01-25 00:00:00.001 - the point in time before which the historical performance data will be purged. Change the date accordingly.
   (year)-(month)-(date)

4. Execute the statement against Veeam ONE database.
NOTE: this operation can cause significant workload on the database and growth of the database transaction log. Make sure you do not have mission-critical databases on this server.
5. Start Veeam ONE Monitor and Reporter services on the Veeam ONE server.

More Information

In case the aforementioned cleanup procedure does not help, please contact Veeam Support.