Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Combing RS databases with other production databases Expand / Collapse
Author
Message
Posted Friday, February 1, 2013 12:49 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, March 27, 2013 10:24 AM
Points: 16, Visits: 98
Curious what the industry norm is. Can / should i put my report databases on the same server / instance as other production databases ?

In the past my company had created a new server / instance for every item that required sql, after combining some of the smaller ancillary items, im looking at combining the report server also ?
Post #1414816
Posted Monday, February 4, 2013 1:33 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Saturday, November 1, 2014 6:54 AM
Points: 5,221, Visits: 5,118
I have not seen any issues in our environments where the RS and RSTempDB are on the same server as production.

We have SSRS installed on a dedicated box, but the DB is on the main prod engine server.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1415159
Posted Monday, February 4, 2013 3:49 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 2:43 AM
Points: 279, Visits: 232
Really depends on your resources, you could have a separate server for each aspect or 1 server for all.
I've always had at least 2 anywhere i've worked 1 for live and 1 for reporting/backup so the working environments(reporting) never had any direct interaction with the performance of the live system. I think in most cases this would be the more reasonable setup.

My last job we were adding a 3rd for an SSAS cube in the latest SQL server version but it was a big cost and in my opinion it wasn't really nessesary as it would make the reporting server redundant.
(better to have upgraded the 2nd instead for the cost).


Regards
ld

Stoke-on-Trent
United Kingdom

If at first you don't succeed, go to the pub and drink away your current thought plan.
Post #1415210
Posted Tuesday, February 5, 2013 5:03 PM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, November 18, 2014 10:48 PM
Points: 482, Visits: 889
If your SSRS server is querying the operational database (OLTP) directly then I would put them on different servers. SSRS will use the OLTP server to process queries but other resources for running the SSRS website and it's own database would take away resources from your production machine if they were on the same machine. Likewise keeping the SSRS machine as a client of the OLTP server just like any other client e.g. application users, keeps it independent in the case of server issues or required maintenance or upgrades.

On the other hand if you have a datawarehouse and OLAP cubes then I like to put SSRS on the same machine, unless you are completely familiar with Kerberos or you are a security guru and have your own authentication solution. If you don't run Kerberos in your network then double hop is the biggest pain in the backside.
Post #1416168
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse