MSSQL Provider

The MSSQL Provider lets you run Microsoft SQL Server as a managed service on the Solanica Platform. Instead of working with SQL Server custom resources directly, you declare a single Instance and the provider takes care of the rest.

The Solanica Platform is built on the open-source OpenEverest project, which defines a common database API (Instance, Backup, Restore, ...) shared across database technologies. The MSSQL Provider plugs SQL Server into that API.

How it works

The provider is a thin control-plane component. It validates your Instance against the selected topology, then generates and manages the corresponding MSSQL Operator resources — the operator is bundled as a dependency and does the actual SQL Server provisioning.

What you get

• A single, declarative Instance API for SQL Server
• Curated versions (SQL Server 2019 / 2022 / 2025)
• Two topologies: standalone and availabilityGroup
• Native backup & restore with point-in-time recovery
• Consistent behavior with other Solanica Platform database providers

More than a Custom Resource

Running SQL Server on the Solanica Platform gives you more than the Instance custom resource. Because the provider plugs into OpenEverest, the entire OpenEverest surface is available to you:

• The full OpenEverest API. Beyond Instance, you manage Backup, Restore, BackupStorage, and the other core resources with the same declarative, Kubernetes-native API — consistent across every database provider, not just MSSQL.
• A Web UI. Provision and operate databases from your browser: create instances with guided forms, pick a topology and version, scale resources, trigger backups and restores, and monitor status — no YAML required.
• kubectl & GitOps. The API is standard Kubernetes, so everything also works with kubectl and GitOps tools like Argo CD and Flux alongside your existing automation.

This means teams can self-serve databases through the UI while platform engineers manage the same resources declaratively — both operate on the exact same objects.

Provisioning Microsoft SQL Server from the Solanica Platform Web UI.

Creating an instance: choose a topology, version, and resources.

Configuring scheduled backups to S3-compatible storage.

Operator or provider?

Both are supported paths for running SQL Server:

	MSSQL Operator	MSSQL Provider (this)
API	MSSQLInstance / MSSQLAvailabilityGroup	Instance (core.openeverest.io)
Best for	Direct, operator-native control on any cluster	A managed-service experience on the Solanica Platform
Platform	Any Kubernetes cluster	Solanica Platform / OpenEverest

See Get Started to pick a path.

Where to next

• Installation — install the provider with Helm.
• The provider model — providers, components, topologies, backup classes.
• Topologies — standalone vs. Availability Group.
• Instance reference — the full Instance spec.