Skip to content

[DRAFT] Raven to SQL migration engine - #5851

Draft
warwickschroeder wants to merge 4 commits into
masterfrom
warwick/spike-migration-engine
Draft

[DRAFT] Raven to SQL migration engine#5851
warwickschroeder wants to merge 4 commits into
masterfrom
warwick/spike-migration-engine

Conversation

@warwickschroeder

Copy link
Copy Markdown
Contributor

Currently only contains the high level raven to sql migration design (still in draft).

@rbev rbev left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This all looks good so far

Comment thread docs/ravendb-to-sql-migration-overview.md Outdated
Comment thread docs/ravendb-to-sql-migration-overview.md Outdated
Comment thread docs/ravendb-to-sql-migration-overview.md Outdated

- A third RavenDB lifecycle opens the source: connect, check the version, stop. It never calls `DatabaseSetup.Execute`.
- Both source databases must be on the same server or cluster (`LicensingDataStore.cs:35`).
- 🍅 The only version check that exists today compares the RavenDB server version to the RavenDB client version, and runs only for an external source. Nothing stamps a ServiceControl data version in the database, so refusing an unsupported source and naming the version to upgrade through is new work.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could actually enforce that they run at least once with the current version and stamp it into a document, refusing to run a migration until the version in that document matches.

That would make the step 1. Upgrade ServiceControl as normal, still on RavenDB. mandatory and make sure that customers jumping major versions don't bite us.

@warwickschroeder
warwickschroeder force-pushed the warwick/spike-migration-engine branch from 3965754 to f76ce9f Compare September 11, 2026 06:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants