Skip to content

DROP GRAPH

Enterprise command reference.

Command Snapshot

Field Value
Category Platform Extensions
Mutates Data Yes/Depends
Scope Cluster / Object
Privilege Model Requires administrative or feature-specific governance/cluster privileges.

Purpose

Defines, changes, or removes schema and metadata objects.

Syntax

DROP GRAPH [IF EXISTS] graph_name

Operational Notes

  • Use schema-qualified identifiers in automation and automation pipelines.
  • Validate behavior in staging for cluster-impacting or governance-impacting changes.
  • Confirm runtime effects through system tables and metrics before and after execution.

When to Use

  • Use for graph, memory, governance, and licensing lifecycle management.
  • Use when feature-specific metadata and policy controls are required.

When Not to Use

  • Avoid enabling strict enforcement modes before validation and staged verification.

Common Errors and Troubleshooting

Symptom Likely Cause Action
Permission denied / unauthorized Missing privilege on object or cluster scope Re-run with required grants or elevated admin role.
Analysis/parse error Syntax variant or object shape mismatch Compare with canonical syntax and object definition.
Runtime failure under load Resource limits, breaker pressure, or node state transitions Check sys.jobs, sys.operations, sys.checks, and retry after mitigation.

Cross-References

Detailed Reference

Removes a graph namespace from graph metadata.

SQL Statement

DROP GRAPH [IF EXISTS] graph_name

Parameters

  • graph_name: Graph identifier to remove.

Privileges

Requires administrative DDL privilege.

Example

DROP GRAPH IF EXISTS social;

Notes

  • Drop or detach graph-bound vertex/edge metadata first when dependency checks apply.
  • Prefer IF EXISTS in CI/CD teardown scripts.