Technical articles on SSRS migration, T-SQL to PostgreSQL conversion, Domo integration, and paginated report modernization. Written by the team building ReportBridge.
SSRSPower BI Report ServerPBIRSComparisonMicrosoft
Power BI Report Server uses the same RDL and the same rendering engine as SSRS, and for an all-in Microsoft shop, it may be the easiest path off SSRS there is. What PBIRS gets you for free, what it still costs, and when your estate goals point somewhere else entirely.
Power BI and Fabric pricing for paginated reports is usually quoted as one number and billed as several. Per-user licensing, capacity licensing as its own separate line, and what changes when a one-time conversion replaces a recurring bill.
SSRS 2022 is patched with security fixes through January 11, 2033, and that fact is true. It is also not the reason most organizations are migrating right now. The slower, honest pressures already pushing estates off SSRS, and the earlier SQL Server dates that arrived first for some of them.
The ten T-SQL constructs that do not translate mechanically to PostgreSQL: PIVOT, recursive CTEs, temp tables, cursors, MERGE, APPLY, FOR XML/JSON, TOP WITH TIES, IDENTITY, and linked servers. What each one does, why PostgreSQL differs, and how to convert it.
What to count before you migrate off SSRS: reports, datasets, shared data sources, subscriptions, subreports, and parameters. Where the bodies are buried: duplicate names, broken references, dynamic SQL, and a 60-day execution log.
SSRS subscriptions transfer to no migration target automatically. What rebuilding one actually means, schedule, rendering, delivery, failure alerting, and how ReportBridge approaches scheduled reports on PostgreSQL.
The five stages a report goes through before it counts as converted: static assessment, automated conversion with up to three fix rounds, EXPLAIN plus LIMIT 1 execution, a parity check, and a frozen, verified lock.
Extended support for SQL Server 2016 ended July 14, 2026 — no more security patches, ever. What actually ended, who's affected, why SSRS specifically is exposed, and the three realistic paths forward.
Replacing SSRS isn't just swapping the rendering engine — it's keeping the delivery model. How we added async background rendering for long-running reports and cron-driven scheduled snapshots so the SSRS subscription workflow survives the migration to PostgreSQL.
When the AI gets you to 95% and stops, the gap closes with editor affordances, not bigger models. Live EXPLAIN, schema reference, AI-Fix-with-hint round trip, side-by-side diff, test preview, snippets — six small tools that turn a 5-minute manual round trip into 30 seconds.
How to break a long-tail of SQL conversion residuals into tiers — what to fix, what to defer, and how to know the difference. The triage methodology behind the last mile of an AI-powered T-SQL to PostgreSQL pipeline, with explicit ROI math.
A wrong-hypothesis, a broken fix, and a 30-second canary that would have saved 14 minutes. The post-mortem of three failed attempts to make Bedrock failover fire when Anthropic stalls — and the 90-second safety-net that finally produced the first observable failover event.
Three failure modes recursive CTEs reveal in AI-powered T-SQL to PostgreSQL conversion — UNION-arm type drift, an integer-to-date cast, and a column-list parser bug — and the deterministic scrubs that moved a pilot pass rate from 84.0% to 89.6%.
The most dangerous bug in an SSRS to PostgreSQL migration isn't the one that errors. It's the one that compiles, runs, and returns the wrong answer. A three-layer validation model that catches silent failures before they ship.
Automation handles 85% of an RDL conversion project. The last 15% is where migrations stall. Five UI affordances that turn a stalled migration into a shipped report library — and how to build them.
Case study in fixing an AI-powered T-SQL conversion pipeline. How schema-cache staleness, reserved-word collisions, and stripped subquery aliases dropped our pass rate to 11% — and the five changes that took it to 85.7% across a multi-jurisdictional report library.
Practical guide to the T-SQL-to-PostgreSQL gotchas that break SSRS report migrations. Covers ISNULL vs COALESCE, TOP vs LIMIT, date functions, temp tables, stored procedures, and string concatenation.
Step-by-step Bold Reports setup for SSRS refugees. What carries over (RDL format, parameters, expressions), what doesn't (custom assemblies, subscriptions), and how to configure data sources for production.
TCO analysis of legacy SSRS: Windows Server licensing, SQL Server CALs, security patches ending, talent scarcity, and opportunity cost. The real numbers behind the Nov 2025 SSRS deprecation.
Step-by-step guide to migrating from SQL Server Reporting Services. Covers why organizations migrate, the three fundamental approaches (rebuild, lift-and-shift, replatform), what to evaluate, and how ReportBridge automates the process.
Honest comparison of five cloud alternatives for paginated reports after leaving SSRS — Power BI, Bold Reports, Crystal Reports, JasperReports, and Telerik Reporting. Pros, cons, costs, and migration paths for each.
Microsoft quietly ended an era in November 2025. SQL Server 2025 shipped without SSRS. I evaluated every realistic alternative after migrating nearly 200 reports — here's what I found with honest pros and cons for each option.
ReportBridge migrates paginated SSRS reports to Domo and PostgreSQL with AI-powered conversion — most reports convert automatically, and guided correction tools close the rest. Proven across a ~190-report multi-jurisdictional library.