When trying to do a standard install of SQL Server, you may have noticed that the 2017 or newer versions of SQL Server Reporting Services (SSRS) aren’t installed as well. That’s because SSRS now has its own separate installer. In this blog, we’ll show some of the changes compared to older versions of the software and detail how to install and update the 2019 version.
Let’s first take a look at how you can get SSRS 2019 on your device. In the past you could just install your version of SQL and get the tool with it in one go. However, when installing SQL2019 through the usual method, as you did with edition 2016 or older, you will notice that you can no longer select SQL Server Reporting Services as a feature during your setup.
At the top you see a hyperlink that directs you to the Microsoft download page for the SSRS installer which is now a separate executable. Beware, though, the link included in the 2019 ISO directs you to the 2017 version of Reporting Services. So it is not the correct version.
This is the correct version for 2019. If you’re using the other installer, you will not be able to use the product key you used for the SQL2019 version you installed.
Once you’ve downloaded the correct installer for Reporting Services, copy it to the local server on which you wish to install and double click to start the installation. You will be prompted with the following window:
Click ‘Install Reporting Services’. On the next page, you can choose between a free or a paid edition. The free edition is limited to 180 days, developer and express. For the paid edition, a product key needs to be provided.
This key can be found in the ISO from SQL2019. Run the setup and continue to the product key page.
Once you’ve copied the key, click next. Accept the License terms. Click next and define the install location. Finally, press ‘Install’.
Once the installation is finished, you can start configuring your new Reporting Services. When you open it, you’ll see that it’s called SSRS. But wait… I always named my reporting service the same as the SQL instance on which it is configured. I also have several tenants with multiple SSRS instances on one host machine. Where is the option to name the service?
Sadly, since 2019 there is no longer an option included in the installation to name the service, and if we start a new installation using the downloaded .exe then we get this:
No option for a second installation or renaming can be found on this installer, unfortunaly.
Since SSRS is now a stand-alone service, it will not get updated with the patch you apply on your SQL Server, which was the case with version 2016 or older. You’ll find updates for SSRS in the download centre mentioned above. First, verify the version number of your current install by going to properties on the running service.
On the download page, you’ll find the version number of the available install files in details section.
Once downloaded and copied to the desired server, just run the file like you would when doing a new install as detailed above.
It’ll look like this:
Select “Upgrade Edition” and just follow the installer.
As you may have noticed several things are different in the new version of Reporting Services. First, because of the stand-alone installation, the service is no longer visible in the SQL Server configuration manager.
Third, the 2016 version could also be installed using command prompt, but in the official documentation of later versions this is no longer mentioned.
Finally, adding the service account, which normally happens during the installation, now must be done during configuration.
Cookie | Duration | Description |
---|---|---|
ARRAffinity | session | ARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user. |
ARRAffinitySameSite | session | This cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category. |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | Cloudflare set the cookie to support Cloudflare Bot Management. |
pll_language | 1 year | Polylang sets this cookie to remember the language the user selects when returning to the website and get the language information when unavailable in another way. |
Cookie | Duration | Description |
---|---|---|
_ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
_gat_gtag_UA_* | 1 minute | Google Analytics sets this cookie to store a unique user ID. |
_gid | 1 day | Google Analytics sets this cookie to store information on how visitors use a website while also creating an analytics report of the website's performance. Some of the collected data includes the number of visitors, their source, and the pages they visit anonymously. |
ai_session | 30 minutes | This is a unique anonymous session identifier cookie set by Microsoft Application Insights software to gather statistical usage and telemetry data for apps built on the Azure cloud platform. |
CONSENT | 2 years | YouTube sets this cookie via embedded YouTube videos and registers anonymous statistical data. |
vuid | 1 year 1 month 4 days | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. |
Cookie | Duration | Description |
---|---|---|
ai_user | 1 year | Microsoft Azure sets this cookie as a unique user identifier cookie, enabling counting of the number of users accessing the application over time. |
VISITOR_INFO1_LIVE | 5 months 27 days | YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface. |
YSC | session | Youtube sets this cookie to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt-remote-device-id | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt.innertube::nextId | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
WFESessionId | session | No description available. |