Re: .Pre Files

As much as it is difficult for you to believe, your two publisher databases
must also be configured as subscriber databases for somebody else. You may
be able to find out who the "publisher" of your publisher is by looking at
the name of the application executing the drop command in SQL Profiler.

-Raymond
"A. Robinson" <ARobinson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C9A824BA-7A98-4F33-9A92-4F73C9ECA713@xxxxxxxxxxxxxxxx
Witnessing some strange behavior...

For some reason, instead of SQL Serve rapplying the .pre files to the
subscriber, SQL Server is trying to apply those scripts to the publisher.

What gives?

I've dropped the subscription, dropped the publication, recreated
everything
and I'm still getting the issue.

The odd thing is that aout of three different publications, this is
hppening
to to of them - the third publication works just fine - you can check the
history and see that the .pre files get applied to the subscriber.

Has anyone ever seen this??

Thanks!!


.

Relevant Pages