Skip to content

ALTER 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

ALTER GRAPH [IF EXISTS] graph_name [WITH (...)]

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

Updates mutable graph metadata properties.

SQL Statement

ALTER GRAPH [IF EXISTS] graph_name [WITH (...)]

Parameters

  • graph_name: Existing graph identifier.
  • WITH (...): Property updates.

Privileges

Requires administrative DDL privilege.

Example

ALTER GRAPH IF EXISTS social WITH (description = 'social interactions graph');

Notes

  • Supported property keys are build-dependent. Validate accepted keys in your target release.
  • Use IF EXISTS in automation to avoid hard failures when environments drift.