cmilkosk
Posts: 6
|
| Posted: 08/27/2008, 7:23 AM |
|
All,
Using the application builder, I created a default search form with a grid. The database is a SQL Server 2000 database and I'm connecting to it with a System DSN on a different server.
When I load the page, it comes back at me with the search form, but the grid fails to display - replaced with:
Error: [Microsoft][SQL Native Client]Query timeout expired (Microsoft OLE DB Provider for ODBC Drivers)
How do I increase the timeout? The timeout to me is way too short right now. I know that a query to the server locally on the same database would take a little over a minute.
Thanks,
Chris
|
 |
 |
wkempees
Posts: 1679
|
| Posted: 08/27/2008, 2:37 PM |
|
Do you really need/want the Grid to be filled upon first entry, before search parameters are supplied by user?
I do now have the timeout setting for you, but would advice to let the grid NOT select upon a blank search, by deafulting the search value to an 'impossible' value, you can have empty grid.
My2ct
Walter
Oh and btw I googled it for you and found this:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3753564&SiteID=17
http://www.dbforums.com/showthread.php?t=1617966
_________________
Origin: NL, T:GMT+1 (Forumtime +9)
CCS3/4.01.006 PhP, MySQL .Net/InMotion(Vista/XP, XAMPP)
if you liked this info PAYPAL me: http://donate.consultair.eu
|
|
|
|
cmilkosk
Posts: 6
|
| Posted: 08/28/2008, 5:56 AM |
|
Quote wkempees:
Thanks for the response.
RE: do I need the Grid filled upon first entry - No, but the timeout still appears to be too short even if I avoided the grid. It feels like it is set to 30 seconds. My database is pretty big and a query could typically run a little over that. Maybe I need to tweak a little on the database to increase performance, but I'd still like to know the right way to adjust the timeout.
RE: what you googled - thanks for checking. I probably should've posted this, but I googled for the timeout settings as well, and tried adding something like connection.CommandTimeout in all of the spots where I believed a query to the ODBC database was being made (and of course using the right object name instead of "connection"). Whenever I made the change, it didn't seem to take effect. The timeout remained at around 30 seconds.
Any thoughts?
Thanks,
Chris
|
|
|
|
cmilkosk
Posts: 6
|
| Posted: 08/29/2008, 6:57 AM |
|
I think I figured it out finally. I thought I tried this, but I must have missed right place to put the CommandTimeout property.
In Classes.asp, I went to line 3316 where an ADODB.Command object was being created. I then placed this before the Command.Execute(Command) operation:
Command.CommandTimeout = 300
And that appears to have done it. It sets the timeout to 5 minutes which may seem crazy to some, but it is fine for me.
Chris
|
|
|
|
wkempees
Posts: 1679
|
| Posted: 08/29/2008, 2:39 PM |
|
I am no ASP ADODB guy, but I hope one of the others will show you a way of doing this in such a way that it is active like that only in the procedure you need it in.
In comparison, in PhP we can (temporarily) overrule the PHP timeout, without affecting general operation.
Well done, meanwhile.
Walter
_________________
Origin: NL, T:GMT+1 (Forumtime +9)
CCS3/4.01.006 PhP, MySQL .Net/InMotion(Vista/XP, XAMPP)
if you liked this info PAYPAL me: http://donate.consultair.eu
|
|
|
|
|
