You built a great set of queries in your staging database. Now you need them in production - and the two databases have different schemas, different IDs, different connection strings. EQQ's Clone feature handles that.

What cloning moves

Settings → Database - every registered connection is a valid clone target.
Settings → Database - every registered connection is a valid clone target.
  • Views, queries, and functions.
  • Parameter definitions and defaults.
  • Role permissions (optional).
  • Not the data itself - just the definitions.

Cloning in four clicks

  1. Go to Manage Queries in the source database scope.
  2. Select the queries to clone, click Clone To Database.
  3. Pick the target database. EQQ validates that the referenced tables and columns exist.
  4. Fix any mismatches in the preview, then confirm.

Large-scope clones

Cloning everything from dev to prod can take minutes because EQQ runs schema validation and permission rebinding as it goes. The operation runs as a background job; you can close the page and come back to a finished status.

Practical workflow

  1. Build and iterate in a staging database scope.
  2. Test with non-production users.
  3. Clone to production, then flip queries from In Process to Active.
  4. Keep staging as your sandbox for the next iteration.

Want to see it live? Book a 30-minute demo - we connect EQQ to your database and build a query with you. Book a Demo →