Hi,
I created a transactionnal publication with one pull subscription. All
work fine, the transactions are replicated on subscriber. But on the
subscriber, I have two subscriptions under the "Local subscription" in
SQL Server Management Studio with one that don't have a publication
name. I cannot see properties, I get this message :
- SQL Server is unable to complete the operation.
-
- You must manage this subscription from the Publisher because it
shares a Distribution Agent with subscriptions - to other
publications from the same publication database. (Subscription
Properties)
This subscriptions appears after I call
sp_addpullsubscription_agent...
It's normal?I suggest you to post this message to
"microsoft.public.sqlserver.replication"
You'll probably get more answers about this issue there.
--
Ekrem Önsoy
"PPaquin" <patrick.paquin@.gmail.com> wrote in message
news:1189199171.692355.60980@.19g2000hsx.googlegroups.com...
> Hi,
> I created a transactionnal publication with one pull subscription. All
> work fine, the transactions are replicated on subscriber. But on the
> subscriber, I have two subscriptions under the "Local subscription" in
> SQL Server Management Studio with one that don't have a publication
> name. I cannot see properties, I get this message :
> - SQL Server is unable to complete the operation.
> -
> - You must manage this subscription from the Publisher because it
> shares a Distribution Agent with subscriptions - to other
> publications from the same publication database. (Subscription
> Properties)
> This subscriptions appears after I call
> sp_addpullsubscription_agent...
> It's normal?
>|||Thanks, I do...
On 7 sep, 17:20, Ekrem =D6nsoy <ek...@.btegitim.com> wrote:
> I suggest you to post this message to
> "microsoft.public.sqlserver.replication"
> You'll probably get more answers about this issue there.
> --
> Ekrem =D6nsoy
> "PPaquin" <patrick.paq...@.gmail.com> wrote in message
> news:1189199171.692355.60980@.19g2000hsx.googlegroups.com...
>
> > Hi,
> > I created a transactionnal publication with one pull subscription. All
> > work fine, the transactions are replicated on subscriber. But on the
> > subscriber, I have two subscriptions under the "Local subscription" in
> > SQL Server Management Studio with one that don't have a publication
> > name. I cannot see properties, I get this message :
> > - SQL Server is unable to complete the operation.
> > -
> > - You must manage this subscription from the Publisher because it
> > shares a Distribution Agent with subscriptions - to other
> > publications from the same publication database. (Subscription
> > Properties)
> > This subscriptions appears after I call
> > sp_addpullsubscription_agent...
> > It's normal... Masquer le texte des messages pr=E9c=E9dents -
> - Afficher le texte des messages pr=E9c=E9dents -
Showing posts with label replicated. Show all posts
Showing posts with label replicated. Show all posts
Monday, March 12, 2012
Pull subscription
Labels:
created,
database,
microsoft,
mysql,
oracle,
publication,
pull,
replicated,
server,
sql,
subscriber,
subscription,
transactionnal,
transactions
Friday, March 9, 2012
Publishing Parts of a table
I'm new to SQL 2000, one of my customers requires two tables of my DB replicated on it's server, for auditing, I guess.
I'm thinking about using transactional Replication given that the changes are made often and the tables are going to increase fast in size. The problem is, in the same tables, I have information also from other customers that I don't want to replicate to
the one is asking me this. So, Is there any way to do this? I mean, apply a kind of Select to the tables before sending the transactions to the Subscriber server? so they only receive what concerns to them.
I don't know if my question is clear or not, sorry about that, and thanks so much for the help.
Manuel,
you can filter the rows in the publication properties. This is on the
"Filter Rows" tab. You should end up with a filter something like this:
SELECT <published_columns> FROM <<TABLE>> WHERE
<<TABLE>>.categoryid > 2
HTH,
Paul Ibison
I'm thinking about using transactional Replication given that the changes are made often and the tables are going to increase fast in size. The problem is, in the same tables, I have information also from other customers that I don't want to replicate to
the one is asking me this. So, Is there any way to do this? I mean, apply a kind of Select to the tables before sending the transactions to the Subscriber server? so they only receive what concerns to them.
I don't know if my question is clear or not, sorry about that, and thanks so much for the help.
Manuel,
you can filter the rows in the publication properties. This is on the
"Filter Rows" tab. You should end up with a filter something like this:
SELECT <published_columns> FROM <<TABLE>> WHERE
<<TABLE>>.categoryid > 2
HTH,
Paul Ibison
Subscribe to:
Posts (Atom)