Replication Objects are still there.....

I restored a db to a new server, executed the following;
exec sp_removedbreplication 'ADAGE'
go
exec sp_dboption 'ADAGE', 'published', 'FALSE'
go
exec sp_dboption 'ADAGE', 'merge publish', 'FALSE'
go
Yet, the ADAGE db still has views like sync%
Did I miss a step necessary to remove all traces of replication on this db?
Do I have to manually remove these objects?
I want to use this database to replicate to (New Publication / Subscription), but I first want to make sure all traces of previous replication are gone.
JLS
you missed the manual delete step. But you really don't have to do this. When you reinstall replication or recreate a publication it will whack the objects it doesn't need anymore or create new names.
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
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23DNr6Nk2FHA.2816@.tk2msftngp13.phx.gbl...
I restored a db to a new server, executed the following;
exec sp_removedbreplication 'ADAGE'
go
exec sp_dboption 'ADAGE', 'published', 'FALSE'
go
exec sp_dboption 'ADAGE', 'merge publish', 'FALSE'
go
Yet, the ADAGE db still has views like sync%
Did I miss a step necessary to remove all traces of replication on this db?
Do I have to manually remove these objects?
I want to use this database to replicate to (New Publication / Subscription), but I first want to make sure all traces of previous replication are gone.
JLS
|||Ok, great, Thanx!!!!
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:%234Jhehk2FHA.3416@.tk2msftngp13.phx.gbl...
you missed the manual delete step. But you really don't have to do this. When you reinstall replication or recreate a publication it will whack the objects it doesn't need anymore or create new names.
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
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23DNr6Nk2FHA.2816@.tk2msftngp13.phx.gbl...
I restored a db to a new server, executed the following;
exec sp_removedbreplication 'ADAGE'
go
exec sp_dboption 'ADAGE', 'published', 'FALSE'
go
exec sp_dboption 'ADAGE', 'merge publish', 'FALSE'
go
Yet, the ADAGE db still has views like sync%
Did I miss a step necessary to remove all traces of replication on this db?
Do I have to manually remove these objects?
I want to use this database to replicate to (New Publication / Subscription), but I first want to make sure all traces of previous replication are gone.
JLS

Replication Loop Back Detection Problems in SQL Server 2000

Hi,

I am monitoring my replication process and I have a problem with the loop detection, I can see origined transacctions in the server, executed in the same for the replication.

The subscriptions configuration is sp_helpsubscription

exec sp_addsubscription @.publication = N'PUBLICATION',
@.article = N'all',
@.subscriber = N'192.168.0.23',
@.destination_db = N'PRUEBABD',
@.sync_type = N'none',
@.update_mode = N'read only',
@.offloadagent = 0,
@.dts_package_location = N'distributor',
@.loopback_detection = 'true'
GO

I need for help.

Sorry, it's not clear to me what the problem is. Are you getting an error of some sort?|||

Yes, I have loops in the replication between the subscribers and too many deadlocks.

My topology is

Server A replicates to Server P,

the Server P replicates to Server A,

Server B replicates to Server P and

the Server P replicates to Server B.

I am using transactional replication,

|||sorry, i'm still not clear. what exactly is the error. if it's deadlock, what statements are deadlocking?|||My problem is that loop back detection is unless when I registed the subscriptions with IP. The publicator servers are registered for name.