SQL Server Performance

Replication! immediate help required please

Discussion in 'Performance Tuning for SQL Server Replication' started by thebeginner, Aug 3, 2004.

  1. thebeginner New Member

    Hi folks; I have two SQL machines; SERVER1 (Publisher) and SERVER2(Pull merge Subscriber).<br />Every thing seems to be working but:<br />I've just imported 17,000 records from another SQL database into a published table of the production server SERVER1 using IMPORT-EXPORT wizard. Now the subscriber doesn't get updated with these records. When i run the merge-agent; the agent just stops with success without pulling the data.<br /><br />When i set the agent-profile to ROWCOUNT-VALIDATION; it fails at this table.<br /><br />Publisher db at SERVER1 has recovery-model =FULL<br />Subscriber db at SERVER2 has recvery-model=BULK-LOGGED<br /><br />The data in other tables is being merged smoothly though.<br />Please help!![<img src='/community/emoticons/emotion-6.gif' alt=':(' />!]
  2. satya Moderator

    REfer to SQL SErver error log and SQLAgent log for any information on this behaviour.


    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  3. thebeginner New Member

    Dear Satya, the agent runs with success, but doesn't replicated the records i've inserted. If i insert a single record into that published table; it successfully gets merged at the subscriber.
    There isn't any error or info in the Logs.
  4. satya Moderator

    Then monitor the event with PROFILER on both the machines to assess the situation.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  5. thebeginner New Member

    What events should i monitor;
    TEXTDATA =%insert%,%update%,%delete%
  6. satya Moderator

    Bring up the profiler trace that was captured during the time the System Monitor log was also captured, group it by CPU, and look at the large CPU values for the RPC:Completed or the SQL:BatchCompleted events. This will indicate the queries that are CPU intensive<br /><br />2. SQL Profiler with the following events:<br />• SQL:BatchStarting<br />• SQL:BatchCompleted <br />• RPC<img src='/community/emoticons/emotion-7.gif' alt=':S' />tarting <br />• RPC:Completed <br /><br /><br /><hr noshade size="1"><b>Satya SKJ</b><br />Moderator<br /<a target="_blank" href=http://www.SQL-Server-Performance.Com/forum>http://www.SQL-Server-Performance.Com/forum</a><br /><center><font color="teal"><font size="1">This posting is provided “AS IS” with no rights for the sake of <i>knowledge sharing.</i></font id="size1"></font id="teal"></center>

Share This Page