Quote:>-----Original Message-----
>I have found that replication is not the best solution
for
>a client and setting up Log Shipping for their warm stand
>by server. Two questions here. 1. I've removed the
>replication jobs, but the database folder in EM still
>shows the database folder with the shared hand symbol.
How
>do I remove this? 2. What is the best newgroup to get
help
>on Log Shipping? Thanks!!!
>.
Say, any idea where I can post questions on Log Shipping?
Quote:>-----Original Message-----
>To remove replication completely go to Tools -
>Replication - Disable Publishing and make sure you use
the
>Yes - disable publishing on YourServerName. This will
>drop all publishers and drop all subscriptions.
>>-----Original Message-----
>>I have found that replication is not the best solution
>for
>>a client and setting up Log Shipping for their warm
stand
>>by server. Two questions here. 1. I've removed the
>>replication jobs, but the database folder in EM still
>>shows the database folder with the shared hand symbol.
>How
>>do I remove this? 2. What is the best newgroup to get
>help
>>on Log Shipping? Thanks!!!
>>.
>.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
thanks.
greg
Quote:> Excellent!! Works like a charm.
> Say, any idea where I can post questions on Log Shipping?
> >-----Original Message-----
> >To remove replication completely go to Tools -
> >Replication - Disable Publishing and make sure you use
> the
> >Yes - disable publishing on YourServerName. This will
> >drop all publishers and drop all subscriptions.
> >>-----Original Message-----
> >>I have found that replication is not the best solution
> >for
> >>a client and setting up Log Shipping for their warm
> stand
> >>by server. Two questions here. 1. I've removed the
> >>replication jobs, but the database folder in EM still
> >>shows the database folder with the shared hand symbol.
> >How
> >>do I remove this? 2. What is the best newgroup to get
> >help
> >>on Log Shipping? Thanks!!!
> >>.
> >.
1. Removing conflict Tables after replication is removed
I have a database that gone through the ringer with replication. Currently
the database is not replicated, but it still has all of the replication
tables in it (system tables). From my understanding if I add merge
replication back, the system will see the existing tables and start
lettering a new set of tables
conflict_AO_xxxx
aconflict_AO_xxxx
bconflict_AO_xxxx
I guess I am looking at how to remove these tables cleanly or the best
method to rebuild this database.
--
David Gabrielson
2. How to retrieve 10 records at a time from VB - SQL - ACCESS db?
3. Enterprise Manager is not removing or adding permissions correctly
5. Transaction Replication Setup Correctly But Not Seeing Transactions
6. permission page of user properties in Enterprise manager**
7. REMOVE, remove, PLEASE REMOVE this idoit out of this group
8. Hacking VFP6
9. Removing merge replication/conflicting triggers
12. Transactional replication- distributor removes FK constraints
13. How to clear up removed subscriptions in Replication\Subscriptions container in SQL2K Server