SQL Server Reporting Services (SSRS) is a server-based reporting platform from Microsoft that creates, manages, and delivers formatted reports, typically pulling data from SQL Server databases. It specializes in paginated reports, the kind of structured, print-ready documents businesses use for invoices, financial statements, inventory lists, and compliance filings. If your organization runs on SQL Server and needs pixel-perfect reports that can be exported to PDF, Excel, or Word, SSRS is the tool built for that job.
How SSRS Works
SSRS runs on a report server, which is a dedicated instance installed alongside or separately from your SQL Server database. The report server stores everything: report definitions, shared data sources, schedules, and subscription settings. Users interact with it through a web portal accessible in any browser, where they can browse folders, run reports on demand, and manage permissions.
The basic workflow looks like this: a report author designs a report layout and connects it to one or more data sources. That report definition gets published to the report server. From there, end users can open the report in a browser, enter any required parameters (like a date range or department name), and view the results. They can also export to formats including PDF, Excel, Word, PowerPoint, CSV, and XML. Behind the scenes, the report server queries the database, applies the layout, and renders the output.
What Paginated Reports Actually Are
The term “paginated” means the report is designed to fit a printed page. Unlike a dashboard that scrolls endlessly, a paginated report has defined margins, page headers, footers, and data regions that expand across multiple pages in a controlled way. You can specify exact sizing down to fractions of an inch or centimeters.
This matters when you need documents that look the same every time they’re printed or saved as a PDF. Think monthly sales summaries sent to regional managers, patient billing statements, or regulatory filings where formatting requirements are strict. Paginated reports handle tables with thousands of rows by flowing them neatly across pages, repeating column headers on each page, and grouping data with subtotals exactly where you want them.
Report Authoring Tools
Microsoft provides two main tools for building SSRS reports, each aimed at a different audience.
Report Builder is a standalone, lightweight application designed for business users and analysts. It has a simplified interface with a single Report Data pane where you manage your data sources and datasets. If you need to create or modify a report without a full development environment, Report Builder is the easier path.
Report Designer lives inside SQL Server Data Tools (SSDT), which is a Visual Studio environment. It’s built for developers and IT teams who manage multiple reports as a project. Report Designer supports shared data sources and shared datasets as separate files within Solution Explorer, making it easier to reuse connections across many reports. It also integrates with Visual Studio’s Configuration Manager, so you can set up separate deployment profiles for development, test, and production servers and push reports to each with a single click.
Both tools produce the same report definition files. The choice comes down to whether you need project-level organization and source control (Report Designer) or a simpler, self-service experience (Report Builder).
Delivering Reports to Users
SSRS supports three ways to get reports to the people who need them.
On-demand access is the simplest. A user opens the web portal, navigates to a report, fills in any parameters, and views the results in the browser. They can export or print from there. This works well when people need to pull reports at unpredictable times or with unique parameter combinations.
Standard subscriptions automate delivery on a schedule. You define who gets the report, which parameters to use, and what format to deliver it in. The report server then generates the report and either emails it or drops it in a shared folder at the scheduled time. Each standard subscription produces one version of the report with one fixed set of parameters, so it works best when the same report goes to a small, known group.
Data-driven subscriptions are the heavy-duty option. Instead of hardcoding recipients and parameters, the subscription queries an external data source at runtime. Each row in the query result can specify a different recipient, different parameter values, and even a different export format. If you need to send personalized monthly statements to 5,000 customers, each showing only their own data, a data-driven subscription handles that automatically. Report server administrators typically set these up because they require query-building skills and an understanding of how parameters flow from the data source into the report.
What You Can Build With SSRS
SSRS reports go well beyond simple tables. The tablix data region (a flexible grid that combines table, list, and matrix behaviors) supports nested groups, adjacent groups, and complex layouts with repeating headers across printed pages. You can embed subreports inside a main report, pulling in related data from different queries.
Visual elements include data bars, sparklines, indicators, and gauges (both radial and linear) for displaying KPI values and status. These can be embedded directly inside grid rows, so each row in a sales table could show a small gauge reflecting performance against target. The map data region can visualize SQL Server spatial data types, rendering points, lines, and polygons on a map, and it also supports ESRI shape files for geographic overlays.
Reports can render images stored in binary format in a database, display richly formatted HTML text, and use VB.NET expressions throughout the layout. Those expressions give you access to core .NET Framework libraries, letting you calculate custom fields, conditionally format cells, or even change the layout based on which export format the user selected. You can also write reusable VB.NET function blocks within a report and call them from any expression.
Parameters are highly customizable. You can create cascading parameters (where selecting a value in one dropdown filters the choices in the next), set data-driven defaults, and use parameters not just for filtering data but for “what-if” scenarios or dynamic styling.
How SSRS Relates to Power BI
Power BI and SSRS solve different problems. Power BI is built for interactive dashboards and visual data exploration, where users click, filter, and drill into data on screen. SSRS is built for structured, print-ready documents where layout precision matters more than interactivity.
The two tools overlap in one area: Power BI Service now supports paginated reports using the same report definition format as SSRS. You can author paginated reports in Power BI Report Builder and publish them to the Power BI cloud. These paginated reports connect to any supported data source directly, without needing a Power BI semantic model first, and they support the same fine-grained formatting, complex parameters, and export options.
For organizations that want to keep everything on-premises, SSRS remains the standard tool. Starting with SQL Server 2025, Microsoft is consolidating on-premises reporting under Power BI Report Server, which runs paginated reports locally while also supporting Power BI interactive reports. If you’re already running SSRS, this is the direction the product is heading.
Licensing and Editions
SSRS is included with several SQL Server editions: Enterprise, Standard, Web, Developer, and Express with Advanced Services. The basic Express edition (and Express with Tools) does not include SSRS. There is no separate license to buy for SSRS itself; it comes as part of your SQL Server license.
The Developer edition is free and includes all Enterprise features, but it’s licensed only for development and testing, not production use. For production environments, most organizations choose Standard or Enterprise depending on their broader SQL Server needs. Power BI Report Server, the successor for on-premises reporting starting with SQL Server 2025, is available to customers running Enterprise or Standard editions. For SQL Server 2022 and earlier, Power BI Report Server rights applied only to Enterprise edition core licenses with active Software Assurance.
When SSRS Is the Right Fit
SSRS makes the most sense when your reporting needs center on structured, repeatable documents rather than interactive exploration. If your team already uses SQL Server, the integration is natural since SSRS connects directly to your existing databases without additional middleware. It’s particularly strong for high-volume automated delivery, where hundreds or thousands of personalized reports need to go out on a schedule without anyone clicking a button.
Organizations in finance, healthcare, insurance, and government tend to rely heavily on SSRS because those industries produce large volumes of formatted documents with strict layout requirements. If your primary need is ad-hoc visual analytics and self-service dashboards, Power BI is the better starting point. But for the operational backbone of scheduled, formatted, print-ready reporting, SSRS remains widely deployed and actively supported.