Build NoSQL Database table schema configurations with DDL statements, indexes, and capacity settings.
Last verified: May 2026
Build NoSQL Database table schema configurations with DDL statements, indexes, TTL, and capacity settings.
Required Fields
compartmentIddisplayNameddlStatementtableLimitsOutput will appear here...Build NoSQL Database table schema configurations with DDL statements, indexes, and capacity settings. This tool helps OCI engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.
Your team is building a session store needing 50K reads/sec, 10K writes/sec, with sessions expiring after 24 hours. The builder generates a NoSQL table: primary key (user_id, session_id), TTL on session_id with 24-hour default, provisioned capacity matching the throughput. Without TTL, the team would have built a cleanup job to delete expired sessions; with TTL, expired rows auto-delete with no compute cost. Storage stays bounded at active-session-data only — easily 90% smaller than naive 'never delete' design.
Choose primary key carefully — it's the partition key for distribution. Hot partition keys (e.g., status='active' on a status-heavy workload) cause throttling. Use compound keys with high cardinality (user_id + timestamp) for even distribution.
Secondary indexes cost RU on writes — every index update consumes write capacity. Indexes on rarely-queried fields are pure cost overhead. Audit indexes regularly and drop ones not used by query patterns.
TTL (time-to-live) on table rows is the cleanest pattern for ephemeral data (sessions, caches). Set TTL at write time; rows auto-delete at expiration without consuming RU. Without TTL, you pay for storage on stale data forever or build cleanup pipelines.
The builder constructs OCI NoSQL table configurations: table resource (compartment, name, DDL statement defining primary key + columns + types), capacity (provisioned: read/write units explicitly, OR on-demand: per-request pricing), indexes (secondary global indexes for additional query patterns), TTL configuration (column-based or table-default TTL), and tags. Output is generated as oci nosql commands and Terraform oci_nosql_table + oci_nosql_index resources.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.