Results 1 to 4 of 4
  1. #1
    Join Date
    Sep 2003
    Location
    KY
    Posts
    146

    Unanswered: Tricky replication situation

    I have a Transaction replication running between 2 SQl 2000 Servers. The distributor is on seperate machine.

    Server1 is an online Db which is sending replicated trn to Server2 which is a reporting Server. Because of space issues, I have to remove about 100 Million Rows from Server1 Table without affectiing Server2 Table (Server 2 Retains those rows)
    Is there any Stored Proc available to disable the replication only during that time ?

    Thanks

  2. #2
    Join Date
    Jul 2002
    Posts
    63
    You should drop the subscription of this article from this publication by the following system SP :

    exec sp_dropsubscription
    @publication = 'PublicationName'
    , @article = 'TableName'
    , @subscriber = 'SecondServerName'
    , @destination_db = 'DataBaseName'

    when Finshed , add it again -
    sp_addsubscription
    @publication = 'PublicationName'
    , @article ='TableName'
    , @subscriber = 'SecondServerName' , @destination_db = 'DataBaseName'


    Eyal

  3. #3
    Join Date
    Jul 2002
    Posts
    63
    alternative option is :

    you could alter the delete stored procedure on the subscribers to prevent the delete, although this will obviously result in non-synchronised data.
    (FROM http://www.replicationanswers.com/Transactional.asp)

  4. #4
    Join Date
    Sep 2003
    Location
    KY
    Posts
    146

    Thanks

    Thanks to both !

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •