Hi, I'm Gordon, for those who dont know me I am a nut about a fantastic Operations Management product from Microsoft called MOM.
I am a MOM MVP, Technical Architect, Evangeliser and now Blogger, and will be sharing some of my experiences with MOM 2005, as well as sharing my thoughts on all things Microsoft Management.
I quite often have to carry out a split install of SRS for my OpsMgr deployments, this is normally down to the fact that most SQL admins wont allow IIS to be installed on their SQL boxes.
In these situations I typically have a large database server with the Ops and sometimes Datawarehouse DB's on, and one server with my RMS role. As I normally install the Webconsole on the RMS server to avoid any double hop issues, it always makes sense to me to also install the SRS front end here too, especially as the reporting is now accessible through the console which requires a connection to the RMS anyway.
The tricky part for a lot of people I talk to is getting the SRS split install to work, so I thought I would blog about how you do this step by step:
Installing A SQL Server Reporting Services Split Install
The Root Management Server will contain the front-end SRS reporting function for OpsMgr with the back-end SRS Report and Report temp DB’s being hosted on the same SQL Cluster as the Operations and Data Warehouse DB’s.To enable this functionality a split install of SRS needs to be implemented.The following steps must be taken on the Root Management Server to install the SRS front end component
1. Make sure IIS is installed locally on the server.
2. Locate the SQL Install media and click on setup.exe
3. Click next on the “Registration Information” page
4. On the components to install page check the Reporting Services box and click next
5. On the “Instance Name” tab choose the default instance
6. On the “Service Account” tab choose Use a domain user account that has full access to the Data Warehouse (I usually use the SDK or data reader\writer account), make sure the start Reporting Services at the end of setup tab is checked and click next
7. On the “Report Server Installation Options” and “Error and Usage Report Settings” tabs click
8. On the “Ready To Install” tab click install to finish
9. When the install completes please run Service Pack 2 to update the components to the necessary service pack level
The next step is to configure SRS so it installs the report DB’s on the remote SQL Server
1. Go to Start, All Programs, Microsoft SQL Server 2005, Configuration Tools, Reporting Services Configuration
2. On the “Configure Report Server” screen click connect to access your local SRS instance
3. Click on the “Database Setup” tab on the left hand side, click Connect, in the “SQL Server Connection Dialog” screen specify the SQL Instance that the SRS DB’s will be installed too, leave Current User – Integrated Security selected as the credentials type and click OK 4. Next click the “New” button and leave the defaults but make sure “Create the report server database in SharePoint Integrated Mode” is unchecked, next click OK to create the new DB’s 5. Next, go to the “Report Server Virtual Directory” tab and check the box “Apply default settings” next to the New Button, the click apply
6. Go to the “Report Manager Virtual Directory” tab and check the box “Apply default settings” next to the New Button, the click apply
7. Go to the “Web Service Identity” tab and click apply
8. Click on the “Database Setup” tab again and on the left hand side and click the Connect button, in the “SQL Server Connection Dialog” screen specify the SQL Instance that the SRS DB’s are now installed too, leave Current User – Integrated Security selected as the credentials type and click OK to connect, now choose ReportServer in the database name pull down box and click apply
9. Finally, to test that the above steps have been carried out correctly, open up a browser and navigate to http:\\localhost\reports, if everything has been successful then you should see the reporting services home page.