November 8, 2017 at 12:57 pm
I understand reporting service is a separate download for SQL 2017.
I go to the download site there is only one download. How can I know which edition is the SSRS?
Is it standard, developer or Enterprise?
If we install the reporting service on two servers for scale out purpose, do we need buy licenses for both servers?
November 8, 2017 at 2:20 pm
sqlfriends - Wednesday, November 8, 2017 12:57 PMI understand reporting service is a separate download for SQL 2017.
I go to the download site there is only one download. How can I know which edition is the SSRS?
Is it standard, developer or Enterprise?If we install the reporting service on two servers for scale out purpose, do we need buy licenses for both servers?
They still don't have anything documented on any of this...I know people have complained. And if you check the features for 2017 documentation, the SSRS link still just points back to 2016. So nothing official.
Just before the separate download went live, there was an MS blog that said the SSRS edition was tied to the edition of SQL Server. I can't find that blog right now but that part I did remember. So once you point to instance to use for the databases, it would know the edition.
It used to be each SSRS server needed a license with scale out but without any documentation..who knows. Have you contacted MS or the vendor who is handling your MS Licensing? I'd be curious to know myself.
Sue
November 8, 2017 at 2:32 pm
Sue_H - Wednesday, November 8, 2017 2:20 PMsqlfriends - Wednesday, November 8, 2017 12:57 PMI understand reporting service is a separate download for SQL 2017.
I go to the download site there is only one download. How can I know which edition is the SSRS?
Is it standard, developer or Enterprise?If we install the reporting service on two servers for scale out purpose, do we need buy licenses for both servers?
They still don't have anything documented on any of this...I know people have complained. And if you check the features for 2017 documentation, the SSRS link still just points back to 2016. So nothing official.
Just before the separate download went live, there was an MS blog that said the SSRS edition was tied to the edition of SQL Server. I can't find that blog right now but that part I did remember. So once you point to instance to use for the databases, it would know the edition.
It used to be each SSRS server needed a license with scale out but without any documentation..who knows. Have you contacted MS or the vendor who is handling your MS Licensing? I'd be curious to know myself.Sue
Is this the blog you're talking about Sue? https://blogs.msdn.microsoft.com/sqlrsteamblog/2017/10/02/sql-server-2017-reporting-services-now-generally-available/
In the blog, it states:
To run SSRS 2017 in production, just enter your SQL Server 2017 product key during setup.
So, one could (safely?) assume that SSRS will know what type of version it is, due to the licence key being used.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 8, 2017 at 2:49 pm
Does that mean SSRS 2017 edition is decided by the edition of the SQL server database engine edition?
Reporting service is now looks like every body can download it, I wonder if the license changed or not?
I cannot find any license document for SQL server 2017.
No I have not checked with Microsoft yet.
November 8, 2017 at 2:51 pm
Thom A - Wednesday, November 8, 2017 2:32 PMSue_H - Wednesday, November 8, 2017 2:20 PMsqlfriends - Wednesday, November 8, 2017 12:57 PMI understand reporting service is a separate download for SQL 2017.
I go to the download site there is only one download. How can I know which edition is the SSRS?
Is it standard, developer or Enterprise?If we install the reporting service on two servers for scale out purpose, do we need buy licenses for both servers?
They still don't have anything documented on any of this...I know people have complained. And if you check the features for 2017 documentation, the SSRS link still just points back to 2016. So nothing official.
Just before the separate download went live, there was an MS blog that said the SSRS edition was tied to the edition of SQL Server. I can't find that blog right now but that part I did remember. So once you point to instance to use for the databases, it would know the edition.
It used to be each SSRS server needed a license with scale out but without any documentation..who knows. Have you contacted MS or the vendor who is handling your MS Licensing? I'd be curious to know myself.Sue
Is this the blog you're talking about Sue? https://blogs.msdn.microsoft.com/sqlrsteamblog/2017/10/02/sql-server-2017-reporting-services-now-generally-available/
In the blog, it states:
To run SSRS 2017 in production, just enter your SQL Server 2017 product key during setup.
So, one could (safely?) assume that SSRS will know what type of version it is, due to the licence key being used.
Thanks Thom. Not the same but that one seems better. There was some blog that used similar terminology about it being "tied to the edition of SQL Server".
I would think the license key would provide that - that's more info than they first had. The registry has the edition as well which is what I was originally thinking .
It's irritating that they released a product but don't have the documentation anywhere yet. Unfortunately not surprised though.
Sue
November 8, 2017 at 2:54 pm
sqlfriends - Wednesday, November 8, 2017 2:49 PMDoes that mean SSRS 2017 edition is decided by the edition of the SQL server database engine edition?Reporting service is now looks like every body can download it, I wonder if the license changed or not?
I cannot find any license document for SQL server 2017.No I have not checked with Microsoft yet.
SSRS was already available on Express, Standard, Enterprise and Developer, and it was always tied to the version and licence that your data engine had. That has not changed by the looks of that blog.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 8, 2017 at 2:57 pm
sqlfriends - Wednesday, November 8, 2017 2:49 PMDoes that mean SSRS 2017 edition is decided by the edition of the SQL server database engine edition?Reporting service is now looks like every body can download it, I wonder if the license changed or not?
I cannot find any license document for SQL server 2017.No I have not checked with Microsoft yet.
It would seem that the edition is determined by the database engine edition. That's what it seems from what I had read before and then this last post from Thom.
When they first were going the direction of the separate download available to everyone, I was wondering about licensing as well. That's why I kept trying to track it but they didn't provide any solid information. And now that it has been announced and released to everyone, they still don't provide the documentation. Frustrating.
Sue
November 8, 2017 at 3:01 pm
We install two reporting services servers. Only reporting service on the server, one is used as scaled out server.
They both connect to report dbs on another database engine instance server which is an enterprise edition.
So I guess reporting service edition is decided by the database server which hosts the report databases.
November 8, 2017 at 3:07 pm
sqlfriends - Wednesday, November 8, 2017 3:01 PMWe install two reporting services servers. Only reporting service on the server, one is used as scaled out server.
They both connect to report dbs on another database engine instance server which is an enterprise edition.
So I guess reporting service edition is decided by the database server which hosts the report databases.
Thanks posting that - you normally wouldn't be able to scale out if it wasn't recognized as Enterprise. And that's what it should be based on what Thom and I had both found.
Maybe you could test out all the other pieces (like data driven subscriptions), document it and sell it to Microsoft since they didn't get around to doing the documentation yet 🙂
Sue
November 8, 2017 at 3:45 pm
sqlfriends - Wednesday, November 8, 2017 3:01 PMWe install two reporting services servers. Only reporting service on the server, one is used as scaled out server.
They both connect to report dbs on another database engine instance server which is an enterprise edition.
So I guess reporting service edition is decided by the database server which hosts the report databases.
Although kind of what I said, I will admit, I was under the assumption that your SSRS and Data Engine are hosted on the same Server. If they are hosted on separate servers, then each server will have their own Licence. If the server you use for SSRS only has a Standard licence, then SSRS will be standard edition; of course the inverse could be true too and you might use a Standard licence on your DB Engine and Enterprise on your SSRS Server. You can't use the same licence you used on your data engine for SSRS, if it's on a different machine (that would be breaking your licence agreement); you need a licence for each machine if you're hosting SSRS on a different machine to your data engine, so that's 2 set's of licences.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 8, 2017 at 4:04 pm
Thanks, I know in previous version of SQL, as long as Reporting service is installed, that server needs the licenses.
So in our case it does need two to cover the two servers. I am just curious if this still the case or not, esp, the reporting service can be downloaded by anyone.
Also if in our case only reporting service is installed, separate from database server, you said that edition is decided by the SSRS edition.
This goes back to my original question, how can I find out what edition it is for the SSRS since there is only one installation file to download.
https://www.microsoft.com/en-us/download/details.aspx?id=55252
November 8, 2017 at 5:08 pm
After reading this page https://docs.microsoft.com/en-us/sql/reporting-services/install-windows/install-reporting-services
, I realized for install SSRS edition, there is a drop down for evaluation or developer edition.
And also there is a production key for standard or enterprise.
Since our case is database engine is on a separate server, so I guess if I put a product key that is from Enterprise database engine, then the SSRS will be enterprise,
if the product key is from a standard edition of database engine install file, then the SSRS will be standard. Am I correct?
Thanks
November 8, 2017 at 5:14 pm
sqlfriends - Wednesday, November 8, 2017 5:08 PMAfter reading this page https://docs.microsoft.com/en-us/sql/reporting-services/install-windows/install-reporting-services, I realized for install SSRS edition, there is a drop down for evaluation or developer edition.
And also there is a production key for standard or enterprise.
Since our case is database engine is on a separate server, so I guess if I put a product key that is from Enterprise database engine, then the SSRS will be enterprise,
if the product key is from a standard edition of database engine install file, then the SSRS will be standard. Am I correct?Thanks
Yes, that's what I said, the version of SSRS will be relative to the key. But you still need a separate licence to that of your DB engine.
Also, it's worth noting that making it a separate install hasn't really changed much. You could just download the SQL Server ISO and install the SSRS service only, which could be downloaded by anyone. It just means that the ISO doesn't contain SSRS now.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 8, 2017 at 5:26 pm
Thanks, we bought volume license and software assurance.
we just count licenses by cores.
The product key is really only one for standard , one for enterprise.
November 20, 2017 at 6:12 am
You need to be aware there are two separate Reporting Services products available for SQL 2017:
* SQL Server Reporting Services
* PowerBI Reporting Services
SQL Server Reporting Services is the one we know from many previous SQL Server editions and which of course we love unconditionally.
In previous versions of SQL RS you could choose your RS instance name and install multiple RS instances on the same server. With the SQL 2017 version of SQL RS you do not get these choices and always have an instance name of SSRS. The installer will let you install either the Developer Edition or Evaluation Edition without a PID key, but for Standard or Enterprise editions you need a PID key. You can get the PID key from your SQL Media, in the \x64\DefaultSetup.ini file.
PowerBI Reporting Services brings a host of new features into the Reporting Services world. As well as traditional Report Builder or VS, you can author reports in PowerBI Desktop or in Excel. These reports can be published on PowerBI Server and shared around your organisation. On the RS Web GUI you get a PowerBI branded set of pages, but otherwise it is the same as SQL RS. However, you can replace the PowerBI branding with your own organisation branding.
PowerBI RS is a replacement for SQL RS and can replace any SQL RS installation from SQL2008 onwards (providing you are on an acceptable version of Windows). The instance name is fixed at PBIRS. As with SQL RS, you can install either Developer Edition or Evaluation Edition without a PID key, but otherwise you need a PID. Getting the PID for PowerBI is complicated. If you have a Select Agreement with Service Assurance, then you can get to your PID key. You need to get your Select Agreement administrator to view the entry for SQL Server 2017, then click on the Downloads tab. Somewhere in the middle of the verbiage that gets displayed is your PowerBI PID. If you do not have the right software agreement then you can purchase PowerBI separately.
If you do install PowerBI RS and connect it to an existing RS database you get a warning you have gone down a one-way street. The database automatically gets updated for PowerBI RS and can no longer be used with SQL RS.
At my place we run a RS cluster to improve availability of the RS service, and it was a simple job to install and configure PowerBI RS and swap the service into the cluster in place of the old SQL 2014 RS service.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply