OriginCreate an instance
Use the current console guide for live instance workflows and availability. Screenshots below illustrate the demo workspace with sample data. In the signed-in console, actions operate on the selected instance when your role and its capabilities allow them.
Configure resources, review the deployment, and distinguish a local preview from a live instance.
1. Start from your instance inventory
Sign in to the console, open Instances, then choose New instance. Follow the available configuration and review steps for your selected instance type.
A page labeled Local preview creates a browser entry, not infrastructure. It does not issue production credentials or start billing. Use a live quote and provisioning response to confirm a real deployment.
2. Choose a configuration
Free provides a starting configuration. A pooled configuration shares provisioned resources; Dedicated offers instance resources and supported configuration controls. Use the choices currently offered to your organization. Check the displayed resource limits and eligibility before continuing.
Supply an instance name and environment, then choose an available deployment location. The current preview accepts 3–40 lowercase letters, numbers, or hyphens, starting with a letter, and checks for duplicate names in the organization. Live deployment validation is authoritative.
3. Review a free configuration
With Free selected, review the supplied compute, storage, and feature summary. You do not configure dedicated resources in this mode. A local preview can demonstrate the console without a billable database; a live free database requires a successful provisioning response.
When using a managed free instance, check its current storage quota, idle behavior, and per-account eligibility. These service limits are separate from the browser preview's sample configuration.
4. Configure a dedicated instance
| Setting | What to review |
|---|---|
| Compute | The selected vCPU and memory per node. |
| Storage | Capacity, storage mode, and any cache allocation. |
| Availability | Node count and the topology supported by the selected configuration. |
| Recovery | The requested retention window and any recovery feature prerequisites. |
| Networking | Public or private connectivity requirements. |
| Capabilities | SQL, vector, graph, full-text, and optional features supported by the instance. |
| Release channel | The engine release offered for the target deployment. |
Options marked Preview, including a preview topology, must not be treated as a production availability guarantee. Saved feature preferences do not activate engine capabilities. A live quote is required to confirm price, region availability, and valid combinations.
Read deployment options and replication limits before choosing the topology for a production workload.
5. Review before creating
Choose Review instance and check the name, region, resources, features, and network request. Use Edit configuration to change them. In local preview, Create preview instance saves only the browser entry.
For a live launch, review the quote and any required approval or payment step before submitting. Follow the actual provisioning status; an inventory row or a draft is not proof that the database is running. If credentials are shown once, store them securely. Rotating a credential can invalidate the previous value and affect connected clients.
Next: connect and query
Open the instance overview, use Connect for your application or client, then follow the quickstart against a confirmed live endpoint.