October 20, 2006 at 7:18 am
There is nothing wrong with the components you're using to access your sql server, we use the same basic setup with hundreds of users. The time out expired problem is most likely because of things like poorly written queries, lack of stored procedures, inadequate hardware, etc.
If you can run the software locally, you need to be looking at things like performance monitoring.
For the heck of it, I would certainly upgrade the ADO and MDAC to whatever MS's latest is. Just turn on Windows updates. ADO is up to 2.9 or so, and there have been a lot of enhancements, especially in security since your version was written.
Student of SQL and Golf, Master of Neither
October 20, 2006 at 8:20 am
I wouldn't be so quick to judge this on poor equipment or queries. While it may very well be the case, there are many times data needs to be aggregated and massaged before being returned to the client.
That said, what is the command timeout set at in your VB6 code? By default, ADO's timeout is 15 seconds. Try increasing this to 30 or 60 seconds to relieve your problem. If you're using a new server, rebuild the indexes and stats to ensure some more effective execution plans.
Hope this helps,
J²fi
Viewing 2 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply