Re: SQL Server 2000 Replication Agents Credentials

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

they are stored in sysjobsteps in msdb, but they are stored in encrypted
format.

--
Hilary Cotter

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



"Ronald Green" <zzzbla@xxxxxxxxx> wrote in message
news:1170764727.927169.252770@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Hilary,

Thanks for your prompt response.

I investigated it further, and ran a trace on the three servers
(publisher, distributor and subscriber) to find out which agent is
using which login.

Apparently, the snapshot agent IS using sql login to connect to the
publisher and to the distributor although it is not specified in its
command line.

The pull distribution agent (running on the subscriber) IS using sql
login to connect both to the distributor and to the subscriber
although only the subscriber sql login is specified in the command
line.

Finally, the log reader agent ISN'T using sql login to connect to the
publisher, but rather the SQL Agent service account. In order to
override it, I change the command line parameters in the job step.

Do you (or anyone else) know where SQL Server 2000 saves the sql
logins used by the replication agents?

Also, why isn't the log reader using sql login like the rest of the
agents?
I know I don't directly tell it to use sql login. Is there any way to
manipulate the log reader agent using stored procedures? For instance,
how do I tell it to use a schedule other than the default (Start with
sql server)? Now I simple change the job schedule and remove the "-
Continuous" flag in the command line parameters.

Thanks in advance,
R. Green

On Feb 6, 1:57 pm, "Hilary Cotter" wrote:
You can run the binaries from the command line, or write a program using
dmo
or the replication activex controls and set the accounts here.

--
Hilary Cotter

Looking for a SQL Server replication
book?http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL
FTShttp://www.indexserverfaq.com




Hi,

I have a replication topology as follows: sql server 2000 sp4
publisher on one server, sql server 2000 sp4 distributor on another
server and sql server 2000 sp4 subscriber on another server.

I execute sp_addpullsubscription_agent (on subscriber) and set all the
security_mode parameters to 0 (zero) and provide logins and passwords
to distributor and subscriber.

Then in the distribution agent job, the command line parameters are as
follows:
-Publisher pubsrv -PublisherDB [mydb] -Publication [mydb subsrv] -
Distributor [distsrv] -SubscriptionType 1 -Subscriber [subsrv] -
SubscriberSecurityMode 0 -SubscriberLogin [sa] -
SubscriberEncryptedPassword [xxxx] -SubscriberDB [mydb_sub]

Using profiler, I see that it connects to the distributor using the
windows credentials the SQL Server agent on the subscriber is using.

Is there any way to change the way the distribution agent connects to
the distributor other than changing it in the job step?

Also, is there any way to even set the credentials for the snapshot
and the log reader agents other than in the job steps?

Thanks in advance,
R. Green



.

Relevant Pages

  • Re: Outlook for MAPI on SBS
    ... I wound up looking at another thread here on installing SQL 2005 which I ... I have noticed something interesting here in SBS ... agent from the SBS Monitoring Agent to the 2005 agent instance. ... Is there an easy way to set up notifications from SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook for MAPI on SBS
    ... I wound up looking at another thread here on installing SQL 2005 which I ... particularly 2005 on SBS. ... agent from the SBS Monitoring Agent to the 2005 agent instance. ... Is there an easy way to set up notifications from SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Setting DCOMCNFG LaunchPermission registry value for everyone group back to "special access"
    ... trying to push content from one SQL server to a cluster server. ... Also this replication ... got TimeOut exipred messages when the agent ran - the specific error message ... SQL Server Agent could not access the replication agent. ...
    (microsoft.public.sqlserver.replication)
  • Setting DCOMCNFG LaunchPermission registry value for everyone group back to "special access"
    ... trying to push content from one SQL server to a cluster server. ... Also this replication ... got TimeOut exipred messages when the agent ran - the specific error message ... SQL Server Agent could not access the replication agent. ...
    (microsoft.public.sqlserver.connect)