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

Posted on 2006-03-19
Last Modified: 2013-12-03

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,
Question by:orasaj
    LVL 142

    Expert Comment

    by:Guy Hengel [angelIII / a3]
    >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
    LVL 75

    Expert Comment

    by:Aneesh Retnakaran
    Hi orasaj,
    Are you trying it from a workstation...

    LVL 11

    Expert Comment

    by:Ved Prakash Agrawal
    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..

    Author Comment

    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.
    LVL 7

    Expert Comment


    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.


    LVL 75

    Accepted Solution

    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

    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Join & Write a Comment

    I recently came across an interesting Question In EE ( and was puzzled about how to achieve that using SSIS out of the box tasks, which was i…
    Introduction In my previous article ( I showed you how the XML Source component can be used to load XML files into a SQL Server database, us…
    Via a live example, show how to shrink a transaction log file down to a reasonable size.
    Excel styles will make formatting consistent and let you apply and change formatting faster. In this tutorial, you'll learn how to use Excel's built-in styles, how to modify styles, and how to create your own. You'll also learn how to use your custo…

    754 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    21 Experts available now in Live!

    Get 1:1 Help Now