Reporting Services Deployment Options

determine your database deployment options first (see database deployment options docid\ h8xefagya8j 286x6q747 ), and then your operations console deployment options (see operations console deployment options docid\ mqkjufzjjfg607d5u6l7x ) then determine your reporting services deployment options in all of the reporting services deployment options below, note the following you can substitute any of the database deployments described in database deployment options docid\ h8xefagya8j 286x6q747 for the database deployments in the figure for example, for the database engine instance shown in option r5 below, you could substitute option d1, option d2a/b, option d3, and so on for that database engine instance you can substitute any of the operations console deployments described in operations console deployment options docid\ mqkjufzjjfg607d5u6l7x for the operations console deployments in the figure for example, for the single application server shown in option r5 below, you could substitute option oc3 for that application server the report database can reside on a separate database instance, or on a database instance on a separate server the microsoft ssrs instance can run on the database server, application server, or on a separate server the reporting feature should be installed on the microsoft ssrs server we recommend using either option r1 or option r2 option r1 multiple microsoft ssrs instances on the same database server (best practice) this deployment is the most common and recommended for simplicity and security the advantage of this deployment is that you have a reporting feature for production that is separate from the development environments example of multiple microsoft ssrs instance on one database server option r2 separate microsoft ssrs instances and a separate database server (best practice) use this deployment to keep the reporting separate between the production and development environments example of separate microsoft ssrs instances and a separate database server option r3 separate microsoft ssrs instances use this deployment to keep the reporting separate between the production and staging/uat environments example of separate microsoft ssrs instances option r4 multiple microsoft ssrs instances on a separate report server this deployment is recommended if you need to maintain your database in a locked down environment and keep it separate from the development environment we also recommend this deployment if you already have a server with a microsoft ssrs instance for other applications example of a multiple microsoft ssrs instances on a separate report server option r5 single microsoft ssrs instance on one database server we do not recommend using this deployment unless you are setting up a demo environment example of a single microsoft ssrs instance on one database server