Anuj, When dealing with this requirement in the past myself I found it was best to both limit the production query set and limit the dataset on production to what is needed for production..if you don't need 4 years of history in production, don't have it..this will increase the performance of production by default. Then you can have your entire data set in reporting.if someone wants to run a 'large' query in production, they will either hit the results limit or not have the data they need because of truncation of old data and need to go to the reporting server anyway. At one position I held we had a 'this month and last' rule in production..62 days worth of ticket data in production..everything else needed to come from reporting.
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Anuj DUA Sent: Wednesday, July 07, 2010 11:34 PM To: [email protected] Subject: Re: Directing Search based reports to another ARS and DB ** Hi Joe, Yes, our user base is very large. We have observed that when large search is fired on our production server, then the performance deteriorates. Hence we want the search to be fired on other ARS and DB (having backup of the production data). Moreover, we are not going for load balancer, we simply want that through workflows we should be able to achieve this. With Regards, Anuj Dua From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joe D'Souza Sent: Wednesday, July 07, 2010 8:03 PM To: [email protected] Subject: Re: Directing Search based reports to another ARS and DB ** Anuj, Why would you want to do something like that? Are the number of concurrent users on your system extremely large? What kind of a usage do you expect in terms of numbers both total and concurrent?? And even if you do have an extremely large user base, are you aware that the creation threads on the ARS are different from the search threads? If you have more than one server pointing to the same database, wouldn't you rather configure them to be a part of a server group? An RPC call sent from a client doesn't get assigned to a Fast or a List thread until the transaction hits the server, so it may not be possible to direct this call from a load balancer configuration to one or the other server based on what kind of a thread the server would assign this call to. Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]]on Behalf Of Anuj DUA Sent: Wednesday, July 07, 2010 4:19 AM To: [email protected] Subject: Directing Searchbased reports to another ARS and DB ** Hello, We have a requirement to directing searchbased reports in remedy to another server. For ex. 1. We have server A and server B 2. Both the server has ARS and DB installed. 3. We want user from server A to fire search to server B (with data coming from server B) The objective of this exercise is to keep the Server A lighter to be used only for creation of ticket and keeping server B for reporting only. Please suggest how to proceed on it. With Regards, Anuj Dua _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
