SQL Server Performance

Transactional Replication with Queued updating

Discussion in 'Performance Tuning for SQL Server Replication' started by shantaram, Mar 19, 2006.

  1. shantaram New Member

    Hi
    I'm trying to do replication(tarnsactional replication with queued updating) on two different servers(SQL server 2000) one of them is configured as Publisher and Distributer whereas other one is a subscriber. Everything seems fine but only problem is that modifications made to the articles from the subscribers are not being updated on the publisher.The transactions from publisher to the subscriber works fine.I tried ODBCping from publisher which gives the output as follows:

    CONNECTED TO SQL SERVER

    ODBC SQL Server Driver Version: 03.80.0194

    SQL Server Version: Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
    Dec 17 2002 14:22:05
    Copyright (c) 1988-2003 Microsoft Corporation
    Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

    But when I tried same thing from subscriber to the publisher the output was as follows:

    C:program FilesMicrosoft SQL ServerMSSQLBinn>odbcping -S 172.16.128.42 -U sa
    -P

    COULD NOT CONNECT TO SQL SERVER

    SQLState: 28000 Native Error: 18456
    Info. Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for u
    ser 'sa-P'.

    Can anyone solve this problem , it's very urgent.

    Regards
    Shantaram
  2. shantaram New Member

    Hi
    I've found that when odbcping command was given without -P the subscriber server got connected to the publisher server.
    However the problem still persists,i.e. the chenges made to the article at subscriber end doesn't get updated at the publisher end. Queued reader agent error :"Server: ABC, Database unique : ODBC Error:Could not change the Publisher because the subscription has been dropped. Use sp_subscription_cleanup to clean up the triggers."
    Any clue on this?
    Regards
    Shantaram
  3. satya Moderator

Share This Page