LogoLogo
Release notesAPI docsDocs homeEphemeral CloudTonic.ai
  • Tonic Ephemeral guide
  • About Tonic Ephemeral
  • Getting started with the Ephemeral free trial
  • Managing your Ephemeral account
  • Managing Databases
    • Viewing the list of databases
    • Starting a database
    • Changing the database configuration
    • Database configuration settings
      • Setting the required resources for a database
      • Setting the database expiration
      • Providing a custom configuration file
    • Connecting to a database
    • Resetting a database
    • Deactivating and reactivating databases
    • Managing auto snapshots
    • Tracking database activity
    • Deleting a database
  • Managing user snapshots
    • About user snapshots
    • Viewing the user snapshot list
    • Creating a user snapshot from an Ephemeral database
    • Creating a user snapshot from imported data
    • Editing a user snapshot
    • Creating a database from a user snapshot
    • Deleting a user snapshot
  • Installing and configuring Ephemeral
    • Ephemeral architecture
    • Configuring an allowlist for Ephemeral Cloud database connections
    • Installing a self-hosted instance of Ephemeral
      • System requirements
      • Deploying Ephemeral with Helm
    • Configuring database access on a self-hosted instance
    • Configuring tolerations and node selectors
    • Managing access to Ephemeral
      • Managing Ephemeral users
      • Enabling SSO on a self-hosted instance
        • Google
        • Okta
    • Setting the registry location for data volumes
    • Managing custom images
      • Creating, editing, and deleting custom images
      • Oracle image configuration
    • Configuring automatic deletion of snapshots
  • Monitoring and data collection
    • Monitoring your Ephemeral billed usage
    • Monitoring your disk storage
    • Data that Tonic.ai collects
  • Using the Ephemeral API
    • About the Ephemeral API
    • Configuring Ephemeral
    • Getting information about Ephemeral databases
    • Starting a database
    • Managing databases
    • Managing snapshots
Powered by GitBook
On this page
  • Expiring a database based on inactivity
  • Expiring a database after a specific amount of time
  • Limiting a database to business hours

Was this helpful?

Export as PDF
  1. Managing Databases
  2. Database configuration settings

Setting the database expiration

PreviousSetting the required resources for a databaseNextProviding a custom configuration file

Last updated 10 months ago

Was this helpful?

You can configure the database to expire automatically, or to pause outside of business hours. When you start a new database, the default configuration is to expire the database after 8 hours of inactivity.

To set the expiration, on the Settings tab of the details panel, Establish an expiration timer for the database must be in the on position.

When you enable expiration, the options are:

  • Inactivity - The database expires when it hasn't been used for a specified amount of time. For example, expire the database after it hasn't been used for 3 hours. By default, a database expires after 8 hours of inactivity.

  • A set duration - The database expires after a specific amount of time. For example, expire the database 3 days after it is created. If the database is in use when it is scheduled to expire, Tonic Ephemeral waits to expire the database until an hour after it is no longer in use.

  • Business hours - The database is only active during specified business hours, and pauses outside of those hours. The database does not expire. For example, pause the database each weekday at 5:00 PM, and resume it the next weekday at 7:00 AM. If the database is in use when the business hours end, Ephemeral waits to pause the database until an hour after it is no longer in use.

Expiring a database based on inactivity

To set the expiration based on inactivity:

  1. Click Inactivity.

  2. Select the length of inactivity after which the database expires.

  3. Ephemeral provides built-in options to expire the database after 3, 8, or 24 hours of inactivity. To configure a custom expiration:

    1. Click Custom.

    2. In the value field, provide the number of hours or days of inactivity after which to expire the database.

    3. Click the unit to use (Hours or Days).

Expiring a database after a specific amount of time

To set the expiration based on a specific time period:

  1. Click Set Duration.

  2. Select the length of time that the database is active.

    1. In the value field, provide the number of hours or days that the database is active.

    2. Click the unit to use for the duration (Hours or Days).

Limiting a database to business hours

To limit a database to specified business hours:

  1. Click Business Hours.

  2. From the Timezone dropdown, select the time zone to use to determine the business hours.

  3. From the From and To dropdowns, select the start and end days when business hours are in effect. For example, for a traditional 5-day work week, the start day is Monday and the end day is Friday.

  4. From the Start and End dropdowns, select the start and end time for each business day. For example, your business hours might be from 7:00 AM to 6:00 PM.

Expiration based on inactivity
Expiration based on a set duration
Limiting a database to specified business hours