Removing replicated data on a remote device without deleting it on the server

In the replication scenario I am dealing with, a mobile device (PDA)
uses SQL Server Mobile to synchronize data with a SQL Server database
located on some server. The mobile user can enter new data on the PDA.
Data replicated from the server to the PDA cannot be modified.
However, after a long period of time, it is possible that the amount
of new data entered on the PDA could be potentially large.
Is it possible with replication that once new data is entered into the
PDA and then gets replicated back to the server, that it can be
removed from the PDA but without this removal causing the data to be
deleted on the server?
Thanks for your help
Polaris
You could try disabling the triggers before deleting the records. However
this means that modifications to these rows on the publisher will fail when
being applied to the subscriber. I'd archive the data on the publisher then
delete it on the publisher so the delete flows to the subscriber. If you
want to see the data on the publisher you could use a view which amalgamates
the data there.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||I think you need to use a technology like RDA for this.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Polaris431" <polaris431@.gmail.com> wrote in message
news:1172129049.331836.154340@.a75g2000cwd.googlegr oups.com...
> In the replication scenario I am dealing with, a mobile device (PDA)
> uses SQL Server Mobile to synchronize data with a SQL Server database
> located on some server. The mobile user can enter new data on the PDA.
> Data replicated from the server to the PDA cannot be modified.
> However, after a long period of time, it is possible that the amount
> of new data entered on the PDA could be potentially large.
> Is it possible with replication that once new data is entered into the
> PDA and then gets replicated back to the server, that it can be
> removed from the PDA but without this removal causing the data to be
> deleted on the server?
> Thanks for your help
> Polaris
>

Removing Mobile Edition BOL

I'm hoping that someone has any ideas on this. I want to completely strip the entire Books Online module for SQL Server Mobile Edition. Why? It gets really irritating when I try to look up topics and it always yanks up stuff from the Mobile edition and I could care less about those. There are entire sets of topics that BOL will do nothing but pull up the Mobile edition topic which is completely irrelevant for other editions.

Hi Michael,

Yes, you can remove the Mobile edition topics from the help collection. See the Books Online topic "SQL Server 2005 Combined Help Collection Manager " (ms-help://sql90/sqlcc9/html/b06d0f98-ef00-4b03-9f5d-b5c184b8df92.htm).

In that topic under the heading "Available Help Collections", clear the checkbox for SQL Server Mobile and then click Update Combined Help Collection. Close BOL and reopen it and the Mobile topics will be gone from the Index and Search filters.

Regards,

Gail

|||

That would make sense, if it would actually work or point me to anything. Pulling up that help topic throws a debug runtime error message:

n_objPlugInListMSDNArchive.Count is null or not an object

I'm assuming that it is on this page that it actually shows the collections, but since it always throws a runtime error, they obviously don't display. I'm also assuming that it is in this list that will not display that I'll find the check boxes to get rid of the Mobile Edition BOL.

I have now tried this on 11 different machines. 3 of them throw run time debug errors. The other 8 pull up the page which doesn't display any installed collections at all. So, it takes me back to my original question since there doesn't seem to be any working mechanism for getting rid of this Mobile Edition help that continuously garbages up my results.

|||

Hi Michael,

The scripting error you're getting occurs in some scenarios when SQL Server 2005 BOL and the MSDN Library are installed side-by-side. I was told that this error was fixed in the April refresh of SQL Server 2005 Books Online. Updating your version of Books Online to the April or July refresh from here: http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx should fix the scripting problem. Afterwards, you should be able to use the page I mentioned earlier correctly.

Let me know if this doesn't solve the problem for you.

Regards,

Gail