Initial delay on ExecuteSQLQuery - InfoPath Dev Sign in | Join | Help in Qdabra qRules Qdabra Software Product Support (Entire Site) InfoPath Dev InfoPath Dev is dedicated to bringing you the information and tools you need to be successful in your Microsoft Office InfoPath development projects. Home Blogs Forums Photos Downloads InfoPath Dev » Qdabra Software Product Support » Qdabra qRules » Initial delay on ExecuteSQLQuery Initial delay on ExecuteSQLQuery Last post 10-10-2012 11:27 AM by Hilary Stoupa. 3 replies. Page 1 of 1 (4 items) Sort Posts: Oldest to newest Newest to oldest Previous Next 10-09-2012 05:38 PM tenbao Joined on 04-12-2012 Posts 57 Initial delay on ExecuteSQLQuery Reply Contact There seems to be an initial delay when using the ExecuteSQLQuery command for the first time of the day in qRules. Is there any way to run a "warmup" script? 10-09-2012 06:00 PM In reply to Hilary Stoupa Joined on 06-20-2008 Posts 13,297 Re: Initial delay on ExecuteSQLQuery Mark as Not AnswerMark as Answer... Reply Contact Maybe have your form execute a SQL query via a data connection that will only bring back a limited amount of data? Is all of qRules slow the first time the form is used on a given day? Or just ExecuteSQLQuery? Hilary Stoupa 10-10-2012 11:18 AM In reply to tenbao Joined on 04-12-2012 Posts 57 Re: Initial delay on ExecuteSQLQuery Mark as Not AnswerMark as Answer... Reply Contact Actually, it seems to have been a SSO delay issue. Once I turned off SSO, the data returned immediately.Thanks. 10-10-2012 11:27 AM In reply to Hilary Stoupa Joined on 06-20-2008 Posts 13,297 Re: Initial delay on ExecuteSQLQuery Mark as Not AnswerMark as Answer... Reply Contact Wonderful - thanks for the update! Hilary Stoupa Page 1 of 1 (4 items) Copyright © 2003-2019 Qdabra Software. All rights reserved.View our Terms of Use.
Maybe have your form execute a SQL query via a data connection that will only bring back a limited amount of data? Is all of qRules slow the first time the form is used on a given day? Or just ExecuteSQLQuery?
Actually, it seems to have been a SSO delay issue. Once I turned off SSO, the data returned immediately.
Thanks.
Wonderful - thanks for the update!