SQL Server Performance

X locks on the SQL table

Discussion in 'General DBA Questions' started by CanadaDBA, Aug 31, 2005.

  1. CanadaDBA New Member

    I have an Access query that appends some rows to a SQL Server table. The problem is that after the data is populated, there are X locks remaining on the SQL table and the developers can't do anything while they are in there. If I kill the process, then they can continue. What's the problem?


    Environment:
    Access 2003 Sp1
    SQL Server 2000 8.00.818 SP3
    Windows 2003

    CanadaDBA
  2. deepakontheweb New Member



    I am not sure but what about if, Trying to populate data in temporary tables and move from there.



    Deepak Kumar

    --An eye for an eye and everyone shall be blind
  3. CanadaDBA New Member

    The code was working until last week that we deploied a new compile of Access application.
    The Access query is not changed. The problem is like if I want to append 100 records, a number of 100 (or more) X locks appears on the table in SQL server. By ending the appendings, there should be a command from Access to SQL Srever that update the indexes and unlock the table but this doesn't happen.

    CanadaDBA

Share This Page