SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Combing RS databases with other production databases


Combing RS databases with other production databases

Author
Message
cjbaum
cjbaum
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
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 ?
anthony.green
anthony.green
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10029 Visits: 6303
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
When a question, really isn't a question - Jeff Smith
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


ldorian81
ldorian81
SSC-Addicted
SSC-Addicted (430 reputation)SSC-Addicted (430 reputation)SSC-Addicted (430 reputation)SSC-Addicted (430 reputation)SSC-Addicted (430 reputation)SSC-Addicted (430 reputation)SSC-Addicted (430 reputation)SSC-Addicted (430 reputation)

Group: General Forum Members
Points: 430 Visits: 323
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.
davoscollective
davoscollective
SSC Eights!
SSC Eights! (915 reputation)SSC Eights! (915 reputation)SSC Eights! (915 reputation)SSC Eights! (915 reputation)SSC Eights! (915 reputation)SSC Eights! (915 reputation)SSC Eights! (915 reputation)SSC Eights! (915 reputation)

Group: General Forum Members
Points: 915 Visits: 1004
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search