<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: DBREMOTE with selective publications in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/dbremote-with-selective-publications/qaa-p/13847073#M4877916</link>
    <description>&lt;P&gt;AFAIK, no, there is no such option.&lt;/P&gt;
&lt;P&gt;DBREMOTE sends and/or receives modifications for all according publications. IMHO, that is a design choice and does manifest in the fact that the according SYS.SYSREMOTEUSER table stores the sent/received transaction log offsets per remote database, not per publication. – In contrast, MobiLink does manage those per publication, cf. SYSSCYNC/SYSSYUNC2.&lt;/P&gt;</description>
    <pubDate>Mon, 23 Apr 2018 07:55:42 GMT</pubDate>
    <dc:creator>VolkerBarth</dc:creator>
    <dc:date>2018-04-23T07:55:42Z</dc:date>
    <item>
      <title>DBREMOTE with selective publications</title>
      <link>https://community.sap.com/t5/technology-q-a/dbremote-with-selective-publications/qaq-p/13847072</link>
      <description>&lt;P&gt;Is there any way to start DBREMOTE so that it replicates only specific publications?
Something like the option -n in DBMLSYNC.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Apr 2018 07:09:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/dbremote-with-selective-publications/qaq-p/13847072</guid>
      <dc:creator>Baron</dc:creator>
      <dc:date>2018-04-23T07:09:05Z</dc:date>
    </item>
    <item>
      <title>Re: DBREMOTE with selective publications</title>
      <link>https://community.sap.com/t5/technology-q-a/dbremote-with-selective-publications/qaa-p/13847073#M4877916</link>
      <description>&lt;P&gt;AFAIK, no, there is no such option.&lt;/P&gt;
&lt;P&gt;DBREMOTE sends and/or receives modifications for all according publications. IMHO, that is a design choice and does manifest in the fact that the according SYS.SYSREMOTEUSER table stores the sent/received transaction log offsets per remote database, not per publication. – In contrast, MobiLink does manage those per publication, cf. SYSSCYNC/SYSSYUNC2.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Apr 2018 07:55:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/dbremote-with-selective-publications/qaa-p/13847073#M4877916</guid>
      <dc:creator>VolkerBarth</dc:creator>
      <dc:date>2018-04-23T07:55:42Z</dc:date>
    </item>
    <item>
      <title>Re: DBREMOTE with selective publications</title>
      <link>https://community.sap.com/t5/technology-q-a/dbremote-with-selective-publications/qaa-p/13847074#M4877917</link>
      <description>&lt;P&gt;Thanks, this was also my point, I wanted just to get a confirm.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Apr 2018 07:57:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/dbremote-with-selective-publications/qaa-p/13847074#M4877917</guid>
      <dc:creator>Baron</dc:creator>
      <dc:date>2018-04-23T07:57:18Z</dc:date>
    </item>
    <item>
      <title>Re: DBREMOTE with selective publications</title>
      <link>https://community.sap.com/t5/technology-q-a/dbremote-with-selective-publications/qaa-p/13847075#M4877918</link>
      <description>&lt;P&gt;Well, "AFAIK":) - possibly Reg has some smart workaround?&lt;/P&gt;</description>
      <pubDate>Mon, 23 Apr 2018 08:05:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/dbremote-with-selective-publications/qaa-p/13847075#M4877918</guid>
      <dc:creator>VolkerBarth</dc:creator>
      <dc:date>2018-04-23T08:05:10Z</dc:date>
    </item>
  </channel>
</rss>

