SQL Server Performance

High Load data replication locking issues

Discussion in 'Performance Tuning for SQL Server Replication' started by kuffy, Mar 17, 2006.

  1. kuffy New Member

    Hi,
    I'm currently encountering a problem with transactional replication on SQL 2K. An application needs to drop and recreate tables nightly, that are necessary for replication. These tables (only a handfull) have ~250000 records in them. These tables are also required for replication, so I've scripted seperate drop, recreate and initialize t-sql scripts, that are executing within DTS packages.

    Due to continuous activity with the application and database, I'm currently encountering irregular table lock timeouts in MSSQL, which is causing the application to fail. I have checked that concurrent snapshots are set, and have set each agent to use a seperate agent each. I have also extended the timeout on all 3 agents. The distributer is local.
    Does anyone have any suggestions as to how I can reduce or stop these lock timeouts?

    Thanks. [xx(]
  2. satya Moderator

  3. kuffy New Member

    Thanks Satya.

Share This Page