August 8, 2006 at 11:16 am
How do you remove a database from replication process (database is still being used, replication of the database is no longer needed)?
I removed it from the publication, doesn't appear anywhere in replication monitoring, but appears to still be replicating.
Any help would be greatly appreciated.
Thanks,
Wanda
August 9, 2006 at 8:24 am
What do you mean "I removed it from the publication" ?
Did you delete the publication ?
If the database is truly not used in Replication, or you need to temporarily mark it as not used for replication, then you can do a little hack and go into Master..sysdatabases and set category = 0.
August 9, 2006 at 12:20 pm
Yes, I did deleted the publication.
I will keep looking around, I know there's a trigger set to stop replicating a database.....a little uncomfortable with the little, "hack into Master".
Thanks for your suggestion....
Have a Great Day
Wanda
August 9, 2006 at 5:55 pm
(1) Did you delete she subscriber?
(2) Did you use the "Disable Publishing" wizard to disable the replication?
you need to do both of the above for proper disabling. also make sure the distribution database is deleted. The wizard should do it for you.
******************
Dinakar Nethi
Life is short. Enjoy it.
******************
August 10, 2006 at 12:32 am
Hi All,
I am new with SQL2000. I successfully configured (means I can see articles
created at subscriber) Merge Replication (publisher push Pubs database from server A to subscriber Pubssubcriber db at server B) through wizard during replication setup. However I try add one table to publisher but do not see it at subscriber. My doubts as below.
1. How and where to check that replication is running. What things need to watch out?
2. What is the function of SQLServerAgents in merge replication?
3. How and what is the proper way of conduction test case to make sure my replication works.
Your input is welcome..warmest thanks.
Cheers.
August 10, 2006 at 7:12 am
to answer questions from 'chess' questions 1 and 2 kinda go together
1) & 2) checking replication: here are some of the jobs that may get created, listed in no specific order, see BOL (a) agent checkup - makes sure the jobs are running (2) log reader - "watches" the log for cange to replicate (3) the distribution agent - actually does the replication
3) if possible I would do an action to get replicated to verify it is working
what to watch out for: I've found that I had sometimes go back and check my "custom procs" this are the procs that get called on the subscriber to do the inserts, update and deletes
Curtis Smith
SQL Server DBA
Well in worked in Theory ...
August 10, 2006 at 8:21 am
August 10, 2006 at 8:37 am
You can use sp_removedbreplication [ @dbname = ]
August 11, 2006 at 6:56 am
Note: After each of these steps the user TESTED the application & restarted services that was having problems
1. Backed database
2. Shrank database log files & database
3. Attached & reattached database (which indicated no replication)
4. Restored backup database with a different name
5. Dropped original database
6. Renamed restored backup to original name (replication tables no longer appeared)
7. User tested application & restarted services
8. Application LAUNCHED
All of this was related to transactional replication. Problems seem to have appeared due to stopping replication on one of our databases.
I used disable publishing & deleted the subscript.....I deleted the publication had ALL signs that replication had been stopped successfully. Then over two months later I am told that an application will not launch and replication appears to be the problem (replication log full).
Thanks for your responses,
Have a Great Day!
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply