Remote-Agent Activation

Hi,
Two questions:
1. Not 100-percent sure about this, but it looks like for a
subscription configured with remote agent activation where the
destination owner for articles are not specified as dbo, during a
resync the articles at the subscriber can be owned by any login on the
subscriber. Is this correct? If so, how can this be fixed without
reinitialising the subscriptions!
2. Is it possible with a no-sync subscription to progate schema changes
without recreating the subscription?
Thanks in advance for any worthwhile comments.
1) no, articles define to have a different object owner on the subscriber
should always be owned by the different object owner after a resync.
2) yes, in sql 2005 the default is to replicate ddl changes, in sql 2000 you
can use sp_repladdcolumn or sp_repldropcolumn. It doesn't matter if you did
an automatic sync or a no sync.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
<paul.mu@.gapbuster.com> wrote in message
news:1159942193.130907.275300@.h48g2000cwc.googlegr oups.com...
> Hi,
> Two questions:
> 1. Not 100-percent sure about this, but it looks like for a
> subscription configured with remote agent activation where the
> destination owner for articles are not specified as dbo, during a
> resync the articles at the subscriber can be owned by any login on the
> subscriber. Is this correct? If so, how can this be fixed without
> reinitialising the subscriptions!
> 2. Is it possible with a no-sync subscription to progate schema changes
> without recreating the subscription?
> Thanks in advance for any worthwhile comments.
>
|||Thanks for your response Hilary.
The answer to my first question was not what I was after.
Firstly, I am working with transactional replication on SQL Server
2000.
Secondly, I did not have this issue before he change to use remote
agent activation.
The current setup is that most of the articles in the publications do
not have the 'destination_owner' set (it is left as a blank) - the
source_owner is always 'dbo'.
The problem: with remote agent activation, when performing a resync,
the articles at the subscribers have been created with a different
'destination_owner' which is not 'dbo'. This owner can vary from one
resync to another.
A question: can this issue be resolved without having to reconfigure
the publication (ie. replace all blank destination_owner with 'dbo'),
which will require a resync?