February 25, 2004 at 8:59 am
I have SQL SERVER install on 5 different servers with the same database (restoring it from a common backup) on two of the 5 I get an ODBC TIMEOUT error in a simple insert to a table. On these two server the DRIVE D DISK WRITE Process is pegging after the insert is executed until the timeout occurs. The database is on drive d the log is on c.
Anyone got any ideas?
Kelley
February 25, 2004 at 9:17 am
Are these five machines identical in hardware and configuration? Do you run database statistics update after the restoration?
February 25, 2004 at 9:33 am
Have you run a dbcc checkdb to rule out physical errors on these two?
February 25, 2004 at 11:53 am
Steve, Yes I have run dbcc checkdb and checktable.
Allen, No the two that fail are compaq servers the three that work are a variety of Dell hardware. What is database statistics update and how do I run that?
Thanks guys,
kelley
February 25, 2004 at 12:38 pm
On QA run
EXEC sp_updatestats
Take a look at BOL "statistical information, updating"
* Noel
February 25, 2004 at 2:53 pm
update stats did not fix it either.
February 25, 2004 at 3:12 pm
How do you perform the simple insert? Do you receive time-out from QA or EM when perform similar insert? Can you post exact error message when time-out occurs?
Can you post hardware configuration on both Compaq and Dell servers?
Do you see any errors in SQL Server errorlog and machine's application and system logs?
What is the query time-out setting in your QA/EM?
February 26, 2004 at 7:27 am
I am using em to perform the INSERT INTO SignOnLog
(userid)
VALUES ('kelley')
the message is [Microsoft][SQL Server ODBC Driver] Timeout expired
one of the two that fail is a windows 2000 sp4
1 gig of ram 2 1 gig process
22 gig usable in a raid 5 config
one that works is a dell laptop 1.6 gig proc 512 ram 40 gig hardrive running xp pro sp 2
no log error messages for sql server.
February 26, 2004 at 7:31 am
What is the query time-out setting in your QA/EM? Verify it from EM --> Tools --> Options --> Advanced tab --> Query Time-out.
February 26, 2004 at 4:24 pm
was set to 0 tried as high as 999 no effect. We did find something interesting today... If the query is executed in QA it takes 1.44 minutes to execute the first time but it does run. subsequently the query works in EM (instantly) and also instantly in QA.
Kelley
Viewing 10 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply