SQL Server 2000: Timeout Expire when I try to insert data from Enterprise manager


My table have about 700,000 record and no primary key.
I try to run this statement to insert record from enterprise manager

"insert into tableA (F1) value ('TEST')"

The Error occur "[Microsoft] [ODBC SQL SERVER DRIVER] Timeout Expire"

Thanks in advance,
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
>My table have about 700,000 record and no primary key.
this is a possibility if the timeout reason, but not alone.

there might be a trigger on the table which performs very badly due to the missing primary key/indexes
Aneesh RetnakaranDatabase AdministratorCommented:
Hi orasaj,
Are you trying it from a workstation...

Ved Prakash AgrawalDatabase Consultant/Performance ArchitectCommented:
Hi you have tried this using Query Analyzer.
if not , please run your statement using Query Analyzer.

for this you need to connect with sql serever and then you run this script.

or you can check using profiler what's going on server when you run this server.
so if any error occured you can saw that in profiler also.

and i think after that you can take decision where is going something wrong..

Good Luck..
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

orasajAuthor Commented:
Hi everybody,

Now I can insert the record with the same statement by use enterprise manager.
But I still don't know what happen!

Thank you everybody,
Orasa J.

maybe you got a timeout specified in the connection you use.
I think default value is something like 10 or 15 (s). And if the operation takes longer, as in your sample because of missing PK, than the timeout
Try finding out what is the value for "timeout" in the connection u are using and increase it or set it to 0. 0 means, that the connection will stay open as long as the operation takes.


Aneesh RetnakaranDatabase AdministratorCommented:
When you insert a value from the EM, these two things will happen
1. An 'INSERT INTO ... '  statement is run first -- This wont give the timeout error
2. After the above statement, it will run a 'SELECT * FROM urTable' -- I think the problem is here
Since it has to return more than 700000, sometimes it may give an error

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Fonts Typography

From novice to tech pro — start learning today.