Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

CLR Objects - impossible to remove schema replication from them????

0 views
Skip to first unread message

geraint

unread,
Aug 11, 2008, 6:05:06 AM8/11/08
to
Hi,

I've got a database that _was_ replicated at one point. The replication has
been removed, and doesn't exist any more.

BUT - there appears to be some replication artefacts hanging around for 4
objects.
Key info:
- 4 objects in sys.objects have their is_schema_published values set to 1
- These 4 objects are the only CLR functions/stored procedures in the
database. They are written in C# in a DLL. Neither the DLL nor the objects
can be dropped/altered.
- _Every_ object (including the 4 mentioned above) in the database has
is_published = 0 in sys.objects
- I've run sp_removedbreplication on the database - it doesn't change the
value of is_schema_published for these objects.
- I've run sp_MSunmarkreplinfo on the 4 affected objects - again, no
effect
- There are no publications nor subscriptions on the database (e.g.
sp_helppublication returns nothing).

Does anyone have any idea how I can actually remove this replication so that
I can update or just delete the objects?!
Is it just a co-incidence that this replication "issue" only affects CLR
objects? Is this a bug?!

THANKS!

geraint.


Hilary Cotter

unread,
Aug 16, 2008, 12:04:13 PM8/16/08
to
Is it possible for you to drop the assemblies and other related objects?

"geraint" <ger_at_beff.co.uk> wrote in message
news:aZidnRAXZJFPkz3V...@posted.plusnet...

geraint

unread,
Aug 26, 2008, 11:11:31 AM8/26/08
to

Ysgrifennodd "Hilary Cotter" <hilary...@gmail.com> mewn neges
newyddion:FD2DA311-F938-4B32...@microsoft.com...

> Is it possible for you to drop the assemblies and other related objects?

Nothing related to these objects can be dropped because the objects are
flagged for replication.
Also tried stopping SQL Server and deleting the assembly DLLs, then
restarting the server, and it still won't let me drop them.

I've ended up having to copy the schema across to a new blank database, then
populating the new database with the data from the previous one.
A lot of hassle/work, but there was no other way I could find of actually
removing these supposedly replicated objects.

ARGH!

hwyl!
geraint.


0 new messages