Reporting for SQL Server on Linux: SSRS and Alternatives
SQL Server Reporting Services (SSRS) does not run on Linux, but you can still report on a Linux SQL Server instance. Run SSRS or Power BI Report Server on a separate Windows machine, connect a cross-platform BI tool such as Grafana or Metabase, or build scripted reports in Python or R. The database itself is not the limiting factor.
This guide is for DBAs, data teams and IT leaders planning a move to SQL Server on Linux who need to keep existing reports working or choose a new reporting stack.
Key takeaways
- SQL Server has run on Linux since SQL Server 2017, but Reporting Services is listed as unsupported on Linux.
- Microsoft's supported pattern is to run SSRS or Power BI Report Server on Windows; their catalog databases can live on SQL Server on Linux.
- Starting with SQL Server 2025, Microsoft has consolidated on-premises reporting under Power BI Report Server.
- Cross-platform BI tools and Python or R scripts connect to Linux SQL Server like any other instance.
What changes for reporting when SQL Server runs on Linux?
Microsoft's documentation says SQL Server runs on Linux starting with SQL Server 2017. Supported distributions include Red Hat Enterprise Linux and Ubuntu, while SUSE Linux Enterprise Server is supported only up to SQL Server 2022. Most database engine features work the same, but Microsoft's list of unsupported Linux features includes Analysis Services and Reporting Services, and the SQL Server Agent SSRS subsystem.
So the reporting layer has to live somewhere else. That's often a good thing. Separating report processing from the transactional database reduces resource contention, and it forces a deliberate choice instead of inheriting whatever was installed years ago. A common mistake we see in migration projects is discovering this late, after the database move is scheduled, when dozens of subscriptions and paginated reports still point at a local SSRS instance.
Option 1: Keep SSRS on a separate Windows server
If you have a large library of SSRS reports, the least disruptive path is to keep SSRS on a dedicated Windows server and point its data sources at the Linux instance. To SSRS, the Linux SQL Server is just another database server. Microsoft's guidance is to run SSRS on Windows and, if you want, host the SSRS catalog databases on SQL Server on Linux.
You keep paginated reports, subscriptions, caching and the web portal. The trade-off is a Windows server to license, patch and manage in an otherwise Linux environment. For organizations already running mixed estates, that is usually acceptable.
Option 2: Move to Power BI Report Server
Power BI Report Server is Microsoft's on-premises report server. It hosts Power BI reports (.pbix), Excel files and paginated reports (.rdl), and Microsoft describes it as a superset of SSRS. Like SSRS, it runs on Windows and connects to the Linux database over the network.
This option matters more now. Microsoft's Reporting Services documentation states that starting in SQL Server 2025, on-premises reporting services is consolidated under Power BI Report Server. If you are planning a new deployment, check Microsoft's consolidation FAQ before committing to SSRS.
Licensing differs from SSRS. According to Microsoft, Power BI Report Server rights come with SQL Server Enterprise Edition core licenses with active Software Assurance (for versions before 2025; SQL Server 2025 has its own terms), with Power BI Premium P SKUs, or with Fabric F64 or larger reserved capacity. Viewing reports does not require a Power BI Pro license, but publishing some report types does.
Hosting the report server catalog on Linux
Microsoft documents how to put the Power BI Report Server catalog databases on SQL Server 2019 or later on Linux. Be ready for some Active Directory work:
- Join the Linux SQL Server instance to the domain.
- Register service principal names for the SQL Server and report server service accounts.
- Configure Kerberos constrained delegation for both accounts.
- Edit
rsreportserver.configto enable Kerberos authentication, because SQL Server on Linux supports only SQL and Kerberos authentication. - Use embedded credentials for subscriptions. Microsoft notes that the "impersonate the user viewing the report" option fails with Windows credentials in this setup.
Option 3: Use a cross-platform BI tool
Most BI tools don't care what operating system SQL Server runs on, only that they can reach it over the network. Two examples with clear documentation:
- Grafana ships with a Microsoft SQL Server data source out of the box and connects to SQL Server 2012 or newer, Azure SQL Database and Azure SQL Managed Instance. It suits operational and infrastructure dashboards.
- Metabase supports SQL Server as a data source. You supply the host, port (1433 is the usual default), database name and credentials.
Commercial platforms such as Tableau, Qlik and Looker are also common choices; check each vendor's current connector documentation for your SQL Server version. For a sense of how enterprise suites package BI, see our explainer on Infor Business Intelligence and Birst.
Tip: create a dedicated read-only database login for each BI tool. It limits damage if a credential leaks and makes query load easy to trace.
Option 4: Script reports in Python or R
For data teams that already work in code, scripted reporting runs natively on Linux. Python commonly connects through pyodbc with the Microsoft ODBC driver, and Microsoft also offers mssql-python, a driver that connects without an external driver manager. R users typically use the odbc package. From there, Jupyter, R Markdown or Quarto can produce HTML, PDF or Excel output on a schedule.
This works well for analytical reports and data quality checks. It's a weaker fit for pixel-perfect, regulated documents that business users need to run themselves.
Installing the Microsoft ODBC driver on Linux
ODBC Driver 18 for SQL Server supports Alpine Linux, Debian, Red Hat Enterprise Linux, Oracle Linux, SUSE Linux Enterprise Server, Ubuntu and Azure Linux. Installation uses each distribution's package manager. For unattended .deb or .rpm installs from version 18.4, you can accept the license by creating the file /opt/microsoft/msodbcsql18/ACCEPT_EULA. Once installed, the driver is available to applications that use unixODBC.
How do you choose the right approach?
| Situation | Best fit |
|---|---|
| Large library of SSRS paginated reports | SSRS or Power BI Report Server on Windows |
| New deployment on SQL Server 2025 | Power BI Report Server |
| Interactive dashboards and self-service | Cross-platform BI tool |
| Ops and infrastructure monitoring | Grafana |
| Analyst-built, scheduled analysis | Python or R scripts |
Whatever you pick, keep heavy report queries off the primary. Availability groups work on Linux (using Pacemaker for clustering instead of a Windows failover cluster), and readable secondary replicas can absorb read-only workloads. Note that Microsoft says readable secondaries are supported only with Enterprise edition. Good governance matters as much as tooling; our pieces on tailoring custom reporting to the business and building a reporting governance strategy apply well beyond HR systems.
FAQ
Can SSRS run on Linux?
No. Microsoft lists Reporting Services as unsupported on Linux. You can run SSRS or Power BI Report Server on a Windows server and connect it to SQL Server on Linux, and the report server catalog databases can be hosted on the Linux instance. That split keeps reporting off the database server, which is usually what you want anyway.
Is Power BI Report Server replacing SSRS?
Microsoft's documentation says that starting in SQL Server 2025, on-premises reporting services is consolidated under Power BI Report Server. Existing SSRS versions are still documented, but new projects should plan around Power BI Report Server and check Microsoft's consolidation FAQ for upgrade and licensing details.
Do I need Enterprise edition to offload reporting to a secondary?
For readable secondary replicas in an availability group, yes. Microsoft states readable secondaries are supported only with Enterprise edition, and a Standard edition secondary can be used only for availability. Alternatives include a separate reporting copy refreshed on a schedule, or tuning report queries to run at quieter times.
What to do next
- Inventory every report, subscription and data source that points at your current SQL Server.
- Sort reports into paginated, interactive and scripted, and map each group to an option above.
- Check your licensing for Power BI Report Server before you decide between it and SSRS.
- Build one test report against the Linux instance before migration day. If you also want to cut manual report work, see how AI can automate report generation.
Sources
- Microsoft Learn, SQL Server on Linux overview and Editions and supported features of SQL Server 2022 on Linux
- Microsoft Learn, What is Power BI Report Server?, Configure Power BI Report Server catalog databases for SQL Server on Linux and SQL Server Reporting Services
- Microsoft Learn, Install the Microsoft ODBC driver for SQL Server (Linux) and Availability groups for SQL Server on Linux
- Grafana Microsoft SQL Server data source and Metabase SQL Server connection documentation
Last reviewed: October 2026.

Comments
Post a Comment