By Gina Daly, Technical Writer for Technical Marketing, End-User Computing, VMware
With significant contributions from
Jason Marshall, Manager, Product Engineering, End-User Computing, VMware
Growing up, we had a small flower garden, which my mother proudly kept. The rose bushes stand out in my memory—vibrant, colorful, and, more often than not, taller than me. Without regular pruning, these rose bushes would have caused a multitude of problems.
Like pruning a plant to maintain health, the VMware App Volumes SQL database requires pruning to keep it in perfect working order. The Knowledge Base (KB) article Pruning the VMware App Volumes SQL database details how you can keep your database in tip-top condition by pruning certain tables.
Because certain archival tables are constantly growing, the SQL database increases in size quite quickly. The archival tables in question are
- log_records
- snapvol_timeseries
- system_messages
We recommend deleting data from these tables to keep the database at a reasonable size. This is conducive to maintaining a healthy environment, and keeps performance issues in check.
So, what does this pruning task involve? All you need to do is to connect to the App Volumes SQL database and execute the following queries to delete data from the relevant archival tables:
DELETE FROM log_records WHERE created_at < DATEADD(day, -90, GETDATE());
DELETE FROM snapvol_timeseries WHERE created_at < DATEADD(day, -90, GETDATE());
DELETE FROM system_messages WHERE created_at < DATEADD(day, -90, GETDATE());
These commands delete all data older than the last 90 days from the tables. Your App Volumes database is officially pruned and ready for business!
For the technical details, see Pruning the VMware App Volumes SQL database.
