July 22, 2014 at 8:36 am
I have two reporting services environments. First one is a native running on the same sql 2008r2 box using the 2008r2 box for it's backend. The box is a monster 256 gig or RAM and 64 core. The other box I have is a 2008 server running reporting server on same box as SQL Server backend also hosting Sharepoint. The share point is 2007 and this reporing server is running sharepoint integrated mode. For licensing reasons I was going to move the 2nd instance of reporting server (2008 version), which is lightly used and move it to the same box as a 2nd instance and governor it (all of this is enterprise edition). Does this seem feasible. From a performance standpoint I can stand up the 2nd instance pretty easily without impact. More of and issue of sharepoint configuration time than anything.
THanks
July 23, 2014 at 11:02 pm
tcronin 95651 (7/22/2014)
I have two reporting services environments. First one is a native running on the same sql 2008r2 box using the 2008r2 box for it's backend. The box is a monster 256 gig or RAM and 64 core. The other box I have is a 2008 server running reporting server on same box as SQL Server backend also hosting Sharepoint. The share point is 2007 and this reporing server is running sharepoint integrated mode. For licensing reasons I was going to move the 2nd instance of reporting server (2008 version), which is lightly used and move it to the same box as a 2nd instance and governor it (all of this is enterprise edition). Does this seem feasible. From a performance standpoint I can stand up the 2nd instance pretty easily without impact. More of and issue of sharepoint configuration time than anything.THanks
from a licensing perspective, I do not think that what you are planning will actually change anything unless you are planning to completely remove SSRS from the SharePoint server. That assumes that the configuration and content databases for SharePoint 2007 are on the SharePoint server.
This also assumes that you are "happy" that the new instance of SSRS does not need to be integrated with SharePoint.
July 24, 2014 at 6:51 am
the intention was to remove the reporting server from the sharepoint box entirely and have this on the second instance. I get sharepoint integrated is better, but not my choice. This is right now a way to address licensing issue they have.
July 24, 2014 at 10:21 pm
tcronin 95651 (7/24/2014)
the intention was to remove the reporting server from the sharepoint box entirely and have this on the second instance. I get sharepoint integrated is better, but not my choice. This is right now a way to address licensing issue they have.
Are there any other bits of SQL Server installed onto the SharePoint server (e.g. the RDBMS for SP config/content database) ?
July 25, 2014 at 4:05 am
Note you can't use resource governor on the reporting service itself, only connections to the database.
So report rendering/processing etc will be ungoverned.
It's also not instance aware so you might not get the results you expect.
If possible, I'd create a VM on the big host server and install reporting services on that. At least you can limit the CPU then.
Of course, if it's only lightly used then probably not an issue 🙂
Like happycat, I can't see how this fixes a licensing issue if SQL remains on the second box.
Cheers
Gaz
July 25, 2014 at 6:52 am
The new box is proc licensed, the one I am moving from is CA licensed and with Sharepoint hitting the reporting server on that box MS says have to have a SQL license for every user. Make 2nd instance on new box that issue goes away due to proc license
July 25, 2014 at 8:48 am
Cheers, that makes sense, but are the sharepoint databases going to remain on the second box?
Same issue if they are?
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply