SSRS Reminded Me of the Time Microsoft Retired TMG

Question

SSRS Reminded Me of the Time Microsoft Retired TMG

Marko Coha

Grasshopper

Points: 10
More actions
July 11, 2026 at 12:00 am

#4888703

Comments posted to this topic are about the item SSRS Reminded Me of the Time Microsoft Retired TMG

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

pnr8uk SSCommitted Points: 1830 More actions · Answer 1

So few companies now wanting or using SSRS which I think is a big shame, still my favourite reporting platform and the irony of course is everyone now tries to make Power BI look like SSRS!

SSRS changed my life way back when, so I will always be grateful but still think it has a huge place and you probably won't be surprised when you hear my stories of telling businesses they had this great reporting tool which was actually 'free'.

Long live SSRS

Rod at work SSC-Dedicated Points: 34127 More actions · Answer 2

We're still writing apps that utilize SSRS. I'm sure the DBAs are aware of the fact that SSRS is dead and gone, with SQL 2025, but they're keeping that reality quiet, for the time being.

Kindest Regards, Rod Connect with me on LinkedIn.

jpratt-797544 SSC Eights! Points: 936 More actions · Answer 3

I made the switch from SSRS to PBIRS in 2017 since we couldn't get the cloud service and already had SQL Server Enterprise with SA on-prem. It is a seamless transition for those with existing SSRS reports, and I still use the SSRS extension in Visual Studio (now 2026) to build the paginated reports. You can, of course, still use Report Builder to build paginated reports and deploy them to PBIRS. The one down-side is that the initial releases are buggy and they will (eventually) frag your Report Server installation with no rollback available.

My recommended tried-and-true approach is as follows: 1) Wait until 2 months after an initial PBIRS release to see what patches they issue. 2) Use a fully-functional test environment to install it on first. 3) Have IT make a snapshot or full backup of the test server. 4) Install the PBIRS update on the server and the matching desktop Power BI IDE on a secondary PC. 5) Test opening a Power BI report, refreshing it locally, deploying it, and using it. 6) Test a variety of other Power BI reports. 7) Repeat in production from #3 on.

Note that I didn't mention having to test actual paginated reports. I have seen no issues in 9 years with SSRS/RDL reports under PBIRS. It doesn't mean there won't be any, but PBIRS is truly a superset of SSRS and it's the Power BI stuff that is "new".

J Pratt

richardd Hall of Fame Points: 3995 More actions · Answer 4

Having spent around 15 years begging MS to provide an MVC - and later a .NET Core - replacement for the ancient WebForms-based ReportViewer control, this certainly feels like the final middle-finger response to web developers.

Sure, we were told that the "solution" was to move to PowerBI Premium a few years back. But I have still yet to see a genuine replacement for the ReportViewer control. The closest I've seen is a complicated setup to embed the report in an iframe, which seems to require the PBIRS server instance to be accessible from the internet.

No thanks. We'll be sticking with SSRS (and therefore .NET Framework) for as long as it continues to work.

Steve Jones - SSC Editor SSC Guru Points: 742868 More actions · Answer 5

I love Power BI, but I think the complexity and cost can be challenging at times. SSRS is well known and proven. I certainly would be careful about migrating things.

I love things that work and don't look to change just because.