---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Calculate the order-preserving and tokenization database size

# Calculate the order-preserving and tokenization database size {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 30. Juni 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

If using order-preserving encryption or encryption patterns, determine the size of
your MySQL database by multiplying the number of potential records by record
size.

## Vorbereitungen

Role required: admin

## Warum und wann dieser Vorgang ausgeführt wird

Use a dedicated machine to run the order-preserving and tokenization database. Do not
run the database on the same hardware as the proxy server.

## Prozedur

1. Determine the potential number of records that could include fields encrypted with order-preserving encryption.
   1. Multiply the number of encryption configurations using order-preserving encryption by the number of records each configuration is applied to.
   2. To allow for growth, multiply the result by three.
   {#size-db__substeps_iys_wjb_tz}
2. Multiply the result of step 1 by 1,536.  
   1,536 is the average size of a record in bytes.
3. If using encryption patterns, perform steps 1--2 for tokenized records and add the result to the total.

## Ergebnisse

The calculated value is the recommended size in bytes for your order-preserving and
tokenization database.

