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 |
|
psheperia
Starting Member
1 Post |
 Posted - 2005-11-29 : 10:44:28
|
| HiI've got a database in SQL Server 2000 on Windows Server 2003 which appears to be okay from SQL Enterprise Manager and from SQL Query Analyser but which has a problem with one particular table when connected to from a VB DLL using ADO. The queries do either a select or an insert - the latter is via a stored procedure. Once the failure happens, any other queries generate a -2147217871[Microsoft][ODBC SQL Server Driver]Timeout expired.If I delete the table and recreate it all is well. If I run an integrity check nothing shows up. I've tried deleting the indexes and that made no difference either. SQL Server is patched up to SP4 and ADO is from the MDAC 2.8. VB is version 6 Enterprise with SP6. None of the other databases in the instance exhibit the problem and they're all structured in an identical way. The table is quite large but we've got much larger one's using the same procedures and they don't have a problem. Also, if I restore a backup of the problem database onto another machine the problem shows on the other machine too.Any ideas anyone? |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2005-11-29 : 12:08:51
|
| Can you post the DDL, SP and sample input data?....hiding confidential info by obfuscation. |
 |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2005-11-29 : 13:19:25
|
quote:
Once the failure happens, any other queries generate a -2147217871[Microsoft][ODBC SQL Server Driver]Timeout expired.
Can you post more info on the initial failure you allude to above?Paul RandalLead Program Manager, Microsoft SQL Server Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
|
|
|
|
|
|
Strange Table Connection Problem