Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
learntsql
524 Posts |
 Posted - 2009-10-28 : 03:06:23
|
| Hi,How to configure report manager/report server for multiple projects/teams accessing same physical machine/instance of SQL.If i configure like this how could be the maintanance for following activities:-->Security-->Accessing-->Subscription-->reportserver database(backup and restore)-->and any other settingsrelated to report managerPlz. guide me.Should i install different instanses for each team/projects or any other alternatives.ThankQ. |
|
|
JCirocco
Constraint Violating Yak Guru
392 Posts |
Posted - 2009-10-28 : 08:13:55
|
| It is actually a complicated answer to what appears to be something so simple.Most important is what the end users will require. You can have multiple instances for development so they can view as the users would but if the users will be accessing reports from all groups, then a single production Report Server will probably be best.Also important is your source code control so multiple peolple not working on the same report RDL making changes.I belong to the group that believes Developers should not be the ones to move applications/reports into a production environment (unless it is a very small IT department). So I would have multiple instances by development manager and then a single instance for production. You can even have an intermediate instance where users can sign off on accuracy or they can be given access to development. This way you have a seperate server database to back up as well as seperate logs you can erview for report usage.If you do not have an intermediate instance for user testing/validation, then an operations person should do the move of the new report to the production instance using the report manager to save the code from test (using the Edit button under the reports properties on the test instance) and then installing it on the production instance (using the update button under properties on the production instance). If you have the intermediate instance it would be your choice on who moves to the test instance. I still believe it is best NOT to have the developer do it.In the above model you really only need to have folder security for the production folders, preferably using Active Directory groups. The development instances can have a single group at the root folder for that particular development team.JohnIt's a small world (but I wouldn't want to paint it) |
 |
|
|
|
|
|
Report Manager issue