I have read & read & read and cannot seem to find the answer to my =
issue.

I have several publications on SQL-01 with Transactional Replication =
from one db to another, running well.

Now I have a new reporting Sql Server - SQL-02.=20
I set the Distributor up, and created the reporting db to be replicated =
to.

I want to PULL the db from SQL-01 to the db on SQL-02. I want the =
Distributor on the new box, SQL-02 to be used. Since the publication =
already exists on SQL-01, isn't it just a matter of PULLING the =
subscription to SQL-02?

The publication job is setup to use SA, but I continually get=20
"Error 8198: Could not obtain information about Windows NT group =
Domain\SQL02Notif'

To use the distribution database on the subscriber you will have to=20

1) enable the subscriber for replication
2) go to tools, replication, configure publishers, subscribers, =
distributor on the subscriber and click on the publisher tab. And then =
click on the publisher tab, and enable the remote publisher to use this =
distributor. Click on the three ellipses to the right of your publisher =
and disable the administrative link password.
3) connect to your publisher and disable replication. Then recreate it =
and configure it to use the remote distributor on the subscriber.
4) recreate your publication and pull subscription.

Your error sounds like your pull subscription does not have rights to =
access the snapshot share. Either add the account that the SQL Agent =
account runs under on the subscriber to the local admin group on the =
publisher, or change the snapshot share to a folder which the SQL Agent =
account on the subscriber can access.


[quoted text, click to view]
I have read & read & read and cannot seem to find the answer to my =
issue.

I have several publications on SQL-01 with Transactional Replication =
from one db to another, running well.

Now I have a new reporting Sql Server - SQL-02.=20
I set the Distributor up, and created the reporting db to be =
replicated to.

I want to PULL the db from SQL-01 to the db on SQL-02. I want the =
Distributor on the new box, SQL-02 to be used. Since the publication =
already exists on SQL-01, isn't it just a matter of PULLING the =
subscription to SQL-02?

The publication job is setup to use SA, but I continually get=20
"Error 8198: Could not obtain information about Windows NT group =
Domain\SQL02Notif'

# 3 - connect to your publisher and disable replication.

What if I have multiple publications of 1 table going here & 1 table =
going there and want these publications to continue to use the =
distributor on the publishing server?
Is that ok?

For instance; 1 publication publishes only 1 table from database a to =
database b on the same server and uses this server as the distributor.

Then the publication I am now trying to Pull & have the distributor be =
remote, will pull multiple tables from database a to the database on the =
remote server.

Any problems with that?

The disable replication concerned me, I don't want to affect any of the =
other publications by setting up the new publication to run at the =
remote distributor & pull subscription.

I sure hope I am making sense.....


[quoted text, click to view]
To use the distribution database on the subscriber you will have to=20

1) enable the subscriber for replication
2) go to tools, replication, configure publishers, subscribers, =
distributor on the subscriber and click on the publisher tab. And then =
click on the publisher tab, and enable the remote publisher to use this =
distributor. Click on the three ellipses to the right of your publisher =
and disable the administrative link password.
3) connect to your publisher and disable replication. Then recreate it =
and configure it to use the remote distributor on the subscriber.
4) recreate your publication and pull subscription.

Your error sounds like your pull subscription does not have rights to =
access the snapshot share. Either add the account that the SQL Agent =
account runs under on the subscriber to the local admin group on the =
publisher, or change the snapshot share to a folder which the SQL Agent =
account on the subscriber can access.


[quoted text, click to view]
I have read & read & read and cannot seem to find the answer to my =
issue.

I have several publications on SQL-01 with Transactional Replication =
from one db to another, running well.

Now I have a new reporting Sql Server - SQL-02.=20
I set the Distributor up, and created the reporting db to be =
replicated to.

I want to PULL the db from SQL-01 to the db on SQL-02. I want the =
Distributor on the new box, SQL-02 to be used. Since the publication =
already exists on SQL-01, isn't it just a matter of PULLING the =
subscription to SQL-02?

The publication job is setup to use SA, but I continually get=20
"Error 8198: Could not obtain information about Windows NT group =
Domain\SQL02Notif'

Basically you are hosed. Existing publications on the publisher will =
have to be migrated to the new distributor.=20

Why do you want to use a remote distributor? If it is to offload the =
extra processing from the new publication subscription you might want to =
consider remote activation.

For plain pull subscriptions that distributor on the subscriber will =
only contain historical information. It won't contain the transactions =
and commands to be replicated.=20

Perhaps at this point you could tell us exactly what you are trying to =
accomplish so we can consider all the options available to you.

[quoted text, click to view]
# 3 - connect to your publisher and disable replication.

What if I have multiple publications of 1 table going here & 1 table =
going there and want these publications to continue to use the =
distributor on the publishing server?
Is that ok?

For instance; 1 publication publishes only 1 table from database a to =
database b on the same server and uses this server as the distributor.

Then the publication I am now trying to Pull & have the distributor be =
remote, will pull multiple tables from database a to the database on the =
remote server.

Any problems with that?

The disable replication concerned me, I don't want to affect any of =
the other publications by setting up the new publication to run at the =
remote distributor & pull subscription.

I sure hope I am making sense.....

=20
[quoted text, click to view]
To use the distribution database on the subscriber you will have to=20

1) enable the subscriber for replication
2) go to tools, replication, configure publishers, subscribers, =
distributor on the subscriber and click on the publisher tab. And then =
click on the publisher tab, and enable the remote publisher to use this =
distributor. Click on the three ellipses to the right of your publisher =
and disable the administrative link password.
3) connect to your publisher and disable replication. Then recreate =
it and configure it to use the remote distributor on the subscriber.
4) recreate your publication and pull subscription.

Your error sounds like your pull subscription does not have rights =
to access the snapshot share. Either add the account that the SQL Agent =
account runs under on the subscriber to the local admin group on the =
publisher, or change the snapshot share to a folder which the SQL Agent =
account on the subscriber can access.


[quoted text, click to view]
I have read & read & read and cannot seem to find the answer to my =
issue.

I have several publications on SQL-01 with Transactional =
Replication from one db to another, running well.

Now I have a new reporting Sql Server - SQL-02.=20
I set the Distributor up, and created the reporting db to be =
replicated to.

I want to PULL the db from SQL-01 to the db on SQL-02. I want the =
Distributor on the new box, SQL-02 to be used. Since the publication =
already exists on SQL-01, isn't it just a matter of PULLING the =
subscription to SQL-02?

The publication job is setup to use SA, but I continually get=20
"Error 8198: Could not obtain information about Windows NT group =
Domain\SQL02Notif'

I have a new server which will serve as the reporting server. I want to =
replicate all the transactions from my ERP database to a database on the =
reporting server to offload this activity on the production server.

I don't have to use a remote distributor. I am new to this and =
basically feeling my way around to find the absolute best solution. (I, =
for one, am anxiously awaiting the book release)

From what I have read thus far, it was suggested that running the =
Distributor & Pulling the subscription would result in better =
performance for both boxes.
Overall my goal is to enhance performance on the production server, the =
OLTP system. I thought replicating to a reporting server would be a =
significant step in accomplishing this task.

If you had 2 servers, 1 for production transactions and 1 for reporting, =
what would be your choices? =20

The other thing is that I am still experiencing the 8198 error message.
The publication job is setup to use SA, but I continually get=20
"Error 8198: Could not obtain information about Windows NT group =
Domain\SQL02Notif'
I added the accounts on both boxes to the local admins group, therefore, =
they have access to everything on that box. I'm really stuck on this =
one!


[quoted text, click to view]
Basically you are hosed. Existing publications on the publisher will =
have to be migrated to the new distributor.=20

Why do you want to use a remote distributor? If it is to offload the =
extra processing from the new publication subscription you might want to =
consider remote activation.

For plain pull subscriptions that distributor on the subscriber will =
only contain historical information. It won't contain the transactions =
and commands to be replicated.=20

Perhaps at this point you could tell us exactly what you are trying to =
accomplish so we can consider all the options available to you.

[quoted text, click to view]
# 3 - connect to your publisher and disable replication.

What if I have multiple publications of 1 table going here & 1 table =
going there and want these publications to continue to use the =
distributor on the publishing server?
Is that ok?

For instance; 1 publication publishes only 1 table from database a =
to database b on the same server and uses this server as the =
distributor.

Then the publication I am now trying to Pull & have the distributor =
be remote, will pull multiple tables from database a to the database on =
the remote server.

Any problems with that?

The disable replication concerned me, I don't want to affect any of =
the other publications by setting up the new publication to run at the =
remote distributor & pull subscription.

I sure hope I am making sense.....

=20
[quoted text, click to view]
To use the distribution database on the subscriber you will have =
to=20

1) enable the subscriber for replication
2) go to tools, replication, configure publishers, subscribers, =
distributor on the subscriber and click on the publisher tab. And then =
click on the publisher tab, and enable the remote publisher to use this =
distributor. Click on the three ellipses to the right of your publisher =
and disable the administrative link password.
3) connect to your publisher and disable replication. Then =
recreate it and configure it to use the remote distributor on the =
subscriber.
4) recreate your publication and pull subscription.

Your error sounds like your pull subscription does not have rights =
to access the snapshot share. Either add the account that the SQL Agent =
account runs under on the subscriber to the local admin group on the =
publisher, or change the snapshot share to a folder which the SQL Agent =
account on the subscriber can access.


[quoted text, click to view]
I have read & read & read and cannot seem to find the answer to =
my issue.

I have several publications on SQL-01 with Transactional =
Replication from one db to another, running well.

Now I have a new reporting Sql Server - SQL-02.=20
I set the Distributor up, and created the reporting db to be =
replicated to.

I want to PULL the db from SQL-01 to the db on SQL-02. I want =
the Distributor on the new box, SQL-02 to be used. Since the =
publication already exists on SQL-01, isn't it just a matter of PULLING =
the subscription to SQL-02?

The publication job is setup to use SA, but I continually get=20
"Error 8198: Could not obtain information about Windows NT group =
Domain\SQL02Notif'