Re: help: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

From: tajeshwar (tajeshwars_at_grapecity.com)
Date: 08/04/04 

Date: Wed, 4 Aug 2004 11:03:29 +0530

thanks Vikram

    But I guess the problem is somewhere before itself not even in
transaction...
    Actually we are putting records in a temp table which qualify according
to our business logic.
    now these are 2.5 million records. These all have to be finally moved
to our actual physical
    table in a transaction.... The thing is failing in preparation of this
temp table only and
    code fails very much even before transaction starts. I guess it is not
able to take the load or some problem related to
    duration of connection. coz when i run the same using query analyzer it
kept on running for 5 days... Though we stopped it then...
    And using sqlprovider for .NET it's failing in around 17-18 hours and
that's a continous pattern. I think the problem is
    with .NET SQL Provider which is breaking connection.

    Hope now u get a better picture of my problem.....

Regards,

Tajeshwar

"Vikram Jayaram [MS]" <vikramj@online.microsoft.com> wrote in message
news:8onq5IZeEHA.676@cpmsftngxa10.phx.gbl...
>
> Run this query locally from query analyser to see if it goes through.
> Another thing is, unless really needed pls dont use lock hints as SQL
> Server has dynamic and inbuilt lock mgmt.and will allot and deallocate
> locks on it's own. Finally pls have clustered indexes as they improve
> performance.
>
> Vikram Jayaram
> Microsoft, SQL Server
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
>
>

Relevant Pages

  • Re: controlling lock order in transactions
    ... > and the trigger issued a rollback your commit or rollback would error. ... > Andrew J. Kelly SQL MVP ... >> taken) for the duration of the transaction. ... >> find in the clients sp that could be causing the dead lock is the join on ...
    (microsoft.public.sqlserver.programming)
  • Re: controlling lock order in transactions
    ... Andrew J. Kelly SQL MVP ... > ROLLBACK TRANSACTION; ... > find in the clients sp that could be causing the dead lock is the join on ...
    (microsoft.public.sqlserver.programming)
  • Re: Transaction isolation levels
    ... SELECT 'X' INTO #TEMP ... locks the row in table TICKETS until the entire transaction has ... The lock taken out on TICKETS will be a shared lock ... that under the default isolation level will be released. ...
    (comp.databases.ms-sqlserver)
  • Re: Transaction isolation levels
    ... SELECT 'X' INTO #TEMP ... locks the row in table TICKETS until the entire transaction has ... lock the rows in the TICKETS table. ...
    (comp.databases.ms-sqlserver)
  • Re: all about transaction
    ... begintrans is directly affecting the tables but sql server is maintaining all ... this transaction log is a physical file in the server or itz ... >>using readuncommitted or reading with no lock they will see the old values. ...
    (microsoft.public.sqlserver.programming)