Understanding Polaris Reporting Tools: SSRS, Report Builder, Power BI, SQL Server, and SSMS

Clearinghouse Repository Polaris Repository
1

A lot of reporting terminology is confusing because Polaris, Report Builder, SSRS, Power BI, SQL Server, and SSMS are related, but they are all separate tools.

One important thing up front: most reporting stuff is not really Polaris-specific. Polaris is just the application/database you are reporting against. Report Builder, SSRS, subscriptions, Power BI, SQL Server, and SSMS are Microsoft tools and technologies around reporting and database management. The good news is that means tutorials for these Microsoft reporting technologies also apply to Polaris reports, so look around for your favorites. If you are hosted, support may need to clarify which features and licensing are available in your environment.

Report Builder is the most common standalone tool used to create and edit SSRS reports (.RDL files), but SSRS report development can also be done through Visual Studio / SQL Server Data Tools in more advanced development environments.

SSMS (SQL Server Management Studio) is another separate Microsoft tool. It is typically what IT staff, database administrators, or sysadmins use to develop SQL scripts, test queries, troubleshoot data issues, or conduct one-off analysis directly against SQL Server databases. In many environments, SSMS is used to develop and validate the SQL that later gets embedded into Report Builder datasets for SSRS reports.

However, many hosted Polaris customers may not have direct SSMS access, or may only have limited SQL access depending on their hosting arrangement and permissions.

SimplyReports can also generate/publish RDL report files. Those RDLs can later be opened and further edited in Report Builder or Visual Studio if additional customization is needed.

A few presentation links that may help:

The basic workflow is:

  1. Create a blank report in Report Builder (or Visual Studio in some environments). The presentations above get into this in more detail.

  2. Within the report, create the dataset/query for the report to use (this is where the SQL goes).

    1. Often, the SQL itself is first developed or tested in SSMS before being copied into the Report Builder dataset.

  3. Publish the report to SSRS.

This allows it to show up on the SSRS website and in the Desktop Client report toolbar for general staff to use and subscribe to.

  1. Use SSRS to manage subscriptions, schedules, security, etc.

When you publish the report to SSRS, it becomes available either through the SSRS web portal/site (support or your IT department will need to let you know the URL and login information) or through the desktop client report toolbar. You can also add custom links in LEAP that can send people to the SSRS website.

Power BI is also separate. It is more for dashboards and visualizations than traditional SSRS-style reports and subscriptions.

“SQL Enterprise” usually means SQL Server Enterprise Edition. That can matter because some SSRS features, like data-driven subscriptions, depend on the SQL/SSRS edition and licensing. I do not know what Innovative provides for hosted customers, so support would probably need to answer that.

For hosted customers, contact support to find out:

  • if you are licensed to use SSRS and Report Builder

  • your SSRS portal URL

  • which Polaris data source you should use

  • whether direct SQL access or SSMS access is available in your environment

  • what SQL license is available and what subscription features are enabled

8 Likes