Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dbMartiN
Starting Member
26 Posts |
 Posted - 2004-09-09 : 05:28:03
|
| Hello,I have an application on one of my servers and the database on another. Once in a while I get this error message when I am working in the application...RDO Database System ErrorError 40002: S1T00: [Microsoft][ODBC SQL Server Driver] Timeout expiredRDO Messages:0: S1T00: [Microsoft][ODBC SQL Server Driver] Timeout expiredRDO Statement:delete from user where id = 2650Why is this happening and what is the solution to fix this problem??The application is very slow...Grateful for all help!Kind regardsMartinThanks for your help! |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2004-09-09 : 08:52:33
|
| 1...caused by....locking as a result of the activities of other users....use PROFILER to see what long running activities at interfering with this.2...to increase the interval between occurrances....increase the 'timeout' parameter....available at command or connection level...default is about 30seconds.3...index the user table on the id column4...re very slow app....'examine execution plans + code' and remove 'table/index' scans (by appropraite query/db tuning) and from the code remove 99.99% of cursors. |
 |
|
|
dbMartiN
Starting Member
26 Posts |
Posted - 2004-09-14 : 02:57:46
|
| Hello again...Thanks for your answers! I have a few questions though :)1. Is this because of too many users in the application at the same time? How do I use PROFILER?2. Can I increase the "timeout" parameter in SQL Server or must I do it in the application?Grateful for all help I can get.../MartinThanks for your help! |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-09-14 : 08:10:12
|
| It's probably not caused by too many users. It's more likely to be caused by bad database design or a bad stored procedure. Search the forum for locking. You can also look at www.sql-server-performance.com . In addition, if you go to Microsofts web casts area, there is a really good web cast on lock management.You increase the timeout on the application. It should be handled in your data connection component.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
dbMartiN
Starting Member
26 Posts |
Posted - 2004-09-15 : 05:17:00
|
| Hello again...Thanks for the reply!So this has nothing to do with the properties on the SQL Server, it is in the application connect component the "timeout" parameter is to be setup?Somtimes when we try to reach the application we get this error:"The system cannot connect to the application server. Contact your system administrator.Automation errorObject server is stopping when OLE service contacts it"Why is this happening and what is the solution??Kind regardsMartinThanks for your help! |
|
|
|
dbMartiN
Starting Member
26 Posts |
Posted - 2004-09-15 : 05:17:21
|
| Hello again...Thanks for the reply!So this has nothing to do with the properties on the SQL Server, it is in the application connect component the "timeout" parameter is to be setup?Somtimes when we try to reach the application we get this error:"The system cannot connect to the application server. Contact your system administrator.Automation errorObject server is stopping when OLE service contacts it"Why is this happening and what is the solution??Kind regardsMartinThanks for your help! |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-09-15 : 07:27:18
|
| ??? If you're having this error also, you need to have your network and server support group look into this. It sounds like you have network issues or possibly a bad NIC card.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
Timeout expired