Proper way to reset SQL Replication script programatically

[Carlos Mendes]

Hi,

I need to reset a SQL replication script programatically.

I was considering doing only a patch to the "Raven/SqlReplication/Status" and change the LastDocEtag to "00000000-0000-0000-0000-000000000000"

  "LastReplicatedEtags": [

    {

      "Name": "NewsReplication",

      "LastDocEtag": "01000000-0000-0002-0000-000000000010"

    },

I found that when I do it through the studio, I get a "Shutting down database x because the tenant database has been updated or removed" message: http://screencast.com/t/Hdjizrjxp7xg

Changing the LastReplicatedEtags is ok or there's a better way to do it?

Thanks in advance

[Oren Eini (Ayende Rahien)]

That should NOT be causing this.

Your solution would work, and that is how it is supposed to be handled.

Can you send us a way to reproduce this?

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Carlos Mendes]

Hi Ayende,

The problem happened on version 

[Carlos Mendes]

Sorry for the incomplete post...

The problem was detected on version 2851. 

We got the shutdown message just by updating and saving a SQL Replication script using the Studio:

I tested the same procedure using the latest stable version, 2939, and the shutdown message seems to be gone:

But I'm still puzzled by the PUT(s) relative to Versioning documents. 

Does this one look ok? 

[Oren Eini (Ayende Rahien)]

I'm not sure why that would happen either.