Product Documentation

Database sizing tool for XenDesktop 7

Aug 04, 2017

Currently sizing the databases for XenDesktop 7 relies on being able to interpret and understand the database sizing KB article CTX139508. This doesn’t help if you know you have a variation on the listed environments. To help, one of our principal software engineers, Chris Gilbert, created a simple tool that can help generate custom sizing information.

Why a tool?

Many have asked for an Excel file or simple formula to work out database sizing, but these methods aren’t optimal based on the level of complexity and factors involved.

The tool hides the complexity of the calculations and allows for differences between XenDesktop 7.5 and 7.6. The data it consumes and displays is rather raw, but feedback for improvements is welcomed.

Download information

The tool is a zipped msi file, so it’s easy to install and uninstall. The only dependency the tool has is on .Net 4.0; it doesn’t need any part of XenDesktop.

Download the tool from CTX209080.

How to use the tool

When you start the tool, you’ll see a window appear with a section at the top, which allows the input of parameters about the expected environment. The default sets are VDI and HSD of various sizes and should look similar to the following screenshot:

localized image

You can either update one of the rows, or just start typing numbers into the blank bottom row, and it will add more rows.

If you then choose the database type and XenDesktop version and click Calculate, the program will run the math and produce sizing guidance seen in the bottom section of the above screenshot.

The produced data includes a row for each of the rows entered in the top section. The columns will indicate an approximate size at various points in time. For Site databases, the size tends to reach a max size and stay there, as it doesn’t accumulate data. For monitoring, the database will get bigger over time, depending on configured grooming settings for monitoring. Note that this is also dependent on licensing (for example, only Platinum customers can configure the grooming interval to longer than seven days).

So, for monitoring, the data looks as follows:

localized image

Table details

For details of which tables are actually consuming the space, click on the “Sizing by Table” tab, inside which there’s a tab for each calculation:

localized image

This more detailed view shows you which tables may become large so you can possibly tune the monitoring grooming to keep certain areas smaller. The breakdown covers the baseline size (such as fixed size). Generally, tables based on users or machines have growth every day (historical load balancing info) and have growth only on working days (connections and sessions). These are then rolled into a weekly growth column (assumes five working days in a seven-day week) and then into the monthly column.

Exporting the data into Excel

To export any of the tables into Excel, simply click in the table, select and copy all the content, and then paste it into Excel.

This article was modified from a blog post written by Chris Gilbert. You can find the original post, read the comments, and post feedback here: