SQL Server timing out with particular data

[meherne]

Very odd one. Running SQL Server under XP, with Access front end using ODBC. All works fine, but one particular table has a field Company, nvarchar(50), nulls allowed. It used to be fine, but if I try and add any record (or modify an existing one) with the contents starting 'Tow' it fails with an ODBC timeout. I can't see any significance of this particular word!! Any help much appreciated.

 

[gmmastros]

What is the size of this database?

-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom

 

[SQLSister]

First thing I would wonder is do you have an PK on the table? Access using SQl Server backend does not behave well without a unique record guarantee.

"NOTHING is more important in a database than integrity." ESquared

 

[meherne]

There is a PK. A unique INT Indentity field.
The database is not huge. About 1gb in total (mdf). The table itself is about 20 mixed fields (mainly nvarchar) and 21,000 records.
Just been tinkering and tried adding a record manually and it added fine. Now I can add any record through Access I like with no errors.
I had seemingly nonsensical ODBC timeouts before when I changed some code that shouldn't affect anything. That time I rolled back the code and re-coded it and it was fine. But I think that was on a different record in the database ...

 

[meherne]

Sorry ... in my last post, last sentence, when I said 'Record' I meant 'Table'.