Dylan, I may be wrong but I have always expected that kind of performance when operating outside of Development Cache mode. When you operate in normal conditions the server maintains a cache of all actively used forms and workflow. When you make a change its not written directly to this cache; instead the cache has to be copied, updated with your change and then written back over the production cache. Although your work is performec over the Admin thread the cache update happens on the fast thread(s) (I think) and user actions will always take precedence. When you switch to Development cache mode all of your changes are written directly to the cache and your changes will always take precedence over user actions. If you leave development cache on for any extended period of time you'll start receive complaints of poor performance from your users. Cheers! Eli
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Wheeler, Dylan Sent: Wednesday, January 16, 2008 10:02 AM To: arslist@ARSLIST.ORG Subject: Re: Log SQL in Admin ** Hi Eli, Nope, not in development cache mode. ------------- Dylan Wheeler Production Control Analyst Principal IT Operations Downey Savings & Loan Association, F.A. Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eli Schilling Sent: Wednesday, January 16, 2008 9:38 AM To: arslist@ARSLIST.ORG Subject: Re: Log SQL in Admin ** Dylan, A quick (possibly stupid question) but is your AR Server running in development cache mode? -Eli ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Wheeler, Dylan Sent: Wednesday, January 16, 2008 9:36 AM To: arslist@ARSLIST.ORG Subject: Log SQL in Admin ** Is it possible to log the sql queries the admin tool makes when you modify a form? I'm having major lag issues when I try and update anything in my admin tool and it's frustrating the heck out of me. It takes anywhere from 10 - 60 seconds for it to commit when I hit the save button even on a minor modification to an active link. I believe it's because the remote sql server is bogging down but I can't prove it and I can't get the sql admins to look at it without any proof. I have zero access to the sql server so I'm stuck without something to get them to take a look. Ideas anyone? Windows 2003 ARS 6.3 MS SQL 2000 ------------- Dylan Wheeler Production Control Analyst Principal IT Operations Downey Savings & Loan Association, F.A. Direct: 949.509.4565 Fax: 949.509.7841 Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> This message and any attachments are for the intended recipient(s) only and may contain privileged, confidential and/or proprietary information about Downey Savings or its customers, which Downey Savings does not intend to disclose to the public. If you received this message by mistake, please notify the sender by reply e-mail and delete the message and attachments. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"