gaps in transactional replication

  • when we add the subscriptions

    exec sp_addsubscription

    @publication = N'trans_journal_b'

    , @subscriber = N'SERVER\SUBSCRIBER'

    , @destination_db = N'mydb'

    , @subscription_type = N'Push'

    , @sync_type = N'None' -- 'Automatic', 'replication support only'

    , @article = N'all'

    , @update_mode = N'read only'

    , @subscriber_type = 0

  • Hmm that interesting i believe mine is none i don't change the defaults...

    Glad to hear it working.

  • Glad that it's working. Interestingly, BOL says that the "none" option is deprecated and MS wants you to use "replication support only" instead. The same warning is in BOL for SQL 2008 though. Obviously something is different under the covers; I'd love to hear from someone at MS who could explain what the difference is between the two options, or for that matter if what you've discovered is expected behavior.

    Kendal Van Dyke
    http://kendalvandyke.blogspot.com/[/url]

  • Oh that will teach you to read the manual 😀

  • there is a bug in sql 2005 where if you run alter index and the log reader runs on the publisher at the same time then it may not pick up transactions to replicate.

    you can control when you run replication or the latest hotfix build 3294 has a fix for this

Viewing 5 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic. Login to reply