Migration guides / Vendor
From Redgate SQL Monitor to Obsfly
SQL Server-only. Multi-engine teams pay twice.
Why teams switch
- SQL Server-only. Multi-engine teams pay twice.
- On-prem control plane requires its own host + maintenance.
- Limited AI advisory; recommendations are rule-based.
- No multi-cloud Always-On AG visibility without manual setup.
What Redgate is genuinely good at
Fairness signal — useful in renewal conversations.
- Decade-plus expertise on the SQL Server stack.
- Strong custom alert script support for SQL-specific signals.
Migration playbook
Step 1
Compare alert coverage
Map every Redgate alert to an Obsfly rule. Most are 1:1; some custom SQL alerts become Obsfly metric expressions.
Step 2
Install Obsfly
No on-prem control plane required. SaaS or BYOC modes available.
Step 3
Migrate dashboards
Custom Redgate dashboards rebuild in Obsfly; per-engine views ship pre-configured.
Step 4
Decommission
Tear down the Redgate base monitor host after parallel-run window.
Pitfalls to avoid
- If you have Redgate Deploy / SQL Source Control, those products stay — only Monitor migrates.
FAQ
- Do we lose custom T-SQL alert scripts?
- No. Obsfly supports custom metric queries that produce a numeric series; alert rules attach the same way.
Ready to switch?
Book a 30-minute migration call.
We'll spec your parallel-run plan together, agree on success criteria, and quote your first 30-day deal.
Book a call →