As far as I experienced it, SQL Server 2000 (at least SP3 and SP3a) does not
handle correctly merge replication of tables owned not by dbo. Various merge
replication related actions are failing because of that. One you just
mentioned - you can not properly drop merge replication, because it leaves
conflict tables. As you noticed from error message it tries to drop table
'HesstechUser.conflict_MergeReplLIVE_VendorCustomer'. I guess on your
published database you should find table
'dbo.conflict_MergeReplLIVE_VendorCustomer'.
If you can find it then I can provide you with a solution to this problem -
but it means fixing of couple of system stored procedures. Fixes are
straight forward - correct handling of object owners.
--
Regards,
Kestutis Adomavicius
Consultant
UAB "Baltic Software Solutions"
[quoted text, click to view] "djc" <noone@nowhere.com> wrote in message
news:OdhjTNDZEHA.2944@TK2MSFTNGP11.phx.gbl...
> I cannot delete a database becuase it ways its part of replication. I
> removed replication via the EM GUI but it failed. All GUI elements are
gone
> but when I run sp_removedbreplication in query analyzer I get this:
>
> Server: Msg 3701, Level 11, State 5, Line 1
> Cannot drop the table
'HesstechUser.conflict_MergeReplLIVE_VendorCustomer',
> because it does not exist in the system catalog.
>
> the weird thing is that the table mentioned in the error should not (and
> does not to my knowledge) exist in this database? it exists in a different
> database on the same system?
>
> any help is greatly appreciated.
>
>