Tricks or treats in adding SSRS feature to an existing SQL Server 2008 R2 SP2 instance?

• bcaruso 14201

  SSC Veteran

  Points: 272

  More actions

  October 31, 2014 at 5:37 pm

  #294824

  Hello, good folk,

  I'm a newbie DBA and have been tasked with adding SQL Server Reporting Services to an existing SQL Server instance.

  I've searched the forum for a while and run across a few mentions of conflicts when applying SQL Server 2008 R2 SP2 to an installation that already includes the database engine and SSRS. I saw a post from a few years ago mentioning a Windows Hotfix that fights with applying SP2 and keeps SSRS from starting.

  But I'm in the opposite situation, I will be adding the Reporting Services feature to an existing SQL Server 2008 R2 SP2 instance that has multiple databases already running on it. (We do have that KB2661254 hot fix, BTW.) Reporting Services will be used by a new production database on there and, since we have only one production server, the report server and its databases will probably also need to run on this machine. I'll check licensing again to make sure I understand those options.

  Aside from having our application owners check with their vendors to find out if any of the 46 vendor databases will have a conflict with Reporting Services, what other steps can I take to so this implementation is successful? Has anyone added Reporting Services years after the main database installation and found a good strategy?

  Thank you for your help!

  Becky