Definition of capacity model

Pricing for Data Masker for Oracle, Data Masker for SQL Server, SQL Clone, and SQL Provision is based on the total volume of data in all production databases that you would like to provision or mask from. This includes artefacts such as log files and FILESTREAM data.

If you are provisioning or masking from a different source eg a data warehouse or a backup, you will only need to calculate the databases size in their production environment.

Every 12 months after your subscription begins, you will be asked to ‘true up’ to check you are still on the appropriate tier for the next year.

If you exceed the tier capacity during your subscription period, you can continue to use the tool until the end of your subscription. However, you will need to true up to the appropriate tier for your next subscription period.

Example 1

You have 5 production databases with different schemas. Each database is 1.5TB in size, totalling 7.5TB at source. If you would like to provision or mask from these 5 databases over the annual subscription period, you would need a licence in the 10TB capacity tier.

Example 2

If you would like to provision a 1TB database but mask a separate 500GB database, you need to purchase a 3TB capacity license of SQL Provision, or a 1TB license of SQL Provision and a 1TB license of Data Masker to cover this usage.

Example 3

If you would like to provision a 1TB database and mask 500GB of data from the same database, you only need to purchase a 1TB capacity tier license of SQL Provision (or a 1TB license of SQL Clone and a 1TB license of Data Masker).

Example 4

If you would like to provision from a 100GB production database, and backups at different points in the database's history, you will only need to purchase the 100GB tier license. This is because you are provisioning from the same database at different points in its life.

Example 5

If you only need to provision or mask a subset of a 10TB database, you will either need to purchase the 10TB license, as this is the size of the production database, or subset out the data you want to work with into a separate database before using the tools.