dsccommunity / dsccommunity/SqlServerDsc

SqlPowerBIRS: New resource proposal

Open
#1,351 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted resource proposal
Dominant language
PowerShell
Stars
385
Forks
224
PR merge metrics
No merged PRs in 30d

Description

Description

SSRS is basically dead and PowerBI is replacing it. They are literally the same product, except PowerBI can do more. You can still publish reports to the PowerBI RS server. With all that said, it makes sense to basically replace SQLRS.

Proposed properties

Copy and paste from SQLRs, SQLRsSetup and add 1 new parameter. Product.

Product is SSRS or PBIRS. Default is PBIRS.

Another option is to try and figure it out, PBIRS setup for instance is PowerBIReportServer.exe and SSRS is SQLServerReportingServices.exe for install. But maybe PBIRS takes precendence of SSRS. So, PBI would be looked for first and then SSRS.

You can even see here:
PBI (Latest release is 3/28)
https://www.microsoft.com/en-us/download/details.aspx?id=55329

and here
SSRS (Latest release is 2/12)
https://www.microsoft.com/en-us/download/details.aspx?id=55252

Special considerations or limitations

If there are actually differences in RS and PowerBI setup that I am unaware of. The only differences I am aware of are between different versions and setting it up for high availability. The 2 products should be the same in setup and configuration, with different registry values and install locations. This is what the Product option would take care of, to ensure we are looking in the right places.

This will also only cover the version as of today, so SQL 2016+

While we can keep SSRS and PBI separate, the code is the same, so trying to maintain duplicate code isn't ideal, but we could potentially just keep them separate.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing SQLRs and SQLRsSetup resources and comparing their setup and configuration behavior. Determine the differences between SSRS and PBIRS, then define how the Product parameter and product-detection precedence should work. Done means a new resource proposal covering SQL Server 2016+ without duplicating the shared implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.