Showing posts with label login. Show all posts
Showing posts with label login. Show all posts

Wednesday, March 21, 2012

Replication and Windows login

Does the administrator windows login name and password of all servers
participate in replication must be the same?, or may I use the SQL
authentication?IIRC, Replication using windows authentication requires a trusted connection
using the same account on both end. BOL also has this:
Connections to a server (Publisher, Distributor, or Subscribers) can use
Windows Authentication or SQL Server security. Windows Authentication is
generally preferred for greater security and ease of use; however,
connections to Windows 98 servers must use SQL Server security because
Windows Authentication is a feature only on Windows NT 4.0 and Windows 2000.
It is recommended that the Subscriber connection have dbo permissions in the
subscription database to make sure the proper permissions are granted, and
for overall simplification; however, dbo permissions are not
If you are connecting to an untrusted domain you may wish to use SQL
authentication although this will weaken security.
Neil MacMurchy
"Tal" <talg@.nice.com> wrote in message
news:OjhYTt2$DHA.2348@.TK2MSFTNGP09.phx.gbl...
> Does the administrator windows login name and password of all servers
> participate in replication must be the same?, or may I use the SQL
> authentication?
>

Replication and Windows login

Does the administrator windows login name and password of all servers
participate in replication must be the same?, or may I use the SQL
authentication?IIRC, Replication using windows authentication requires a trusted connection
using the same account on both end. BOL also has this:
Connections to a server (Publisher, Distributor, or Subscribers) can use
Windows Authentication or SQL Server security. Windows Authentication is
generally preferred for greater security and ease of use; however,
connections to Windows 98 servers must use SQL Server security because
Windows Authentication is a feature only on Windows NT 4.0 and Windows 2000.
It is recommended that the Subscriber connection have dbo permissions in the
subscription database to make sure the proper permissions are granted, and
for overall simplification; however, dbo permissions are not
If you are connecting to an untrusted domain you may wish to use SQL
authentication although this will weaken security.
Neil MacMurchy
"Tal" <talg@.nice.com> wrote in message
news:OjhYTt2$DHA.2348@.TK2MSFTNGP09.phx.gbl...
> Does the administrator windows login name and password of all servers
> participate in replication must be the same?, or may I use the SQL
> authentication?
>sql

Monday, March 12, 2012

replication 18483 eroor

hi all...
I have a little problem.
"18483 - could not connect to server 'Newname' because distributor_admin is
not defined as a remote login at the server."
Mehmet,
Try (using 'Newname')
Use Master
go
Select @.@.Servername
This should return your current server name but if it
returns NULL then try:
Use Master
go
Sp_DropServer 'OldName'
GO
Use Master
go
Sp_Addserver 'NewName', 'local'
GO
Stop and Start SQL Services
If this is not the solution, please let me know if you are using IP
addresses for registered servers in Enterprise Manager.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)