Hello all, First off, we are using AR Server 6.3 patch 22. We have a escalation that automatically moves our incident tickets from resolved to closed after 48 hours of the ticket being resolved. We recently resolved around 40,000 tickets a couple of days ago not thinking of this escalation. Well, today, the escalation brought Remedy to a halt as the escalation took over all resources.
If I remember the docs correctly, the arsystem uses the admin queue for all database connections correct? And if I also remember correctly, you can only have one admin queue. Why is this limitation in Remedy? And if there isn't a limit, what would be the suggested number? We have a server group of two servers and one database, we're thinking about using one server for all escalations and another that the users can use so that if this happens again, only the escalation server will be bogged down and not the server everyone is using. Is this a valid setup for a server group? Also, is there some way to force Remedy to say only resolve a limited number of tickets in a go? Like a SQL Limit statement? I'm sure we are not the only ones who have ran into this problem, but how do you guys handle that many tickets in a go? -- "A fool acts, regardless; knowing well that he is wrong. The ignoramus acts on only what he knows, but all that he knows. The ignoramus may be saved, but the fool knows that he is doomed." Robert Halstead _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
