Understanding Data Obects

This article covers the following topics:

• What is a database object?
• How am I charged?
• What is not counted as a database object?
• How can I view my usage?
• How to estimate usage

What is a database object?

A database object is a single row of data within a database table. Objects can contain a single field or hundreds of fields, depending on your schema.

Relational schema design is strongly recommended, as it reduces data redundancy, improves scalability, and directly lowers your object count, which affects your hosting plan.

The following object types count toward your usage:

How am I charged?

Billing is based on the total objects stored, regardless of the number of administrators or users. System and custom field metadata contribute minimally to your count.

If you exceed your plan's allocation, overages can be purchased in small increments. See the pricing page for rates.

What is not counted as a database object?

The following are not counted toward your database object usage:

• Event Stream events
• History and audit logs
• CMS Pages, Layouts, and Partials
• Assets
• CLI deployment logs
• DNS records
• Email and SMS Layouts

There are currently no limits or retention policies on Event Stream events and history logs on staging or production instances.

How can I view my usage?

Usage is available in the Insites Console and IIA, broken down by module with historical trends. Use this to plan data retention policies and determine when to upgrade your plan.

How to estimate usage

Use the following to estimate your total object count and select an appropriate plan: